Daily BSOD, ntoskrnl.exe driver fault?

By SunDown
Oct 3, 2010
Post New Reply
  1. Hey guys, Recently got my new computer, and it is amazing! Only problem is that 2 or 3 times a day i get a BSOD...:(

    I checked the Minidump files and it's saying something about VISTA_DRIVER_FAULT and ntoskrnl.exe driver fault.

    This is what the Dump File reads:

    Code:
    Loading Dump File [C:\Users\Nico\Desktop\100210-21122-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c5be50
    Debug session time: Sat Oct  2 15:59:55.289 2010 (UTC + 1:00)
    System Uptime: 0 days 4:09:36.710
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {2b, 2, 0, fffff80002a6ddaa}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+4fdaa )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000000000002b, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002a6ddaa, address which referenced memory
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    
    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    
    MODULE_NAME: nt
    
    FAULTING_MODULE: fffff80002a1e000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     000000000000002b 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt+4fdaa
    fffff800`02a6ddaa 0fb6472b        movzx   eax,byte ptr [rdi+2Bh]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    LAST_CONTROL_TRANSFER:  from fffff80002a8dca9 to fffff80002a8e740
    
    STACK_TEXT:  
    fffff880`0aae5838 fffff800`02a8dca9 : 00000000`0000000a 00000000`0000002b 00000000`00000002 00000000`00000000 : nt+0x70740
    fffff880`0aae5840 00000000`0000000a : 00000000`0000002b 00000000`00000002 00000000`00000000 fffff800`02a6ddaa : nt+0x6fca9
    fffff880`0aae5848 00000000`0000002b : 00000000`00000002 00000000`00000000 fffff800`02a6ddaa 00000000`00000000 : 0xa
    fffff880`0aae5850 00000000`00000002 : 00000000`00000000 fffff800`02a6ddaa 00000000`00000000 66264438`33343836 : 0x2b
    fffff880`0aae5858 00000000`00000000 : fffff800`02a6ddaa 00000000`00000000 66264438`33343836 2e313d72`6f746361 : 0x2
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nt+4fdaa
    fffff800`02a6ddaa 0fb6472b        movzx   eax,byte ptr [rdi+2Bh]
    
    SYMBOL_NAME:  nt+4fdaa
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    
    
    I'm running Windows 7 Home Premium, 64 Bit, i have 6GB RAM, an ATI HD 5770 Graphics Card, and an Athlon II x4 635 Quad Core CPU

    I'll attach the Mini Dump files :)

    Thanks for any help you can give :) <3 Really Appreciate it!

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Tell us when you get these BSODs, i.e., randomly or are you doing something specific at the time.

    You have errors 0x3B and two 0xA but they only cite Windows OS drivers and these are usually too general to be of much diagnostic help.

    By the way, I noticed your system hardware (nice set-up; love to hear your feed back on that 635 processor) and you are running 6 gigs of RAM. Try running with just 4 gigs. Do you gain stability?
  3. SunDown

    SunDown Newcomer, in training Topic Starter

    It's Kinda random, Sometimes it will crash when i'm playing a game, and sometimes it will crash while watching a video. (Which kinda hints to Video Drivers?)

    I recently got the extra Stick of RAM, but before installing that Ram i was still getting the BSOD with the 4GB.

    And the 635 is actually a really nice processor. I was told it was a Low-end Quad Core, But if this is a low end, then I'd love to see the worst Quad Core, Because It's fantastic for the money. Even when playing a game, MSN, Windows Media Player, and a couple other programs open, I'll not go over 50% CPU usage, I'd definitely recommend it to anyone who is on the fence about it, It certainly does deliver, (Especially if your previous CPU was as bad as mine! xD) You can multi-task away without the performance dipping much. (Obviously, there are limits) But for Daily Use and multimedia, It'll definitely do the job. The processor was probably the Component i was most surprised at in my set up.
  4. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Okay, try the following...

    1. Download Driver Cleaner Pro or Driver Sweeper (both have free versions; make sure the version will work with your OS) to your desktop screen and install.

    2. Download the latest diver(s) for your video card but don't install them.

    3. Uninstall your video card drivers and reboot your PC into Safe Mode. Run Driver Cleaner Pro or Driver Sweeper but ONLY for the video card drivers. I had someone use it on their chipset drivers! If it doesn't find any video card drivers that is quite okay.

    4. Reboot and install new video card drivers.


    * Yes, AMD certainly has made some great bang for your buck quad cores that are of top notch quality. There has been a lot of positive experiences with their Athlon II quads (as well as their Phenom II quads).
  5. SunDown

    SunDown Newcomer, in training Topic Starter

    Thanks for the replys,I really Appreciate this! Unfortunately, i cleared out the drivers using Driver Sweeper, and then re-installed them, but have experienced 2 Crashes today within 6 hours :(
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Which drivers did you install? In your next post attach your latest minidumps.
  7. SunDown

    SunDown Newcomer, in training Topic Starter

    I installed the Latest ATI Catalyst Drivers.

    I've attached my latest Minidump! =D

    Thanks <3

    Attached Files:

  8. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Run a virus scan, etc. The latest minidump was 0xD1 and these are uaually caused by faulty drivers but in your case it cited a Windows registry value. I personally have never seen this before but that doesn't mean it is uncommon.

    * Get back to us with the results. It you come up clean then perhasps the next step is a Windows repair.

    * If you know how run a harddrive diagnostics as well.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.