BSOD after sleep mode (driver_power_state_failure / ntkrnlpa.exe)

Page 1 of 2 12 LastLast

  1. Posts : 14
    7 32bit
       #1

    BSOD after sleep mode (driver_power_state_failure / ntkrnlpa.exe)


    Hi,

    I've had a few BSOD's recently, every time has been after I've put my system in sleep mode.

    running win7 profesisonal 32bit, OEM on a HP system (less than 1 year old).

    similar error every time, please see below and attached dump files.

    thanks for any help!



    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.
    The problem seems to be caused by the following file: ntkrnlpa.exe
    DRIVER_POWER_STATE_FAILURE
    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:
    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.
    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.
    Technical Information:
    *** STOP: 0x0000009f (0x00000003, 0x86016568, 0x82d6bae0, 0x858987e8)
    *** ntkrnlpa.exe - Address 0x82d21d10 base at 0x82c45000 DateStamp 0x4c1c3fac
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    theshoemaker said:
    Hi,

    I've had a few BSOD's recently, every time has been after I've put my system in sleep mode.

    running win7 profesisonal 32bit, OEM on a HP system (less than 1 year old).

    similar error every time, please see below and attached dump files.

    thanks for any help!

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.
    The problem seems to be caused by the following file: ntkrnlpa.exe
    DRIVER_POWER_STATE_FAILURE
    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:
    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.
    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.
    Technical Information:
    *** STOP: 0x0000009f (0x00000003, 0x86016568, 0x82d6bae0, 0x858987e8)
    *** ntkrnlpa.exe - Address 0x82d21d10 base at 0x82c45000 DateStamp 0x4c1c3fac

    These were all caused by your broadcom NetXtreme Gigabit Ethernet Driver.. It needs updating and re-installation .

    Also the outdated drivers need attending to
    .





    Old Drivers needing update

    Code:
    hardlock.sys        0x9e93a400    0x000a7400    7/27/2005 08:08:29            0x42e7874d    0x9e893000                
    regi.sys        0x9e9d3500    0x00001500    4/16/2007 10:19:05            0x462393e9    0x9e9d2000                
    mcdbus.sys        0x948ac800    0x0001c800    2/24/2009 05:42:13            0x49a3cf05    0x94890000                
    spldr.sys        0x8c9f8000    0x00008000    5/11/2009 11:13:47            0x4a084ebb    0x8c9f0000                
    GEARAspiWDM.sys        0x91a1c280    0x00005280    5/18/2009 07:16:53            0x4a1151b5    0x91a17000                
    amdxata.sys        0x8c4f8000    0x00009000    5/19/2009 12:57:35            0x4a12f30f    0x8c4ef000                
    PxHelp20.sys        0x8c546300    0x00009300    6/23/2009 18:16:17            0x4a416241    0x8c53d000                
    nvBridge.kmd        0x92563080    0x00001080    6/26/2009 16:38:18            0x4a453fca    0x92562000                
    nvlddmkm.sys        0x925610e0    0x009530e0    6/26/2009 17:15:23            0x4a45487b    0x91c0e000
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      My Computer


  3. Posts : 14
    7 32bit
    Thread Starter
       #3

    thanks for the analysis - I installed the latest version of the ethernet driver, I managed to put the system into sleep mode twice but on the third time I got the same blue screen again.

    I've attached the dump files including the latest one. any idea what might've caused this one?

    I didn't get a chance to update any of the other drivers before this happened, thats on my agenda next but wanted to post this here meanwhile.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    theshoemaker said:
    thanks for the analysis - I installed the latest version of the ethernet driver, I managed to put the system into sleep mode twice but on the third time I got the same blue screen again.

    I've attached the dump files including the latest one. any idea what might've caused this one?

    I didn't get a chance to update any of the other drivers before this happened, thats on my agenda next but wanted to post this here meanwhile.


    Post away. All these and all the last one were a 9F bugcheck. This is that bugcheck.

    The DRIVER_POWER_STATE_FAILURE bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.

    You can see why we want you to update your drivers. If you cant find a hardlock driver after 7/13/09 you will have to remove it.

    Update the drivers

    Good Luck

    Ken J


    Old Drivers Still
    Code:
    hardlock.sys        0x9e93a400    0x000a7400    7/27/2005 08:08:29            0x42e7874d    0x9e893000                
    regi.sys        0x9e9d3500    0x00001500    4/16/2007 10:19:05            0x462393e9    0x9e9d2000                
    mcdbus.sys        0x948ac800    0x0001c800    2/24/2009 05:42:13            0x49a3cf05    0x94890000                
    spldr.sys        0x8c9f8000    0x00008000    5/11/2009 11:13:47            0x4a084ebb    0x8c9f0000                
    GEARAspiWDM.sys        0x91a1c280    0x00005280    5/18/2009 07:16:53            0x4a1151b5    0x91a17000                
    amdxata.sys        0x8c4f8000    0x00009000    5/19/2009 12:57:35            0x4a12f30f    0x8c4ef000                
    PxHelp20.sys        0x8c546300    0x00009300    6/23/2009 18:16:17            0x4a416241    0x8c53d000                
    nvBridge.kmd        0x92563080    0x00001080    6/26/2009 16:38:18            0x4a453fca    0x92562000                
    nvlddmkm.sys        0x925610e0    0x009530e0    6/26/2009 17:15:23            0x4a45487b    0x91c0e000
    
    


      My Computer


  5. Posts : 14
    7 32bit
    Thread Starter
       #5

    Ended up removing hardlock.sys as it was for some software that wasn't even installed on my system - seems like this took care of the BS.

    thanks for your help!
      My Computer


  6. Posts : 14
    7 32bit
    Thread Starter
       #6

    After updating all the drivers I was able to, everything worked fine for a bit but I got another blue screen today when putting the system into hibernation.

    enclosed is the dump file and below are the previously mentioned drivers and what I've done so far:

    hardlock.sys - unecessary, removed
    regi.sys - unecessary, removed
    mcdbus.sys - unecessary, removed
    spldr.sys - not sure what this is, some native windows driver? unable to find a newer version

    GEARAspiWDM.sys - unecessary, removed
    amdxata.sys - unknown, unable to find a new version
    PxHelp20.sys - removed
    nvBridge.kmd - updated
    nvlddmkm.sys - updated
      My Computer


  7. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #7

    Good job with the drivers.
    spldr.sys - This is a Windows driver and it should be OK. You are right; there is no update.
    amdxata.sys - There not a newer version and this one should be OK.

    Error code 9F, DRIVER_POWER_STATE_FAILURE. Caused by a device driver.
    Code:
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82c53000 PsLoadedModuleList = 0x82d9b810
    Debug session time: Fri Nov 26 10:19:58.322 2010 (GMT-5)
    System Uptime: 3 days 23:42:52.961
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    .......
    0: kd> !Analyze
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, 86029030, 82d79ae0, 8865fb40}
    
    *** WARNING: Unable to verify timestamp for b57nd60x.sys
    *** ERROR: Module load completed but symbols could not be loaded for b57nd60x.sys
    Probably caused by : b57nd60x.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 00000003, A device object has been blocking an Irp for too long a time
    Arg2: 86029030, Physical Device Object of the stack
    Arg3: 82d79ae0, Functional Device Object of the stack
    Arg4: 8865fb40, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  8865fb40
    
    DEVICE_OBJECT: 87509028
    
    DRIVER_OBJECT: 86043318
    
    IMAGE_NAME:  b57nd60x.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bf61ed6
    
    MODULE_NAME: b57nd60x
    
    FAULTING_MODULE: 91978000 b57nd60x
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from 82c8f054 to 82d2fd10
    
    STACK_TEXT:  
    82d79a94 82c8f054 0000009f 00000003 86029030 nt!KeBugCheckEx+0x1e
    82d79b00 82c8e8e8 82d79bac 00000000 82d86280 nt!PopCheckIrpWatchdog+0x1f5
    82d79b38 82cbd04d 82d94a20 00000000 63194ff0 nt!PopCheckForIdleness+0x73
    82d79b7c 82cbcff1 82d7cd20 82d79ca8 00000002 nt!KiProcessTimerDpcTable+0x50
    82d79c68 82cbceae 82d7cd20 82d79ca8 00000000 nt!KiProcessExpiredTimerList+0x101
    82d79cdc 82cbb20e 015108bc 85736798 82d86280 nt!KiTimerExpiration+0x25c
    82d79d20 82cbb038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
    82d79d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  0x9F_IMAGE_b57nd60x.sys
    
    BUCKET_ID:  0x9F_IMAGE_b57nd60x.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmtsmn
    start    end        module name
    919ce000 919fa000   1394ohci 1394ohci.sys Mon Jul 13 19:51:59 2009 (4A5BC89F)
    8c2be000 8c306000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
    9141c000 91476000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
    83200000 83212000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
    8c4f9000 8c502000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
    934c9000 934d3000   appliand appliand.sys Fri May 28 07:54:28 2010 (4BFFAEF4)
    96a50000 96a9d000   ATMFD    ATMFD.DLL    unavailable (00000000)
    91978000 919ce000   b57nd60x b57nd60x.sys Fri May 21 01:49:10 2010 (4BF61ED6)
    8cb5a000 8cb61000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
    91400000 9140e000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
    832a8000 832b0000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
    8caeb000 8cb04000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
    96a30000 96a4e000   cdd      cdd.dll      unavailable (00000000)
    8cb34000 8cb53000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
    832f2000 8339d000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
    8ca17000 8ca3c000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
    832b0000 832f2000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    8c793000 8c7f0000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
    8c9f0000 8c9fd000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
    964ef000 964fc000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
    9157a000 915de000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
    915de000 915f6000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
    9156e000 9157a000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
    8c609000 8c61a000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
    964cc000 964e5000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
    965d6000 965e7000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
    964fc000 965d6000   dump_iaStor dump_iaStor.sys Fri Aug 07 08:16:56 2009 (4A7C1B38)
    964e5000 964ef000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
    91857000 9190e000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
    933b7000 933f0000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
    8ca3c000 8ca66000   fastfat  fastfat.SYS  Mon Jul 13 19:14:01 2009 (4A5BBFB9)
    8cbee000 8cbf9000   fdc      fdc.sys      unavailable (00000000)
    8c536000 8c547000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    8c502000 8c536000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
    8c600000 8c609000   Fs_Rec   Fs_Rec.sys   unavailable (00000000)
    833ca000 833fc000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
    8c957000 8c988000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
    82c1c000 82c53000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
    91959000 91978000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
    9f951000 9f962000   hiber_dumpfve hiber_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
    9f877000 9f951000   hiber_iaStor hiber_iaStor.sys Fri Aug 07 08:16:56 2009 (4A7C1B38)
    935a4000 935b7000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
    935b7000 935bd480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
    965f4000 965ff000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
    8ca66000 8caeb000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
    8c9e8000 8c9f0000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
    8c41f000 8c4f9000   iaStor   iaStor.sys   Fri Aug 07 08:16:56 2009 (4A7C1B38)
    8ca00000 8ca12000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
    91825000 91832000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
    935f3000 935ff000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705)
    80bb5000 80bbd000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
    934df000 93513000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
    8c780000 8c793000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
    8c3ce000 8c3f3000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
    93424000 93434000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
    935be000 935d9000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
    8321f000 83297000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
    965e7000 965f2000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
    91818000 91825000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
    93419000 93424000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
    8c3b8000 8c3ce000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
    8cb04000 8cb16000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
    9dc25000 9dc48000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
    9dc48000 9dc83000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
    9dc83000 9dc9e000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
    8cbb3000 8cbbe000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
    8c30f000 8c317000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
    8c755000 8c780000   msrpc    msrpc.sys    unavailable (00000000)
    91564000 9156e000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    8c9d8000 8c9e8000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
    8c547000 8c5fe000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
    9344f000 9345a000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
    9345a000 9347c000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
    93565000 93576000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
    914ce000 914dc000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
    91476000 914a8000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
    8c200000 8c23e000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
    8cbbe000 8cbcc000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
    9155a000 91564000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
    82c53000 83063000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
    8c626000 8c755000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
    8cb53000 8cb5a000   Null     Null.SYS     unavailable (00000000)
    933b5000 933b6040   nvBridge nvBridge.kmd Sat Oct 16 13:04:23 2010 (4CB9DB17)
    92a18000 933b45a0   nvlddmkm nvlddmkm.sys Sat Oct 16 13:07:56 2010 (4CB9DBEC)
    914af000 914ce000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
    8c400000 8c418000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
    8c34c000 8c35d000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
    9dc9e000 9dca5000   parvdm   parvdm.sys   unavailable (00000000)
    8c317000 8c341000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
    8c7f0000 8c7fe000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    9dca5000 9dd3c000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
    9649d000 964cc000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
    83297000 832a8000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
    93437000 9344f000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
    9347c000 93494000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
    93494000 934ab000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
    934ab000 934c2000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
    91519000 9155a000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
    934d3000 934dd000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
    8cb9b000 8cba3000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
    8cba3000 8cbab000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
    8cbab000 8cbb3000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
    8339d000 833ca000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
    91800000 91813000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
    96201000 9649c140   RTKVHDA  RTKVHDA.sys  Tue Jul 28 09:02:38 2009 (4A6EF6EE)
    9dd3c000 9dd46000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
    9140e000 91418000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
    914dc000 914f6000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
    8c9d0000 8c9d8000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
    9f805000 9f856000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
    9dd74000 9ddc3000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
    9dd46000 9dd67000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
    934dd000 934de380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
    934c2000 934c8600   taphss   taphss.sys   Wed Sep 09 16:55:14 2009 (4AA81632)
    8c80e000 8c957000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
    9dd67000 9dd74000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
    8cbe3000 8cbee000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
    8cbcc000 8cbe3000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
    91509000 91519000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
    96a00000 96a09000   TSDDD    TSDDD.dll    unavailable (00000000)
    91836000 91857000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
    93513000 93521000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
    9358d000 935a4000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
    965f2000 965f3700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
    92a00000 92a0f000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
    93521000 93565000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
    9190e000 91959000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
    9340e000 93419000   usbprint usbprint.sys Mon Jul 13 20:17:06 2009 (4A5BCE82)
    93400000 9340e000   usbscan  usbscan.sys  Mon Jul 13 20:14:44 2009 (4A5BCDF4)
    93576000 9358d000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877)
    933f0000 933fb000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
    8c341000 8c34c000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
    8cb61000 8cb6d000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
    8cb6d000 8cb8e000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
    8c988000 8c991000   vmstorfl vmstorfl.sys unavailable (00000000)
    8c35d000 8c36d000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    8c36d000 8c3b8000   volmgrx  volmgrx.sys  unavailable (00000000)
    8c991000 8c9d0000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
    914f6000 91509000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
    8cb8e000 8cb9b000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
    8c23f000 8c2b0000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
    8c2b0000 8c2be000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    914a8000 914af000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
    96ba0000 96deb000   win32k   win32k.sys   unavailable (00000000)
    92a0f000 92a18000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:19:16 2009 (4A5BC0F4)
    8c306000 8c30f000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
    935d9000 935f3000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
    9f856000 9f876480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)
    
    Unloaded modules:
    9f8e1000 9f9bb000   hiber_iaStor
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    9f9bb000 9f9cc000   hiber_dumpfv
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    9f877000 9f8e1000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    8ca3c000 8ca49000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    8ca49000 8cb23000   dump_iaStor.
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    8cb23000 8cb34000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    91800000 91818000   i8042prt.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    The dump directly blames b57nd60x.sys, your NetXtreme Gigabit Ethernet Driver, and I know you updated this driver. There is a possibility that something else is interfering with with it. Just on a hunch, I see that you have Hotspot Shield by AnchorFree installed. A lot of third party security programs create problems with Win 7. Try uninstalling this program and see how your system does. If there is no change, you can reinstall it. Let us know if this works or not.
      My Computer


  8. Posts : 14
    7 32bit
    Thread Starter
       #8

    thanks for your thoughts!

    the Hotspot isn't running usually, I just used it a couple of times when some sites limit content from non-US visitors. anyway, uninstalled it just in case, and got another BS when entering hibernation.

    this time I happened to sit at my desk for a while, and realized that after I choose hibernation, the screen turns off, but the system keeps running. I waited it out, and it took a good 15 minutes before anything happened, then it was the same old BS.

    I assume the error is the exact same one, but here is the dump just in case.

    any other thoughts?
      My Computer


  9. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #9

    Yes, the dump is virtually the same blaming b57nd60x.sys. The Hotspot driver is shown as an unloaded module, which means it was part of the crash. The HotSpot driver, taphss.sys, loads whether Hotspot is is being used or not. I am interested to see if uninstalling it cures or helps this problem. If this BSOD occured after you uninstalled Hotspot, using Windows Explorer, navigate to C:\Windows\System32\Drivers, locate the driver and rename it from .sys to .bak. Reboot and the driver will not load.

    I don't have any other thoughts yet.
      My Computer


  10. Posts : 14
    7 32bit
    Thread Starter
       #10

    I uninstalled the software and deleted the driver altogether, and got another BS after this.

    I went to look at my recently installed software, and seems like a week or so before the first crash I had installed replay media catcher (software used for ripping streamed media). uninstalled it, and so far no bluescreen

    will have to wait and see for a while, though now I seem to have another problem, my display won't return from sleep mode. stays black and has a led blinking, like the computer would still be off. reconnecting the cable does not help, but since its fairly easy to go back to hibernation mode while blinded (windows key + right twice + enter), I managed to do that and when I turned the system back on, the monitor functioned again.

    any ideas if this could be a driver issue, either the video card or the monitor itself?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Đ Designer Media Ltd
All times are GMT -5. The time now is 21:09.
Find Us