Random BSOD occurances, STOP: 0x000000F4

ADK Snowman · Jun 18, 2012

I've been having random BSOD crashes for the past week. Also, multiple attempts to fix the BSOD problem by using System Restore has resulted in a BSOD crash.

Every BSOD has displayed "STOP: 0x000000F4"

To my knowledge, no new hardware has been installed on my computer in several months.

Here is my Windows 7 info:

Home Premium 64 bit
Original OS
OEM
Age of system and OS installation : 2 years

I have attached my BSOD and PERFMON files for your perusal. Hopefully this will be a short and sweet fix. I really don't want to buy a new computer or have to reinstall Windows 7.

D

usasma · Jun 19, 2012

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
NOTE: For Vista, read these notes:

Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)

Click to expand...

5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

I ran 5 memory dumps
There were 5 different BSOD error codes cited (none were a STOP: 0x000000F4, but one was mentioned in the WER reports in MSINFO32)
and 5 different causes blamed

This is most likely a hardware error. They (hardware errors) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Your Symantec/Norton has drivers dating from 2009. Please do the following:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Video drivers date from 2010 - please update from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

Wireless network driver (netr28x.sys) dates from 2009, please update from the manufacturer's website. More info on the driver here: Driver Reference Table - netr28x.sys

NetGroup Packet Filter Driver, part of the WinPcap packet capture library (npf.sys) dates from 2009, please update it. More info on the driver here: Driver Reference Table - npf.sys

What seems to be a Radio Shack Serial to USB connector has drivers that date from 2007 (ser2rs64.sys) and MUST be updated or removed from your system. More info on the driver may be found here: http://www.carrona.org/drivers/driver.php?id=ser2rs64.sys

Other outdated drivers (such as Chipset drivers) will have to be updated as part of the Service Pack 1 update procedure.

If the BSOD's continue after the above updates, please post back and we'll move on with other diagnostics.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[FONT=lucida console]
AtiPcie64.sys           Wed Mar 10 09:33:45 2010 (4B97ADC9)
BHDrvx64.sys            Tue Mar 13 16:02:37 2012 (4F5FA7DD)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
EraserUtilDrv11210.sys  Tue May 15 20:36:03 2012 (4FB2F673)
EraserUtilRebootDrv.sys Tue May 15 20:36:03 2012 (4FB2F673)
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
IDSvia64.sys            Fri Mar 09 16:57:02 2012 (4F5A7CAE)
Ironx64.SYS             Tue Apr 27 20:48:23 2010 (4BD785D7)
RTKVHD64.sys            Thu Feb 25 04:14:31 2010 (4B863F77)
Rt64win7.sys            Thu Mar 04 08:42:52 2010 (4B8FB8DC)
SRTSP64.SYS             Wed Feb 24 18:59:29 2010 (4B85BD61)
SRTSPX64.SYS            Wed Feb 24 18:59:48 2010 (4B85BD74)
SYMDS64.SYS             Mon Aug 17 19:35:30 2009 (4A89E942)
SYMEFA64.SYS            Wed Feb 16 14:05:29 2011 (4D5C1FF9)
SYMEVENT64x86.SYS       Tue Nov 22 13:30:48 2011 (4ECBEA58)
SYMTDIV.SYS             Tue Jun 21 18:31:58 2011 (4E011BDE)
SymIMv.sys              Fri Apr 30 22:12:21 2010 (4BDB8E05)
amdsbs.sys              Fri Mar 20 14:36:03 2009 (49C3E213)
amdxata.sys             Wed Oct 07 16:13:10 2009 (4ACCF656)
atikmpag.sys            Tue Feb 02 22:23:59 2010 (4B68EC4F)
atipmdag.sys            Tue Feb 02 23:21:24 2010 (4B68F9C4)
ccHPx64.sys             Mon Jul 11 16:26:19 2011 (4E1B5C6B)
ccSetx64.sys            Fri Nov 04 18:05:25 2011 (4EB461A5)
dump_amdsbs.sys         Fri Mar 20 14:36:03 2009 (49C3E213)
dump_storport.sys       Mon Jul 13 20:01:00 2009 (4A5BCABC)
eeCtrl64.sys            Tue May 15 20:36:03 2012 (4FB2F673)
lvbflt64.sys            Fri Aug 19 05:25:01 2011 (4E4E2BED)
lvrs64.sys              Fri Aug 19 05:25:38 2011 (4E4E2C12)
lvuvc64.sys             Fri Aug 19 05:26:11 2011 (4E4E2C33)
netr28x.sys             Fri Dec 18 07:32:14 2009 (4B2B764E)
npf.sys                 Tue Oct 20 14:00:19 2009 (4ADDFAB3)
ser2rs64.sys            Mon Jun 25 03:14:53 2007 (467F6B6D)
usbaapl64.sys           Tue Jan 10 19:56:04 2012 (4F0CDE24)
usbfilter.sys           Wed Oct 07 03:44:08 2009 (4ACC46C8)
[/FONT]

Code:

[FONT=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061112-40341-01.dmp]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jun 11 14:16:21.610 2012 (UTC - 4:00)
System Uptime: 0 days 0:13:36.452
BugCheck 1A, {41790, fffffa8002624c10, ffff, 0}
Probably caused by : win32k.sys ( win32k!SURFACE::bUnMapImmediate+5b )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bUnMapImmediate+5b
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`02624c10 00000000`0000ffff 00000000`00000000
BiosVersion = 6.03
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6510f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061112-41948-01.dmp]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jun 11 11:08:22.410 2012 (UTC - 4:00)
System Uptime: 1 days 14:20:45.877
BugCheck D1, {10, 2, 0, fffff880010c9591}
Probably caused by : storport.sys ( storport!RaidUnitCompleteRequest+c1 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  javaw.exe
FAILURE_BUCKET_ID:  X64_0xD1_storport!RaidUnitCompleteRequest+c1
Bugcheck code 000000D1
Arguments 00000000`00000010 00000000`00000002 00000000`00000000 fffff880`010c9591
BiosVersion = 6.03
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6510f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061112-43227-01.dmp]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jun 11 11:45:42.271 2012 (UTC - 4:00)
System Uptime: 0 days 0:36:50.113
BugCheck 1000007E, {ffffffffc0000005, fffff8800562841d, fffff88003db7408, fffff88003db6c70}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+2d )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+2d
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0562841d fffff880`03db7408 fffff880`03db6c70
BiosVersion = 6.03
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6510f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-37377-01.dmp]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jun 13 12:17:05.381 2012 (UTC - 4:00)
System Uptime: 1 days 15:37:48.848
BugCheck 18, {0, fffffa8005a070ff, 2, fffa800ace06f0fe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46411 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  MOM.exe
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+46411
Bugcheck code 00000018
Arguments 00000000`00000000 fffffa80`05a070ff 00000000`00000002 fffa800a`ce06f0fe
BiosVersion = 6.03
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6510f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-41355-01.dmp]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jun 13 12:36:53.353 2012 (UTC - 4:00)
System Uptime: 0 days 0:19:18.820
BugCheck 24, {1904fb, fffff8800977e5e8, fffff8800977de50, fffff88001301173}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  CarboniteServi
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFcbTableCompare+3
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0977e5e8 fffff880`0977de50 fffff880`01301173
BiosVersion = 6.03
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6510f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

Random BSOD occurances, STOP: 0x000000F4

ADK Snowman

New member

My Computer

usasma

Mr. Cranky Pants

My Computer