BSOD - nvm62x64.sys, ndis.sys and others...

Discussion in 'Windows 7 Help and Support' started by Charles Santos, May 15, 2011.

  1. Charles Santos

    Charles Santos New Member

    Joined:
    May 15, 2011
    Messages:
    8
    Likes Received:
    0
    Hello!

    I really don't know what to do, so I need your help!

    I have been getting random BSODs for almost two months now... I have tried everything, formatting and reinstalling Windows 7, have even downgraded to Windows Vista once, updated every driver I can find, scanned for viruses, spywares etc... and I can't find an answer! And I really need to fix this problem since I use my computer to work, and those damn BSOD are not letting me do any work anymore...

    I've opened some of the minidump files in the BlueScreenView.exe, and there are a number of different files that are responsible for the errors.

    I've also done many different tests to check if my memory, hard drive and CPU are fine, and so far they are okay, with no problems; So I have been thinking that this problem is definetely not hardware related!

    Another symptom is that the CPU and memory usage keep a bit high even when the system is idle; Temperatures also are a little bit high, but I have been managing this with a fan in front of the CPU, so I'm sure that the BSODs are not caused by overheating (I keep Speedfan opened to keep an eye on it)

    Other information:
    OS: Microsoft Windows 7 Ultimate 64-bit 6.1.7601 SP 1 Build 7601
    Processor: AMD Athlon 64 X2 4000+; 2,1 Ghz
    Memory: 3 Gb RAM
    GPU: GeForce 220 1Gb

    I'm also uploading the minidumps from TODAY only!

    I really appreciate your help, if you need more information just tell me!

    Thanks!
    Charles
     

    Attached Files:

  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Hello and Welcome. : )


    Your crashes are caused by nVidia nForce driver.


    1. Update nForce to the latest at nVidia's site
    nvflsh64.sys Fri Aug 01 14:08:23 2008



    2. Uninstall nVidia OC-ing System Utility Driver
    nvoclk64.sys Mon Aug 18 12:00:01 2008



    3. Replace AVG with MSE, if the blue screens persist

    AVG Worldwide - Download tools

    Virus, Spyware & Malware Protection | Microsoft Security Essentials




    CRASH DUMPS

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DMP\051511-30139-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    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 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053650
    Debug session time: Sun May 15 13:44:26.398 2011 (UTC - 4:00)
    System Uptime: 0 days 1:19:34.707
    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 D1, {48, 2, 1, fffff88006b05e83}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvmf6264.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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 : nvmf6264.sys ( nvmf6264+13e83 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000048, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88006b05e83, 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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.
    
    FAULTING_MODULE: fffff80002e0e000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a723142
    
    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     0000000000000048 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nvmf6264+13e83
    fffff880`06b05e83 743b            je      nvmf6264+0x13ec0 (fffff880`06b05ec0)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    LAST_CONTROL_TRANSFER:  from fffff80002e8d2a9 to fffff80002e8dd00
    
    STACK_TEXT:  
    fffff800`00ba2428 fffff800`02e8d2a9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000001 : nt+0x7fd00
    fffff800`00ba2430 00000000`0000000a : 00000000`00000048 00000000`00000002 00000000`00000001 fffff880`06b05e83 : nt+0x7f2a9
    fffff800`00ba2438 00000000`00000048 : 00000000`00000002 00000000`00000001 fffff880`06b05e83 00000000`047b6601 : 0xa
    fffff800`00ba2440 00000000`00000002 : 00000000`00000001 fffff880`06b05e83 00000000`047b6601 00000000`00000000 : 0x48
    fffff800`00ba2448 00000000`00000001 : fffff880`06b05e83 00000000`047b6601 00000000`00000000 00000000`00000000 : 0x2
    fffff800`00ba2450 fffff880`06b05e83 : 00000000`047b6601 00000000`00000000 00000000`00000000 00990022`002b0020 : 0x1
    fffff800`00ba2458 00000000`047b6601 : 00000000`00000000 00000000`00000000 00990022`002b0020 002a0000`00050002 : nvmf6264+0x13e83
    fffff800`00ba2460 00000000`00000000 : 00000000`00000000 00990022`002b0020 002a0000`00050002 00000000`00000000 : 0x47b6601
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvmf6264+13e83
    fffff880`06b05e83 743b            je      nvmf6264+0x13ec0 (fffff880`06b05ec0)
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  nvmf6264+13e83
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvmf6264
    
    IMAGE_NAME:  nvmf6264.sys
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DMP\051511-28501-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    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 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`03094650
    Debug session time: Sun May 15 14:01:33.213 2011 (UTC - 4:00)
    System Uptime: 0 days 0:16:22.523
    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 D1, {fa0, 2, 1, fffff88003b4fe83}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvmf6264.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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 : nvmf6264.sys ( nvmf6264+13e83 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000fa0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88003b4fe83, 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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.
    
    FAULTING_MODULE: fffff80002e4f000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a723142
    
    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     0000000000000fa0 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nvmf6264+13e83
    fffff880`03b4fe83 743b            je      nvmf6264+0x13ec0 (fffff880`03b4fec0)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    LAST_CONTROL_TRANSFER:  from fffff80002ece2a9 to fffff80002eced00
    
    STACK_TEXT:  
    fffff800`00b9c1f8 fffff800`02ece2a9 : 00000000`0000000a 00000000`00000fa0 00000000`00000002 00000000`00000001 : nt+0x7fd00
    fffff800`00b9c200 00000000`0000000a : 00000000`00000fa0 00000000`00000002 00000000`00000001 fffff880`03b4fe83 : nt+0x7f2a9
    fffff800`00b9c208 00000000`00000fa0 : 00000000`00000002 00000000`00000001 fffff880`03b4fe83 fffff800`00b97000 : 0xa
    fffff800`00b9c210 00000000`00000002 : 00000000`00000001 fffff880`03b4fe83 fffff800`00b97000 00000000`00000000 : 0xfa0
    fffff800`00b9c218 00000000`00000001 : fffff880`03b4fe83 fffff800`00b97000 00000000`00000000 00000000`00000000 : 0x2
    fffff800`00b9c220 fffff880`03b4fe83 : fffff800`00b97000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
    fffff800`00b9c228 fffff800`00b97000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvmf6264+0x13e83
    fffff800`00b9c230 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00b97000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvmf6264+13e83
    fffff880`03b4fe83 743b            je      nvmf6264+0x13ec0 (fffff880`03b4fec0)
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  nvmf6264+13e83
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvmf6264
    
    IMAGE_NAME:  nvmf6264.sys
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DMP\051511-38719-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    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 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053650
    Debug session time: Sun May 15 15:02:03.702 2011 (UTC - 4:00)
    System Uptime: 0 days 0:01:06.012
    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 D1, {fffffa8013b8230e, e, 1, fffff8800f55df3f}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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 : nvlddmkm.sys ( nvlddmkm+4eef3f )
    
    Followup: MachineOwner
    ---------
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DMP\051511-29749-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`0305b650
    Debug session time: Sun May 15 15:48:44.090 2011 (UTC - 4:00)
    System Uptime: 0 days 0:34:27.400
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** 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 1E, {0, 0, 0, 0}
    
    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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+7fcd0 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    The system cannot find the file specified.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: fffff80002e16000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +3334333830373266
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    
    BUGCHECK_STR:  0x1E_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002e8d6be to fffff80002e95cd0
    
    STACK_TEXT:  
    fffff800`00b9b2f8 fffff800`02e8d6be : fffff880`01863ebc fffff880`01863ebc fffff800`00b9ba70 fffff800`02ec1890 : nt+0x7fcd0
    fffff800`00b9b300 fffff880`01863ebc : fffff880`01863ebc fffff800`00b9ba70 fffff800`02ec1890 00000000`00000000 : nt+0x776be
    fffff800`00b9b308 fffff880`01863ebc : fffff800`00b9ba70 fffff800`02ec1890 00000000`00000000 fffff800`02ec155d : tcpip!LowMemoryEvent <PERF> (tcpip+0x1abebc)
    fffff800`00b9b310 fffff800`00b9ba70 : fffff800`02ec1890 00000000`00000000 fffff800`02ec155d fffff800`0309c968 : tcpip!LowMemoryEvent <PERF> (tcpip+0x1abebc)
    fffff800`00b9b318 fffff800`02ec1890 : 00000000`00000000 fffff800`02ec155d fffff800`0309c968 fffff800`02fd9cbc : 0xfffff800`00b9ba70
    fffff800`00b9b320 00000000`00000000 : fffff800`02ec155d fffff800`0309c968 fffff800`02fd9cbc fffff800`02e16000 : nt+0xab890
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt+7fcd0
    fffff800`02e95cd0 4883ec28        sub     rsp,28h
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt+7fcd0
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    
    
    
    




    DRIVERS

    Code:
    start             end                 module name
    fffff880`06c06000 fffff880`06c44000   1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8)
    fffff880`00f1d000 fffff880`00f74000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
    fffff880`03e9c000 fffff880`03f25000   afd      afd.sys      Sat Nov 20 04:23:27 2010 (4CE7938F)
    fffff880`0fddf000 fffff880`0fdf5000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
    fffff880`03bc9000 fffff880`03be0000   amdk8    amdk8.sys    Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    fffff880`01101000 fffff880`0110c000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    fffff880`08f91000 fffff880`08f9c000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
    fffff880`00ff1000 fffff880`00ffa000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00c00000 fffff880`00c2a000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
    fffff960`00990000 fffff960`009f1000   ATMFD    ATMFD.DLL    unavailable (00000000)
    fffff880`08992000 fffff880`089bd000   AVGIDSDriver AVGIDSDriver.Sys Thu Apr 14 13:11:05 2011 (4DA72AA9)
    fffff880`0168c000 fffff880`01696000   AVGIDSEH AVGIDSEH.Sys Tue Feb 22 00:23:04 2011 (4D634838)
    fffff880`04671000 fffff880`0467c000   AVGIDSFilter AVGIDSFilter.Sys Wed Feb 09 23:59:37 2011 (4D5370B9)
    fffff880`03b54000 fffff880`03ba3000   avgldx64 avgldx64.sys Thu Jan 06 23:36:39 2011 (4D269857)
    fffff880`03cf3000 fffff880`03d02000   avgmfx64 avgmfx64.sys Tue Mar 01 07:25:15 2011 (4D6CE5AB)
    fffff880`01680000 fffff880`0168c000   avgrkx64 avgrkx64.sys Wed Mar 16 10:06:34 2011 (4D80C3EA)
    fffff880`03c00000 fffff880`03c60000   avgtdia  avgtdia.sys  Mon Apr 04 17:54:35 2011 (4D9A3E1B)
    fffff880`03d0b000 fffff880`03d12000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`03b43000 fffff880`03b54000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
    fffff880`04771000 fffff880`0478f000   bowser   bowser.sys   Tue Feb 22 23:55:04 2011 (4D649328)
    fffff960`00720000 fffff960`00747000   cdd      cdd.dll      unavailable (00000000)
    fffff880`03cc9000 fffff880`03cf3000   cdrom    cdrom.sys    Sat Nov 20 04:19:20 2010 (4CE79298)
    fffff880`00d06000 fffff880`00dc6000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
    fffff880`01650000 fffff880`01680000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
    fffff880`00ca8000 fffff880`00d06000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`01457000 fffff880`014c9000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
    fffff880`0fdcf000 fffff880`0fddf000   CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED)
    fffff880`08f88000 fffff880`08f91000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
    fffff880`07366000 fffff880`07374000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`03aa2000 fffff880`03b25000   csc      csc.sys      Sat Nov 20 04:27:12 2010 (4CE79470)
    fffff880`03b25000 fffff880`03b43000   dfsc     dfsc.sys     Sat Nov 20 04:26:31 2010 (4CE79447)
    fffff880`03e68000 fffff880`03e77000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
    fffff880`0163a000 fffff880`01650000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`072af000 fffff880`072d1000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
    fffff880`03f63000 fffff880`03fa6000   dtsoftbus01 dtsoftbus01.sys Thu Jan 13 03:27:08 2011 (4D2EB75C)
    fffff880`07374000 fffff880`0737e000   dump_diskdump dump_diskdump.sys Sat Nov 20 05:33:56 2010 (4CE7A414)
    fffff880`073bc000 fffff880`073cf000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`0737e000 fffff880`073bc000   dump_nvstor64 dump_nvstor64.sys Mon Jun 22 18:23:37 2009 (4A400469)
    fffff880`073cf000 fffff880`073db000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
    fffff880`0fcdb000 fffff880`0fdcf000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 04:50:50 2010 (4CE799FA)
    fffff880`06cba000 fffff880`06d00000   dxgmms1  dxgmms1.sys  Sat Nov 20 04:49:53 2010 (4CE799C1)
    fffff880`01158000 fffff880`0116c000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`0110c000 fffff880`01158000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
    fffff880`014da000 fffff880`014e4000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`01600000 fffff880`0163a000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
    fffff880`018bc000 fffff880`01906000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
    fffff800`033ff000 fffff800`03448000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
    fffff880`06c44000 fffff880`06c68000   HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E)
    fffff880`0731b000 fffff880`07334000   HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665)
    fffff880`07334000 fffff880`0733c080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
    fffff880`07408000 fffff880`07416000   hidusb   hidusb.sys   Sat Nov 20 05:43:49 2010 (4CE7A665)
    fffff880`046a8000 fffff880`04771000   HTTP     HTTP.sys     Sat Nov 20 04:24:30 2010 (4CE793CE)
    fffff880`019c0000 fffff880`019c9000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
    fffff880`06d85000 fffff880`06d94000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`0733d000 fffff880`0734b000   kbdhid   kbdhid.sys   Sat Nov 20 05:33:25 2010 (4CE7A3F5)
    fffff800`00bc5000 fffff800`00bcf000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
    fffff880`06da3000 fffff880`06de6000   ks       ks.sys       Sat Nov 20 05:33:23 2010 (4CE7A3F3)
    fffff880`013d3000 fffff880`013ee000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
    fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
    fffff880`07400000 fffff880`07405200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
    fffff880`03a8a000 fffff880`03a9f000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`03a67000 fffff880`03a8a000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
    fffff880`00c87000 fffff880`00c94000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
    fffff880`073e8000 fffff880`073f6000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
    fffff880`06d94000 fffff880`06da3000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`073db000 fffff880`073e8000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff880`00dd6000 fffff880`00df0000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
    fffff880`0478f000 fffff880`047a7000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
    fffff880`047a7000 fffff880`047d4000   mrxsmb   mrxsmb.sys   Tue Feb 22 23:56:22 2011 (4D649376)
    fffff880`04600000 fffff880`0464d000   mrxsmb10 mrxsmb10.sys Tue Feb 22 23:55:12 2011 (4D649330)
    fffff880`0464d000 fffff880`04671000   mrxsmb20 mrxsmb20.sys Tue Feb 22 23:55:12 2011 (4D649330)
    fffff880`03d70000 fffff880`03d7b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00f7d000 fffff880`00f87000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`0116c000 fffff880`011ca000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
    fffff880`03e5d000 fffff880`03e68000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
    fffff880`019ae000 fffff880`019c0000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`014e4000 fffff880`015d7000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
    fffff880`0f024000 fffff880`0f030000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
    fffff880`06d00000 fffff880`06d2f000   ndiswan  ndiswan.sys  Sat Nov 20 05:52:32 2010 (4CE7A870)
    fffff880`0725d000 fffff880`07272000   NDProxy  NDProxy.SYS  Sat Nov 20 05:52:20 2010 (4CE7A864)
    fffff880`03f54000 fffff880`03f63000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`03dbb000 fffff880`03e00000   netbt    netbt.sys    Sat Nov 20 04:23:18 2010 (4CE79386)
    fffff880`01000000 fffff880`01060000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
    fffff880`03d7b000 fffff880`03d8c000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`03e51000 fffff880`03e5d000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
    fffff800`02e16000 fffff800`033ff000   nt       ntoskrnl.exe Sat Apr 09 00:15:23 2011 (4D9FDD5B)
    fffff880`01230000 fffff880`013d3000   Ntfs     Ntfs.sys     Sat Nov 20 04:20:57 2010 (4CE792F9)
    fffff880`03d02000 fffff880`03d0b000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`0fcd9000 fffff880`0fcda180   nvBridge nvBridge.kmd Thu Apr 07 23:14:49 2011 (4D9E7DA9)
    fffff880`0467c000 fffff880`0468b000   nvflsh64 nvflsh64.sys Fri Aug 01 14:08:23 2008 (48935117)
    fffff880`072d1000 fffff880`072fe000   nvhda64v nvhda64v.sys Thu Mar 03 10:59:02 2011 (4D6FBAC6)
    fffff880`0f034000 fffff880`0fcd8300   nvlddmkm nvlddmkm.sys Thu Apr 07 23:22:12 2011 (4D9E7F64)
    fffff880`06c68000 fffff880`06cb9500   nvmf6264 nvmf6264.sys Thu Jul 30 19:48:18 2009 (4A723142)
    fffff880`08ed7000 fffff880`08ee6000   nvoclk64 nvoclk64.sys Mon Aug 18 12:00:01 2008 (48A99C81)
    fffff880`00c2a000 fffff880`00c55000   nvstor   nvstor.sys   Fri Mar 19 16:45:11 2010 (4BA3E257)
    fffff880`010c3000 fffff880`01101000   nvstor64 nvstor64.sys Mon Jun 22 18:23:37 2009 (4A400469)
    fffff880`03f2e000 fffff880`03f54000   pacer    pacer.sys    Sat Nov 20 05:52:18 2010 (4CE7A862)
    fffff880`00fc7000 fffff880`00fdc000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
    fffff880`00f87000 fffff880`00fba000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
    fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
    fffff880`00dc6000 fffff880`00dd6000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`014c9000 fffff880`014da000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`0889e000 fffff880`08944000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
    fffff880`07272000 fffff880`072af000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00c94000 fffff880`00ca8000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`0f000000 fffff880`0f024000   rasl2tp  rasl2tp.sys  Sat Nov 20 05:52:34 2010 (4CE7A872)
    fffff880`06d2f000 fffff880`06d4a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
    fffff880`06d4a000 fffff880`06d6b000   raspptp  raspptp.sys  Sat Nov 20 05:52:31 2010 (4CE7A86F)
    fffff880`06d6b000 fffff880`06d85000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
    fffff880`03e00000 fffff880`03e51000   rdbss    rdbss.sys    Sat Nov 20 04:27:51 2010 (4CE79497)
    fffff880`0fdf5000 fffff880`0fe00000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
    fffff880`03d55000 fffff880`03d5e000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`03d5e000 fffff880`03d67000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`03d67000 fffff880`03d70000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`01974000 fffff880`019ae000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
    fffff880`03fd5000 fffff880`03fed000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`0741d000 fffff880`075fd400   RTKVHD64 RTKVHD64.sys Tue Aug 04 05:50:52 2009 (4A78047C)
    fffff880`08944000 fffff880`0894f000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`0196a000 fffff880`01974000   speedfan speedfan.sys Sat Dec 18 06:03:51 2010 (4D0C9517)
    fffff880`01962000 fffff880`0196a000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`08f17000 fffff880`08f88000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
    fffff880`08e3f000 fffff880`08ed7000   srv      srv.sys      Tue Feb 22 23:56:21 2011 (4D649375)
    fffff880`08800000 fffff880`0886a000   srv2     srv2.sys     Tue Feb 22 23:56:00 2011 (4D649360)
    fffff880`0894f000 fffff880`08980000   srvnet   srvnet.sys   Tue Feb 22 23:55:44 2011 (4D649350)
    fffff880`01060000 fffff880`010c3000   storport storport.sys Sat Nov 20 05:35:02 2010 (4CE7A456)
    fffff880`0f030000 fffff880`0f031480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
    fffff880`016b8000 fffff880`018bc000   tcpip    tcpip.sys    Sat Nov 20 04:25:52 2010 (4CE79420)
    fffff880`08980000 fffff880`08992000   tcpipreg tcpipreg.sys Sat Nov 20 05:51:48 2010 (4CE7A844)
    fffff880`03dae000 fffff880`03dbb000   TDI      TDI.SYS      Sat Nov 20 04:22:06 2010 (4CE7933E)
    fffff880`03d8c000 fffff880`03dae000   tdx      tdx.sys      Sat Nov 20 04:21:54 2010 (4CE79332)
    fffff880`03fc1000 fffff880`03fd5000   termdd   termdd.sys   Sat Nov 20 06:03:40 2010 (4CE7AB0C)
    fffff960`00430000 fffff960`0043a000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff880`03ba3000 fffff880`03bc9000   tunnel   tunnel.sys   Sat Nov 20 05:51:50 2010 (4CE7A846)
    fffff880`06de6000 fffff880`06df8000   umbus    umbus.sys    Sat Nov 20 05:44:37 2010 (4CE7A695)
    fffff880`072fe000 fffff880`0731b000   usbccgp  usbccgp.sys  Sat Nov 20 05:44:03 2010 (4CE7A673)
    fffff880`07406000 fffff880`07407f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
    fffff880`03a56000 fffff880`03a67000   usbehci  usbehci.sys  Sat Nov 20 05:43:54 2010 (4CE7A66A)
    fffff880`07203000 fffff880`0725d000   usbhub   usbhub.sys   Sat Nov 20 05:44:30 2010 (4CE7A68E)
    fffff880`03be0000 fffff880`03beb000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
    fffff880`03a00000 fffff880`03a56000   USBPORT  USBPORT.SYS  Sat Nov 20 05:44:00 2010 (4CE7A670)
    fffff880`0734b000 fffff880`07366000   USBSTOR  USBSTOR.SYS  Sat Nov 20 05:44:05 2010 (4CE7A675)
    fffff880`00fba000 fffff880`00fc7000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`03d12000 fffff880`03d20000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`03d20000 fffff880`03d45000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`01906000 fffff880`01916000   vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A)
    fffff880`00fdc000 fffff880`00ff1000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
    fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
    fffff880`01916000 fffff880`01962000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
    fffff880`03fa6000 fffff880`03fc1000   wanarp   wanarp.sys   Sat Nov 20 05:52:36 2010 (4CE7A874)
    fffff880`03d45000 fffff880`03d55000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`00e6a000 fffff880`00f0e000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00f0e000 fffff880`00f1d000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`03f25000 fffff880`03f2e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff960`000b0000 fffff960`003c2000   win32k   win32k.sys   unavailable (00000000)
    fffff880`00f74000 fffff880`00f7d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`03e77000 fffff880`03e98000   WudfPf   WudfPf.sys   Sat Nov 20 05:42:44 2010 (4CE7A624)
    fffff880`08ee6000 fffff880`08f17000   WUDFRd   WUDFRd.sys   Sat Nov 20 05:43:32 2010 (4CE7A654)
    
    Unloaded modules:
    fffff880`08f17000 fffff880`08f88000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00071000
    fffff880`01696000 fffff880`016a4000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`016a4000 fffff880`016ae000   dump_storpor
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000A000
    fffff880`03c78000 fffff880`03cb6000   dump_nvstor6
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0003E000
    fffff880`03cb6000 fffff880`03cc9000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    
    
     
  3. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Well done, actually. Overheating can cause bsod's too.
     
  4. Charles Santos

    Charles Santos New Member

    Joined:
    May 15, 2011
    Messages:
    8
    Likes Received:
    0
    Thanks mate, will try that out!
     
  5. Charles Santos

    Charles Santos New Member

    Joined:
    May 15, 2011
    Messages:
    8
    Likes Received:
    0
    Well, I have tried everything, but number 1, and the BSOD are still here...

    Before coming here I was almost 100% sure that the problem was with my nForce drivers... The big problem is that Nvidia does not makes the driver I need for Windows 7, so I will try to create a partition, install Windows Vista or XP, upgrade and then erase the partition... is that okay, do you think it will work??

    Regarding the overheating, what I meant is that I was keeping an eye in the temperature, so my PC wasn't overheating at all, specially now that I have the fan in front of the CPU; Bad choice of words I guess, English is not my mother language!
     
  6. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    No, your choice of words is excellent, it's very circumspect of you to have taken care of that because overheating causes a lot of problems including blue screens of death (BSOD). Overheating is almost equal to faulty hardware. And I only wanted to point to the importance of proper cooling.

    Speedfan, yes, I see yours is the 2010 version and it's good. Keep using it.





    Well you could try XP or Vista, and another route is to borrow nvm62x64.sys from a higher nForce version that you can download for a newer nForce motherboard. Again, download from nVidia site, not from ASUS. Unpack the archive and search for nvm62x64.sys. Copy out and paste it into C:\Windows\system32\drivers.


    If bsod's persist despite all the efforts, attach this:

    - screenshot of cpu-z MEMORY tab
    - screenshot of cpu-z CPU tab
    - Passmark RAMMon HTML.zip

    The hardware should not be overclocked and RAM should be set up to its rates as advised by the manufacturer - frequency/timings/voltage.
    Sometimes loading bios defaults will adjust hardware to its proper settings.

    Good luck and keep us updated.
     
  7. Charles Santos

    Charles Santos New Member

    Joined:
    May 15, 2011
    Messages:
    8
    Likes Received:
    0
    Thanks for your help, I will try to borrow the nvm62x64.sys from the newer nForce motherboards, I think this might work!
     

Share This Page

Loading...