BSOD Stop Code f4 after sleep

[captainzero83]

Hey everyone,

I been reading different threads about this but I have not found a solution. Im getting the BSOD after sleep mode on my desktop. I let it go to sleep mode overnight and wake it up in the morning. Im getting the Stop Code f4.

here are my specs:
Gateway FX 6480-15e
Running W7 64 bit
8 GB of RAM
1 TB HDD
ATI Radeon HD 5750 1 GB

I have included the mini-dump zip. I really dont want to take it back to best buy unless i have to. The computer is still under warranty.

A little background. i had the HDD fail on me and the replaced it and uploaded W7 again. I have had this computer for about 3 months and is practically new.

Anything i can do to fix this?? thanx guys

 

[usasma]

While the dump files are running, there's 2 things that I suspect:
- your Avast Internet Security
- your Netgear WNDA3100v2 USB adapter

I'd suggest:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Avast Internet Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Avast Internet Security using this free tool: http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039http://www.avast.com/eng/avast-uninstall-utility.html
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

For the Netgear WNDA3100v2 USB adapter I'd suggest:
- Download a fresh copy of the latest Win7 64 bit drivers from the Netgear website: WNDA3100v2 Software Version 1.3
- Uninstall the current version from your system
- Install the freshly downloaded version and monitor for further BSOD's

I'd also suggest these hardware diagnostics due to some of the errors in the BSOD's:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
scmndisp.sys Wed Jan 17 02:48:03 2007 (45ADD4B3)
[url=http://www.carrona.org/dvrref.html#scmndisp.sys]http[i]:[/i]//www.carrona.org/dvrref.html#scmndisp.sys[/url] 

aswNdis.sys  Sat Jan 09 16:22:03 2010 (4B48F37B)
[url=http://www.carrona.org/dvrref.html#aswNdis.sys]http[i]:[/i]//www.carrona.org/dvrref.html#aswNdis.sys[/url] 

Rt64win7.sys Thu Mar 04 08:42:52 2010 (4B8FB8DC)
[url=http://www.carrona.org/dvrref.html#Rt64win7.sys]http[i]:[/i]//www.carrona.org/dvrref.html#Rt64win7.sys[/url] 

GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
[url=http://www.carrona.org/dvrref.html#GEARAspiWDM.sys]http[i]:[/i]//www.carrona.org/dvrref.html#GEARAspiWDM.sys[/url] 

bcmwlhigh664.sys Thu Nov 05 19:27:07 2009 (4AF36D5B)
[url=http://www.carrona.org/dvrref.html#bcmwlhigh664.sys]http[i]:[/i]//www.carrona.org/dvrref.html#bcmwlhigh664.sys[/url] 

WinUsb.sys   Mon Jul 13 20:06:28 2009 (4A5BCC04)
[url=http://www.carrona.org/dvrref.html#WinUsb.sys]http[i]:[/i]//www.carrona.org/dvrref.html#WinUsb.sys[/url] 

usbaapl64.sys Thu Sep 16 22:19:05 2010 (4C92D019)
[url=http://www.carrona.org/dvrref.html#usbaapl64.sys]http[i]:[/i]//www.carrona.org/dvrref.html#usbaapl64.sys[/url] 
[/font]

If all of this doesn't stop the BSOD's, then I'd have to suggest running Driver Verifier according to these instructions:

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 12 09:41:36.892 2011 (UTC - 5:00)
System Uptime: 0 days 9:52:53.001
BugCheck F4, {3, fffffa80091189f0, fffffa8009118cd0, fffff80002dd22d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`091189f0 fffffa80`09118cd0 fffff800`02dd22d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  9 10:31:02.894 2011 (UTC - 5:00)
System Uptime: 0 days 0:20:53.002
BugCheck F4, {3, fffffa8009167060, fffffa8009167340, fffff80002d995d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09167060 fffffa80`09167340 fffff800`02d995d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  9 10:08:58.894 2011 (UTC - 5:00)
System Uptime: 0 days 0:20:52.002
BugCheck F4, {3, fffffa8008785b30, fffffa8008785e10, fffff80002dca5d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08785b30 fffffa80`08785e10 fffff800`02dca5d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  9 09:32:25.875 2011 (UTC - 5:00)
System Uptime: 0 days 9:05:39.983
BugCheck F4, {3, fffffa800912b730, fffffa800912ba10, fffff80002d805d0}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000000E
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0912b730 fffffa80`0912ba10 fffff800`02d805d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 11:05:59.256 2011 (UTC - 5:00)
System Uptime: 0 days 2:41:15.253
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e )
BUGCHECK_STR:  0x7a_c000000e
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  atiesrxx.exe
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c0e
Bugcheck code 0000007A
Arguments fffff6fb`80008000 ffffffff`c000000e 00000001`3845b880 fffff700`01000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 09:07:34.000 2011 (UTC - 5:00)
System Uptime: 0 days 7:52:43.108
BugCheck F4, {3, fffffa80097a74f0, fffffa80097a77d0, fffff80002ddd5d0}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000000E
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`097a74f0 fffffa80`097a77d0 fffff800`02ddd5d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 01:08:12.252 2011 (UTC - 5:00)
System Uptime: 0 days 23:39:52.360
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e )
BUGCHECK_STR:  0x7a_c000000e
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c0e
Bugcheck code 0000007A
Arguments fffff6fc`4002a348 ffffffff`c000000e 00000000`94ce7be0 fffff880`05469000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]