BSOD After Standby Wakeup


  1. Posts : 2
    Windows 7 Professional 32bit
       #1

    BSOD After Standby Wakeup


    I have a Toshiba Satellite A305D-S6848. I am running Windows 7 Pro 32bit. Recently I started getting BSOD's almost every time I wake it up from standby. It will wake up, I will type in my password, it will login, but then my screen becomes all garbled and looks like an old tv without a signal. It will do that for 3 seconds and then will reboot. Windows then tells me it has recovered from an unexpected shutdown. I have tried analyzing the mini dumps, but can't quite seem to pinpoint the problem. I have attached the most recent dump.
      My Computer


  2. Posts : 4
    windows 7 professional 64bit
       #2

    I have the same issue, every time after wake up I will get BSOD.
      My Computer


  3. Posts : 1
    XP , Win7
       #3

    Windows crash in NetIo.sys.
    It should have something to do with network.
    Disable your network cards and try again to see whether the problem disappear.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    In addition to the advice from huangjj - Please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
    Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
    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: http://www.carrona.org/drvrdown.html

    Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
    Code:
    AGRSM.sys    Mon Nov 10 09:56:37 2008 - TOSHIBA V92 Software Modem/Agere Systems Soft Modem/Creatix V.92   Data Fax Modem - http://www.carrona.org/dvrref.html#AGRSM.sys
    atikmdag.sys Mon Dec 01 16:01:46 2008 - ATI Video Display Driver - http://www.carrona.org/dvrref.html#atikmdag.sys
    FwLnk.sys    Sun Nov 19 09:11:12 2006 - Toshiba Firmware Linkage service system driver - http://www.carrona.org/dvrref.html#FwLnk.sys
    giveio.sys   Wed Apr 03 22:33:25 1996 - PLEASE REMOVE ASAP!ADC Analyzer or SwiftForth or Disspy - http://www.carrona.org/dvrref.html#giveio.sys
    rimmptsk.sys Sat Feb 24 00:42:21 2007 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rimmptsk.sys
    rimsptsk.sys Tue Jan 23 02:40:19 2007 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rimsptsk.sys
    rixdptsk.sys Wed Mar 21 09:02:02 2007 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rixdptsk.sys
    SynTP.sys    Thu Aug 14 22:02:22 2008 -    Synaptic Touch Pad Driver - http://www.carrona.org/dvrref.html#SynTP.sys
    Summary of the BSOD:
    Code:
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Wed Apr 28 04:25:19.554 2010 (GMT-4)
    System Uptime: 0 days 4:47:26.661
    BugCheck A, {d, 2, 0, 82a9c973}
    Probably caused by : NETIO.SYS ( NETIO!AddFilterToFilterHashtable+9e )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  svchost.exe
      My Computer


  5. Posts : 2
    Windows 7 Professional 32bit
    Thread Starter
       #5

    i recently got another bsod. it didn't happen immediately after it woke up from standby, but it still happened. this time it has the bad_pool_header error. i assume this is also driver based? is there a tool out there to use that can display all the drivers installed on my system? i have attached the minidump
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    Most BSOD's are caused by problems with 3rd party drivers - but not all.
    Windows drivers are often blamed - but are rarely at fault
    Sometimes there's a whole bunch of different errors - and that may indicate a hardware/compatibility problem.

    MSINFO32.exe has a listing of all drivers - but that's not going to help a whole lot.
    You'll need to know what drivers are involved when the system crashes (we get that with the lmtsm command in the debugger) .

    We first concentrate on the drivers identified (or alluded to) in the debugger - then we look at the older drivers (because they may have compatibility issues). We also look at the particular STOP error and attempt to associate it with specific behaviors/issues (such as checking RAM when we see a Memory Management error).

    First, the STOP 0x19 error (which this last BSOD was) is typically caused by a device driver. In this case, the system blames ntkrpamp.exe. This is the core (kernel) of the operating system, so it's not likely that it is actually the problem (if it was, you'd have many more problems than just the occasional BSOD).

    So, we presume that there's another driver that's causing the ntkrpamp.exe file to crash. Since it's not identified in the BSOD memory dump, we've got to try a couple of other things:

    So, first please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
    Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
    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: http://www.carrona.org/drvrdown.html

    Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
    Code:
    giveio.sys   Wed Apr 03 22:33:25 1996 - ADC Analyzer or SwiftForth or Disspy - ?SpeedFan? - http://www.carrona.org/dvrref.html#giveio.sys
    FwLnk.sys    Sun Nov 19 09:11:12 2006 - Toshiba Firmware Linkage service system driver - http://www.carrona.org/dvrref.html#FwLnk.sys
    rimmptsk.sys Sat Feb 24 00:42:21 2007 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#S
    rimmptsk.sys Sat Feb 24 00:42:21 2007 - Ricoh Memory Card Reader driver -  http://www.carrona.org/dvrref.html#rimmptsk.sys
    rimsptsk.sys Tue Jan 23 02:40:19 2007 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rimsptsk.sys
    rixdptsk.sys Wed Mar 21 09:02:02 2007 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rixdptsk.sys
    AGRSM.sys    Mon Nov 10 09:56:37 2008 - Systems Soft Modem/Creatix V.92   Data Fax Modem - http://www.carrona.org/dvrref.html#AGRSM.sys
    atikmdag.sys Mon Dec 01 16:01:46 2008 - ATI Video driver (remove the Catalyst Control Center and only  install the   Display Driver) - http://www.carrona.org/dvrref.html#atikmdag.sys
    SynTP.sys    Thu Aug 14 22:02:22 2008 - Synaptic Touch Pad Driver - http://www.carrona.org/dvrref.html#SynTP.sys
    Then, run Driver Verifier according to these directions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    Summary of the BSOD:
    Code:
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Mon May  3 02:17:32.501 2010 (GMT-4)
    System Uptime: 0 days 3:26:35.528
    BUGCHECK_STR:  0x19_20
    PROCESS_NAME:  System
      My Computer


 

  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 09:15.
Find Us