BSOD when I play games: "probably caused by ntoskrnl.exe"

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Urgo, Oct 29, 2010.

  1. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    Hi!

    I've started to have decent problems with BSOD's since about 2-3 weeks ago. It only happen when I play games. Practically, Warcraft 3 and NFS Shift.

    Some time before that i got some BSODs in NFS Shift only with announcement of atikmdag.sys as a cause. But I got rid of that by reinstalling video drivers.

    At the moment all of my BSODs are "probably caused by: ntoskrnl.exe". I found out it using WinDbg tool: (the latest log)

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\102810-26052-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
    Debug session time: Thu Oct 28 23:48:56.589 2010 (UTC + 4:00)
    System Uptime: 0 days 0:31:04.321
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {61, 0, fffff880009e9180, 1}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880009e9180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    
    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    
    MODULE_NAME: nt
    
    FAULTING_MODULE: fffff80002a14000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff800`00b9c938 fffff800`02a32453 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e9180 : nt+0x70740
    fffff800`00b9c940 00000000`00000101 : 00000000`00000061 00000000`00000000 fffff880`009e9180 00000000`00000001 : nt+0x1e453
    fffff800`00b9c948 00000000`00000061 : 00000000`00000000 fffff880`009e9180 00000000`00000001 fffff880`00f07ac5 : 0x101
    fffff800`00b9c950 00000000`00000000 : fffff880`009e9180 00000000`00000001 fffff880`00f07ac5 00000001`00000000 : 0x61
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    
    
    I think I have troubles with the symbols for the tool but, anyway, it says ntoskrnl.exe is the problem.

    I've already used Driver verfier and it found two unassigned drivers: atikmdag.sys and atikmpag.sys.
    I just reinstalled all the video drivers to resolve the problem. But it didn't help.

    Please, if you have any information that might help, let me know.
    Thank you.
    View attachment Minidump.rar
     
    #1 Urgo, Oct 29, 2010
    Last edited by a moderator: Oct 29, 2010
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Hey, welcome.

    1) Update audio driver from motherboard website:

    stwrt64 stwrt64.sys Wed Jun 10 02:06:52 2009

    2) Update lan driver from motherboard website:

    l260x64 l260x64.sys Tue Mar 17 06:00:35 2009

    3) Update AMD video card driver:

    atikmdag atikmdag.sys Wed Aug 25 21:47:22 2010

    Drivers & Support | GAME.AMD.COM

    4) Uninstall notorious Daemon Tools. Then use this installer/uninstaller to remove sptd.sys (do not update instead, while using):

    DuplexSecure - Downloads

    Reboot and install PowerISO to replace it. Disc emulation part of it is free forever:

    PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive

    5) Uninstall VirtualCD. The driver is way too old for Windows 7:

    vdrv9000 vdrv9000.sys Thu Nov 08 03:05:16 2007

    -------

    Follow that all well and it will be well. Enjoy.
     
  3. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    Thanks!

    I will follow your instructions and inform if anything goes wrong again.
     
  4. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    I followed your instructions but BSOD appeared again when i was playing.
    And 2 more when i was posting on the forum.

    I think the two last of them appeared because system was busy with utorrent.exe that was, in its turn, checking the current downloads after BSOD.

    View attachment Minidump.rar
     
  5. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Update the motherboard bios to newest. Then set the optimized defaults in the bios and save. If there is any overclocking currently which may be causing this, it will alleviate that. If you're overclocking the video card, don't do that either, until everything is figured out.

    There was a failure in the cpu driver.

    -------

    This driver is older now and not well:

    l260x64 l260x64.sys Fri Oct 17 02:17:10 2008

    Which motherboard do you have? I'll see what I can do.

    Also, this driver has not been updated:

    stwrt64 stwrt64.sys Wed Jun 10 02:06:52 2009
     
  6. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    Ok, will update the motherboard driver.

    No, i'm not overcklocking CPU or video or anything else.

    stwrt64.sys - updated from the manufacturer's website.
    l260x64.sys - same thing.

    I also checked if there any update via devices manager from Windows and it detected an update for lan driver.

    My motherboard:
    ECS A740GM-M v1.0
     
  7. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Never do that from device manager or accept drivers from Windows Update. Not a good thing at all. Always from manufacturers' sites.

    Update the motherboard bios (not driver.)

    --------

    Install this for the Atheros lan driver. It is the absolute newest:

    Atheros Communications
     
  8. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    Oh, I misread that.

    I got 4 more BSODs: 2 when was trying to update the chipset driver and 2 when was trying to launch the bios flashing utility.
    View attachment Minidump.rar
     
  9. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Uninstall the Windows flash utility. Then check C:\Windows\System32\drivers for UCOREW64.SYS

    If it is there, delete it.

    It's causing crashes.

    ------

    Update the Atheros driver from my previous post.

    ------

    Update bios from dos by booting to dos media, instead. I haven't said anything about any chipset drivers. Leave them as is.
     
  10. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Also delete this entire folder:

    D:\Downloads\Drivers\W7Vista_121am
     
  11. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
  12. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    And the 2 other crashes were caused by ATI DSM Dynamic Driver

    atdcm64a.sys July 2009
     
  13. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\102910-25303-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: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a12000 PsLoadedModuleList = 0xfffff800`02c4fe50
    Debug session time: Fri Oct 29 15:39:15.447 2010 (UTC - 5:00)
    System Uptime: 0 days 0:48:21.055
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {20e, fffff88006781432, fffff9804b24ae10, 0}
    
    Unable to load image \??\D:\Downloads\Drivers\W7Vista_121am\W7Vista_121am\Bin64\atdcm64a.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atdcm64a.sys
    *** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
    Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 000000000000020e, A PNP IRP has an invalid status. Any PNP IRP must have its status initialized
        to STATUS_NOT_SUPPORTED.
    Arg2: fffff88006781432, The address in the driver's code where the error was detected.
    Arg3: fffff9804b24ae10, IRP address.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_20e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  20e
    
    FAULTING_IP: 
    atdcm64a+2432
    fffff880`06781432 89442478        mov     dword ptr [rsp+78h],eax
    
    FOLLOWUP_IP: 
    atdcm64a+2432
    fffff880`06781432 89442478        mov     dword ptr [rsp+78h],eax
    
    IRP_ADDRESS:  fffff9804b24ae10
    
    DEVICE_OBJECT: 0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  InstallManager
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002f0c3dc to fffff80002a82740
    
    STACK_TEXT:  
    fffff880`07427418 fffff800`02f0c3dc : 00000000`000000c9 00000000`0000020e fffff880`06781432 fffff980`4b24ae10 : nt!KeBugCheckEx
    fffff880`07427420 fffff800`02f1647a : fffff800`02f0a9f0 fffff880`06781432 fffff980`4b24ae10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`07427460 fffff800`02f17483 : 00000000`0000020e 00000000`00000000 fffff980`4b24ae10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`074274b0 fffff800`02f18115 : 00000000`00000000 fffffa80`0188c502 fffff980`4b24ae10 fffff800`02f0de56 : nt!VfErrorReport1+0x63
    fffff880`07427550 fffff800`02f0c1e0 : fffff980`4b24afb8 fffffa80`045ce010 00000000`00000000 fffff800`02f1ae3f : nt!VfPnpVerifyNewRequest+0x45
    fffff880`07427580 fffff800`02f24b33 : fffffa80`0188c560 fffffa80`045ce010 fffff980`4b24ae10 fffffa80`04351240 : nt!VfMajorVerifyNewRequest+0x70
    fffff880`074275d0 fffff800`02f24d86 : fffff880`00000001 fffffa80`00000001 fffffa80`00000001 fffff880`06781432 : nt!IovpCallDriver1+0x483
    fffff880`07427680 fffff800`02f28bb2 : fffff980`4b24ae10 00000000`00000002 fffff980`4b24ae10 fffff800`02cef00c : nt!VfBeforeCallDriver+0x186
    fffff880`074276e0 fffff880`06781432 : fffff980`4bca2ee0 00000000`00000002 fffffa80`03bf0170 fffffa80`02f9c990 : nt!IovCallDriver+0x502
    fffff880`07427740 fffff980`4bca2ee0 : 00000000`00000002 fffffa80`03bf0170 fffffa80`02f9c990 00000000`00000000 : atdcm64a+0x2432
    fffff880`07427748 00000000`00000002 : fffffa80`03bf0170 fffffa80`02f9c990 00000000`00000000 fffff880`074277a0 : 0xfffff980`4bca2ee0
    fffff880`07427750 fffffa80`03bf0170 : fffffa80`02f9c990 00000000`00000000 fffff880`074277a0 fffff880`07427790 : 0x2
    fffff880`07427758 fffffa80`02f9c990 : 00000000`00000000 fffff880`074277a0 fffff880`07427790 00000000`00000000 : 0xfffffa80`03bf0170
    fffff880`07427760 00000000`00000000 : fffff880`074277a0 fffff880`07427790 00000000`00000000 fffff980`4b24ae10 : 0xfffffa80`02f9c990
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  atdcm64a+2432
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atdcm64a
    
    IMAGE_NAME:  atdcm64a.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a43f28f
    
    FAILURE_BUCKET_ID:  X64_0xc9_20e_VRF_atdcm64a+2432
    
    BUCKET_ID:  X64_0xc9_20e_VRF_atdcm64a+2432
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\103010-41636-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: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50
    Debug session time: Fri Oct 29 16:13:54.916 2010 (UTC - 5:00)
    System Uptime: 0 days 0:05:32.649
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {f6, 150, fffffa80029d8060, fffff8800638afd8}
    
    Unable to load image \??\D:\Downloads\Drivers\A74M0507\UCOREW64.SYS, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for UCOREW64.SYS
    Probably caused by : UCOREW64.SYS ( UCOREW64+fd8 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000f6, Referencing user handle as KernelMode.
    Arg2: 0000000000000150, Handle value being referenced.
    Arg3: fffffa80029d8060, Address of the current process.
    Arg4: fffff8800638afd8, Address inside the driver that is performing the incorrect reference.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_f6
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  AFUWIN.EXE
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002f043dc to fffff80002a7a740
    
    STACK_TEXT:  
    fffff880`072d4548 fffff800`02f043dc : 00000000`000000c4 00000000`000000f6 00000000`00000150 fffffa80`029d8060 : nt!KeBugCheckEx
    fffff880`072d4550 fffff800`02f19ae4 : 00000000`00000150 fffffa80`029d8060 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`072d4590 fffff800`02cd5b40 : 00000065`00000003 fffff880`072d47c0 00000000`00000000 fffff980`1c9a2f00 : nt!VfCheckUserHandle+0x1b4
    fffff880`072d4670 fffff800`02d515f5 : 00000000`00000000 fffff880`000f001f 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
    fffff880`072d4740 fffff800`02f19878 : fffff980`1c9a2fe0 fffff980`1c9a2ff0 fffff980`1c9a2fe0 fffff800`02a75f30 : nt!ObReferenceObjectByHandle+0x25
    fffff880`072d4790 fffff880`0638afd8 : 00000000`0000ffff fffff980`1c9a2ff0 fffff980`1c9a2fe0 fffff980`1c9a2fe0 : nt!VerifierObReferenceObjectByHandle+0x48
    fffff880`072d47e0 00000000`0000ffff : fffff980`1c9a2ff0 fffff980`1c9a2fe0 fffff980`1c9a2fe0 fffff880`072d4860 : UCOREW64+0xfd8
    fffff880`072d47e8 fffff980`1c9a2ff0 : fffff980`1c9a2fe0 fffff980`1c9a2fe0 fffff880`072d4860 00000000`00000000 : 0xffff
    fffff880`072d47f0 fffff980`1c9a2fe0 : fffff980`1c9a2fe0 fffff880`072d4860 00000000`00000000 fffff800`02d95707 : 0xfffff980`1c9a2ff0
    fffff880`072d47f8 fffff980`1c9a2fe0 : fffff880`072d4860 00000000`00000000 fffff800`02d95707 fffffa80`02701e90 : 0xfffff980`1c9a2fe0
    fffff880`072d4800 fffff880`072d4860 : 00000000`00000000 fffff800`02d95707 fffffa80`02701e90 fffffa80`029300d8 : 0xfffff980`1c9a2fe0
    fffff880`072d4808 00000000`00000000 : fffff800`02d95707 fffffa80`02701e90 fffffa80`029300d8 fffffa80`0299c3e0 : 0xfffff880`072d4860
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    UCOREW64+fd8
    fffff880`0638afd8 85c0            test    eax,eax
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  UCOREW64+fd8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: UCOREW64
    
    IMAGE_NAME:  UCOREW64.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  44224a2b
    
    FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_UCOREW64+fd8
    
    BUCKET_ID:  X64_0xc4_f6_VRF_UCOREW64+fd8
    
    Followup: MachineOwner
    
    
    
    
    fffff880`0638a000 fffff880`0638bf00   UCOREW64   (no symbols)           
        Loaded symbol image file: UCOREW64.SYS
        Image path: \??\D:\Downloads\Drivers\A74M0507\UCOREW64.SYS
        Image name: UCOREW64.SYS
        Timestamp:        Thu Mar 23 03:11:39 2006 (44224A2B)
    
    
    
    
    fffff880`06000000 fffff880`0602b000   000      000.fcl      Fri Sep 26 09:11:22 2008 (48DCDF7A)
    fffff880`00e10000 fffff880`00e67000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
    fffff880`0184c000 fffff880`018d6000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`04fd9000 fffff880`04fef000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
    fffff880`03fa4000 fffff880`03fbb000   amdk8    amdk8.sys    Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    fffff880`00fa4000 fffff880`00faf000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
    fffff880`00f71000 fffff880`00f7a000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00f7a000 fffff880`00fa4000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
    fffff880`0432f000 fffff880`0434f000   AtihdW76 AtihdW76.sys Mon Aug 16 06:41:02 2010 (4C6915BE)
    fffff880`04803000 fffff880`04fd9000   atikmdag atikmdag.sys Tue Sep 28 21:41:26 2010 (4CA29946)
    fffff880`03e00000 fffff880`03e4b000   atikmpag atikmpag.sys Tue Sep 28 21:14:49 2010 (4CA29309)
    fffff960`00860000 fffff960`008c1000   ATMFD    ATMFD.DLL    Thu May 27 00:11:31 2010 (4BFDF0F3)
    fffff880`019ac000 fffff880`019b3000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`03f6d000 fffff880`03f7e000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
    fffff880`03908000 fffff880`03926000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
    fffff960`00750000 fffff960`00777000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
    fffff880`01979000 fffff880`019a3000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00c97000 fffff880`00d57000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
    fffff880`01913000 fffff880`01943000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00c39000 fffff880`00c97000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`01321000 fffff880`01394000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
    fffff880`03de6000 fffff880`03df6000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`057b8000 fffff880`057c6000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`03ecc000 fffff880`03f4f000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
    fffff880`03f4f000 fffff880`03f6d000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
    fffff880`02db9000 fffff880`02dc8000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
    fffff880`018fd000 fffff880`01913000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`0438c000 fffff880`043ae000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
    fffff880`057d2000 fffff880`057db000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`057c6000 fffff880`057d2000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`057db000 fffff880`057ee000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`0108a000 fffff880`010b5000   dwprot   dwprot.sys   Mon Jul 26 08:54:08 2010 (4C4D8570)
    fffff880`057ac000 fffff880`057b8000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
    fffff880`03c52000 fffff880`03d46000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
    fffff880`03d46000 fffff880`03d8c000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
    fffff880`01058000 fffff880`0106c000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`00faf000 fffff880`00ffb000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
    fffff880`0142b000 fffff880`01435000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`011bd000 fffff880`011f7000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
    fffff880`01173000 fffff880`011bd000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
    fffff800`02fe6000 fffff800`0302f000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
    fffff880`03d8c000 fffff880`03db0000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
    fffff880`0576f000 fffff880`05788000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
    fffff880`05788000 fffff880`05790080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
    fffff880`05761000 fffff880`0576f000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
    fffff880`03840000 fffff880`03908000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
    fffff880`015f3000 fffff880`015fc000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
    fffff880`03c00000 fffff880`03c1e000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`03c1e000 fffff880`03c2d000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`05791000 fffff880`0579f000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff800`00bd5000 fffff800`00bdf000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
    fffff880`0426b000 fffff880`042ae000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
    fffff880`01400000 fffff880`0141a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
    fffff880`01394000 fffff880`013bf000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
    fffff880`043ae000 fffff880`043b3200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
    fffff880`03db0000 fffff880`03dbe000   l260x64  l260x64.sys  Fri Oct 17 02:17:10 2008 (48F82DE6)
    fffff880`05644000 fffff880`05659000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`05600000 fffff880`05623000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
    fffff880`00c18000 fffff880`00c25000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
    fffff880`057ee000 fffff880`057fc000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
    fffff880`02c3b000 fffff880`02c4a000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`0579f000 fffff880`057ac000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff880`00f57000 fffff880`00f71000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`03926000 fffff880`0393e000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
    fffff880`0393e000 fffff880`0396b000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
    fffff880`0396b000 fffff880`039b9000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
    fffff880`039b9000 fffff880`039dc000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
    fffff880`01812000 fffff880`0181d000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00e70000 fffff880`00e7a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`010b5000 fffff880`01113000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
    fffff880`02dae000 fffff880`02db9000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
    fffff880`01200000 fffff880`01212000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`01222000 fffff880`01314000   NDIS     NDIS.SYS     Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`04fef000 fffff880`04ffb000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
    fffff880`03fbb000 fffff880`03fea000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`0431a000 fffff880`0432f000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
    fffff880`02cdc000 fffff880`02ceb000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`02c5d000 fffff880`02ca2000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
    fffff880`01113000 fffff880`01173000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
    fffff880`0181d000 fffff880`0182e000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`02da2000 fffff880`02dae000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
    fffff800`02a0a000 fffff800`02fe6000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
    fffff880`01450000 fffff880`015f3000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
    fffff880`019a3000 fffff880`019ac000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`02cb6000 fffff880`02cdc000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
    fffff880`03c2d000 fffff880`03c4a000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`00eba000 fffff880`00ecf000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00e87000 fffff880`00eba000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00f40000 fffff880`00f47000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
    fffff880`00f47000 fffff880`00f57000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`0141a000 fffff880`0142b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`060ea000 fffff880`06190000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
    fffff880`0434f000 fffff880`0438c000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00c25000 fffff880`00c39000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`03ea1000 fffff880`03ec5000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`02dc8000 fffff880`02de3000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
    fffff880`02c00000 fffff880`02c21000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
    fffff880`02c21000 fffff880`02c3b000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
    fffff880`02d51000 fffff880`02da2000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
    fffff880`03fea000 fffff880`03ff5000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
    fffff880`019f6000 fffff880`019ff000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`01800000 fffff880`01809000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`01809000 fffff880`01812000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`013bf000 fffff880`013f9000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
    fffff880`05659000 fffff880`05671000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`02d37000 fffff880`02d51000   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:52:25 2010 (4BC2DF49)
    fffff880`06190000 fffff880`0619b000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`03dda000 fffff880`03de6000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`02ceb000 fffff880`02d08000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`0106c000 fffff880`0108a000   spiderg3 spiderg3.sys Mon Jul 19 05:41:50 2010 (4C441DDE)
    fffff880`01445000 fffff880`0144d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`06319000 fffff880`0638a000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
    fffff880`06283000 fffff880`06319000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
    fffff880`0602b000 fffff880`06092000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
    fffff880`0619b000 fffff880`061c8000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
    fffff880`056c7000 fffff880`05742000   stwrt64  stwrt64.sys  Wed Jun 10 02:06:52 2009 (4A2F4D7C)
    fffff880`03df6000 fffff880`03df7480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
    fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
    fffff880`061c8000 fffff880`061da000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
    fffff880`01314000 fffff880`01321000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
    fffff880`0182e000 fffff880`0184c000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
    fffff880`02d23000 fffff880`02d37000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
    fffff960`00530000 fffff960`0053a000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff880`03f7e000 fffff880`03fa4000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
    fffff880`0638a000 fffff880`0638bf00   UCOREW64 UCOREW64.SYS Thu Mar 23 03:11:39 2006 (44224A2B)
    fffff880`042ae000 fffff880`042c0000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
    fffff880`05742000 fffff880`0575f000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
    fffff880`0575f000 fffff880`05760f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
    fffff880`03dc9000 fffff880`03dda000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
    fffff880`042c0000 fffff880`0431a000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
    fffff880`03dbe000 fffff880`03dc9000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
    fffff880`03e4b000 fffff880`03ea1000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
    fffff880`00e7a000 fffff880`00e87000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`019b3000 fffff880`019c1000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`019c1000 fffff880`019e6000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`01435000 fffff880`01445000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
    fffff880`00ecf000 fffff880`00ee4000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00ee4000 fffff880`00f40000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
    fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
    fffff880`02d08000 fffff880`02d23000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
    fffff880`019e6000 fffff880`019f6000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`00d57000 fffff880`00dfb000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00c00000 fffff880`00c0f000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`02cad000 fffff880`02cb6000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff960`00040000 fffff960`0034f000   win32k   win32k.sys   Tue Aug 31 22:58:04 2010 (4C7DC13C)
    fffff880`00e67000 fffff880`00e70000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`02ca2000 fffff880`02cad000   ws2ifsl  ws2ifsl.sys  Mon Jul 13 20:10:33 2009 (4A5BCCF9)
    fffff880`05623000 fffff880`05644000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
    
    Unloaded modules:
    fffff880`01943000 fffff880`01951000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`01951000 fffff880`0195d000   dump_ataport
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`0195d000 fffff880`01966000   dump_atapi.s
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00009000
    fffff880`01966000 fffff880`01979000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    
    
    
    
     
  14. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    TorrentG,

    There was no driver with that name.
    The flashing utility didnt require installing - it was just an ".exe" file.

    Updated already. Are you sure you posted the right link? Because it goes to the L1 type drivers but i have L2 model of Lan. So I installed L2.

    Yes, It was my mistake in trying to update chipset. I mentioned it to provide information that might be helpful.

    I deleted the mentioned folder.

    I will update bios and inform you if smth goes wrong.

    cybercore,

    I used utility from the manufacturer's site. Thanks for the link - will try to use that one.

    Didnt find both drivers in 'system32\drivers'.
     
  15. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Cool. Post new crashes if they happen.

    Update bios from dos, not from Windows, or we will be going through the same problems over and over again.
     
  16. Urgo

    Urgo New Member

    Joined:
    Oct 29, 2010
    Messages:
    14
    Likes Received:
    0
    Downloaded flashing utility from cybercore, link but I relaized that I do not have a floppy drive to commit a DOS-flashing.
    Tried to launched the Windows variant of utility but the system crushed again.

    More than that, overall system works very slowly, program manager shows a high usage of CPU: 70-100%.
    It became that slow today, I think. Yesterday it was not that bad, I suppose.
     

Share This Page

Loading...