BleepingComputer.com: Vista BSOD / Stop Error 0x000000F4

First off... your web site has assisted me on several occasions. Keep up the great work!

All right, here is my situation. Been running 32 bit version of Vista for about 1.5 years now. Same system is in use now as when I installed vista. Only internal hardware changes have been the addition of 2 Seagate SATA HDD about 8 months ago. OS has always run off my WD 74Gb raptor (around 3 to 4 years old). Other than that, I have added a new keyboard (Logitech Dinovo Edge around 3 months ago) and a numeric keypad (Logitech V250 Cordless Mouse/number Pad around 2 months ago. Only keypad is used). Around 2 to 3 months ago, I started getting the dreaded BSOD (Stop Error Code is always 0x000000F4 (first parameter is 0x00000003). Upon restart of the computer, I get a message that Windows has recovered from an unexpected shut down. When checking for solutions it comes back as stating it is my nvidia nforce SATA driver. I updated it and the problem did not go away. After a few weeks of this I started noticing that the BSOD only happened while my computer sat idle for around 5 minutes (no interaction on my part). What I have noticed to this point is that I am able to run a defrag or a virus scan without any further interaction on my part and the computer would stay on. Pretty much anything else and after around 5 minutes or so, the dreaded BSOD would appear. That's about all I can remember at this time.


My computer specs are as follows:
ASUS Crosshair MB
AMD Athlon 64 X2 Dual Core Processor 4200+ (2CPUs), ~2.2GHz
NVIDIA GeForce 7950 Graphics card with 512MB RAM
2GB RAM
4 HDD: 01 - 74GB WD Raptor (System Drive)
02 - 320GB WD
03 - 500GB Seagate
04 - 500GB Seagate
OEM system builder disc version of Windows Vista Ultimate (32bit) w/ SP1

Here is the text from the latest minidump file. I was unable to upload it.

Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini112508-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8223e000 PsLoadedModuleList = 0x82355c70
Debug session time: Tue Nov 25 20:02:45.895 2008 (GMT-8)
System Uptime: 0 days 0:24:04.978
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 8e5910c8, 8e591214, 8247c430}

c0000005 Exception in ext.Analyze debugger extension.
PC: 74737953 VA: 74737953 R/W: 8 Parameter: 0001003f
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8e5910c8, Terminating object
Arg3: 8e591214, Process image file name
Arg4: 8247c430, Explanatory message (ascii)

Debugging Details:
------------------

c0000005 Exception in ext.analyze debugger extension.
PC: 74737953 VA: 74737953 R/W: 8 Parameter: 0001003f

If any more info is needed, please let me know. Thanks for the assistance.

Try typing "lm" (without the quotes) in the box at the bottom of the debugger window - then post the results of that also. This should list the modules that are loaded (if available).

Warning Will Robinson!

I've seen this issue a number of times already here and on other sites.

The fix I'm about to recommend is NOT the First thing you should Attempt, however, I believe that you need to Update your System's BIOS.
You can download this from the motherboard manufacturer's website.

MAKE CERTAIN that if you do this, you have the correct bios revision and know how to accomplish this. In your Case, you'll want to run this
from a boot floppy. If you decide to take this advice, the community can advise on on questions you may have.

I believe that the problem is at the Platform level and has to do with the motherboard, bios, and/or System software.

I don't have any PROOF to this point yet. The evidence is simply pointing to these things as a likely or potential Cause.

Another note if you attempt this, remove any Antivirus software, if AMDLive is installed, remove it. Also remove any Windows updates
from the Add/Remove Programs Applet. You should attempt all of this in Safe Mode, or last known good configuration.

Tap F8 as the machine boots and choose Safe mode or Last known good configuration in order to accomplish the last part.
Then Flash the BIOS from a boot Floppy that you might create.

This is Technically involved and drawn out process and may not work, or worse still it could make things worse. I would do this myself, but I don't
have your motherboard.

If you want to hear the more logical steps, let me know and I or someone in the community will help out. I may catch some flack for recommending this and rightly so. This is purely optional in nature, but make sure you understand the process before attempting.

If the steps that I'm providing now are attempted and work, then we can help solve a number of these issues with much more confidence.

Let me know what you decide.

usasma, on Nov 26 2008, 04:18 PM, said:

All right usasma... Typed in "lm" (without quotes) in debugger and here are the results...

0: kd> lm
start end module name
80400000 80409000 kbdhid (deferred)
80409000 80411000 kdcom (deferred)
80411000 80422000 PSHED (deferred)
80422000 8042a000 BOOTVID (deferred)
8042a000 8046b000 CLFS (deferred)
8046b000 8054b000 CI (deferred)
8054b000 805c7000 Wdf01000 (deferred)
805c7000 805d4000 WDFLDR (deferred)
805d4000 805e9000 rassstp (deferred)
805e9000 805f9000 HIDCLASS (deferred)
80605000 8064b000 acpi (deferred)
8064b000 80654000 WMILIB (deferred)
80654000 8065c000 msisadrv (deferred)
8065c000 80683000 pci (deferred)
80683000 80692000 partmgr (deferred)
80692000 806a1000 volmgr (deferred)
806a1000 806eb000 volmgrx (deferred)
806eb000 806f2000 pciide (deferred)
806f2000 80700000 PCIIDEX (deferred)
80700000 80710000 mountmgr (deferred)
80710000 80715580 pavboot (deferred)
80716000 8071e000 atapi (deferred)
8071e000 8073c000 ataport (deferred)
8073c000 80749000 nvstor (deferred)
80749000 8078a000 storport (deferred)
8078a000 807a1000 SI3132 (deferred)
807a1000 807c7000 SCSIPORT (deferred)
807c7000 807ec000 nvstor32 (deferred)
807ec000 80800000 raspptp (deferred)
8220b000 8223e000 hal (deferred)
8223e000 825f7000 nt (pdb symbols) c:\symbols\ntkrpamp.pdb\E3AF30C94A334570818A670674C7F9602\ntkrpamp.pdb
82c04000 82c36000 fltmgr (deferred)
82c36000 82c46000 fileinfo (deferred)
82c46000 82c49100 SiWinAcc (deferred)
82c4a000 82cbb000 ksecdd (deferred)
82cbb000 82dc6000 ndis (deferred)
82dc6000 82df1000 msrpc (deferred)
82df1000 82dfa000 hidusb (deferred)
82e00000 82e0f000 raspppoe (deferred)
82e0f000 82e49000 NETIO (deferred)
82e49000 82f30000 tcpip (deferred)
82f30000 82f4b000 fwpkclnt (deferred)
82f4b000 82f5d000 xpacket (deferred)
82f5d000 82f7e000 CLASSPNP (deferred)
82f7e000 82fb9000 udfs (deferred)
82fcb000 82fd6000 tunnel (deferred)
82fd6000 82fdf000 tunmp (deferred)
82fdf000 82fef000 amdk8 (deferred)
82fef000 82ff9000 usbohci (deferred)
88206000 88315000 Ntfs (deferred)
88315000 8834e000 volsnap (deferred)
8834e000 883761a0 spssys (deferred)
88377000 8837f000 spldr (deferred)
8837f000 88387000 SiRemFil (deferred)
88387000 88396000 mup (deferred)
88396000 883bd000 ecache (deferred)
883bd000 883e1000 fvevol (deferred)
883e1000 883f2000 disk (deferred)
883f2000 883fb000 crcdisk (deferred)
8be00000 8be3e000 USBPORT (deferred)
8be3e000 8be4d000 usbehci (deferred)
8be4d000 8be64800 AnyDVD (deferred)
8be65000 8be6d280 cdrbsdrv (deferred)
8be6e000 8be86000 cdrom (deferred)
8be86000 8be95200 ohci1394 (deferred)
8be96000 8bea3080 1394BUS (deferred)
8bea4000 8beb6000 HDAudBus (deferred)
8beb6000 8bfb2680 nvmfdx32 (deferred)
8bfb3000 8bfca000 rasl2tp (deferred)
8bfca000 8bfd5000 ndistapi (deferred)
8bfd5000 8bff8000 ndiswan (deferred)
8bff8000 8bffe380 HIDPARSE (deferred)
8c001000 8c70aba0 nvlddmkm (deferred)
8c70b000 8c7aa000 dxgkrnl (deferred)
8c7aa000 8c7b7000 watchdog (deferred)
8c7b7000 8c7b8420 ASACPI (deferred)
8c7b9000 8c7c4000 fdc (deferred)
8c7c4000 8c7f2000 msiscsi (deferred)
8c7f2000 8c7fd000 TDI (deferred)
8ca01000 8ca8a000 rdpdr (deferred)
8ca8a000 8ca9a000 termdd (deferred)
8ca9a000 8caa5000 kbdclass (deferred)
8caa5000 8cab0000 mouclass (deferred)
8cab0000 8cab1380 swenum (deferred)
8cab2000 8cadc000 ks (deferred)
8cadc000 8cae6000 mssmbios (deferred)
8cae6000 8caf3000 umbus (deferred)
8caf3000 8cb27000 usbhub (deferred)
8cb27000 8cb31000 flpydisk (deferred)
8cb31000 8cb42000 NDProxy (deferred)
8cb42000 8cb94000 ADIHdAud (deferred)
8cb94000 8cbc1000 portcls (deferred)
8cbc1000 8cbe6000 drmk (deferred)
8cbe6000 8cbfd000 usbccgp (deferred)
8cbfd000 8cbfe700 USBD (deferred)
8d807000 8d80f000 NuidFltr (deferred)
8d80f000 8d817000 mouhid (deferred)
8d817000 8d822000 point32k (deferred)
8d822000 8d828c00 LHidFilt (deferred)
8d829000 8d82f700 LMouFilt (deferred)
8d830000 8d839000 Fs_Rec (deferred)
8d839000 8d840000 Null (deferred)
8d840000 8d847000 Beep (deferred)
8d847000 8d853000 vga (deferred)
8d853000 8d874000 VIDEOPRT (deferred)
8d874000 8d87c000 RDPCDD (deferred)
8d87c000 8d884000 rdpencdd (deferred)
8d884000 8d88f000 Msfs (deferred)
8d88f000 8d89d000 Npfs (deferred)
8d89d000 8d8a6000 rasacd (deferred)
8d8a6000 8d8bc000 tdx (deferred)
8d8bc000 8d8d0000 smb (deferred)
8d8d0000 8d918000 afd (deferred)
8d918000 8d94a000 netbt (deferred)
8d94a000 8d953000 ws2ifsl (deferred)
8d953000 8d969000 pacer (deferred)
8d969000 8d977000 netbios (deferred)
8d977000 8d98a000 wanarp (deferred)
8d98a000 8d9c6000 rdbss (deferred)
8d9c6000 8d9d0000 nsiproxy (deferred)
8d9d0000 8d9d2440 FileDisk (deferred)
8d9d3000 8d9d6200 elrawdsk (deferred)
8d9d7000 8d9db380 ElbyCDIO (deferred)
8de07000 8de61000 csc (deferred)
8de61000 8de78000 dfsc (deferred)
8de78000 8de85000 crashdmp (deferred)
8de85000 8de8f000 dump_diskdump (deferred)
8de8f000 8deb4000 dump_nvstor32 (deferred)
8deb4000 8dec5000 dump_dumpfve (deferred)
8dec5000 8decf000 Dxapi (deferred)
8decf000 8dede000 monitor (deferred)
8dede000 8def9000 luafv (deferred)
8df01000 8dfb0000 spsys (deferred)
8dfb0000 8dfc0000 lltdio (deferred)
8dfc0000 8dfd3000 rspndr (deferred)
8dfd3000 8dfdc000 asyncmac (deferred)
94210000 94412000 win32k (deferred)
94430000 94439000 TSDDD (deferred)
94450000 9449c000 ATMFD (deferred)
944a0000 944ae000 cdd (deferred)
9a80a000 9a875000 HTTP (deferred)
9a875000 9a892000 srvnet (deferred)
9a892000 9a8ab000 bowser (deferred)
9a8ab000 9a8c0000 mpsdrv (deferred)
9a8c0000 9a8e0000 mrxdav (deferred)
9a8e0000 9a8ff000 mrxsmb (deferred)
9a8ff000 9a938000 mrxsmb10 (deferred)
9a938000 9a950000 mrxsmb20 (deferred)
9a950000 9a977000 srv2 (deferred)
9a977000 9a9c3000 srv (deferred)
9a9c3000 9a9cf000 tcpipreg (deferred)
9a9cf000 9a9ec000 SbieDrv (deferred)
9ae08000 9aed2620 css_dvp (deferred)
9aed3000 9aefb000 fastfat (deferred)
9aefb000 9afd9000 peauth (deferred)
9afd9000 9afef000 cdfs (deferred)
9afef000 9aff9000 secdrv (deferred)

Unloaded modules:
8def9000 8df01000 drmkaud.sys
82f7e000 82f8b000 crashdmp.sys
82f8b000 82f95000 dump_storpor
82f95000 82fba000 dump_nvstor3
82fba000 82fcb000 dump_dumpfve

Once again, I look forward to any assistance or suggestions you awesome people have to offer.


RandomUser... Will look into checking out a bios update and the suggestions you offer. I have not checked for a bios update since I first installed the MB back in Jan or Feb of 2007. Will wait to hear results from others first before I try that. Stay tuned for the results and thanks to you too. I am always open to suggestions. I have done plenty of bios updates before on previous mb's and other devices, so I am comfortable in doing that procedure.

tb39,

Could you provide some more information?

Have a Look through the System Events in the event Viewer and tell us if you have errors relating to Specific DLL, SMBIOS, ACPI, Or Disk Errors?

This is so I can better understand what's going on, and I'd like to compare it to the Debugger output

Thanks

The debugger output is truncated (cut-off) - here's the reason for it:

c0000005 Exception in ext.Analyze debugger extension.
PC: 74737953 VA: 74737953 R/W: 8 Parameter: 0001003f

This is an error in the debugger when it accesses your memory.

Argument 1 indicates that this is an entire process (not a thread) that's crashing.

Arguments 2 and 3 are in the 8e59xxxx range - and there are no corresponding listings in the listing of loaded modules. This could be because the process already crashed and doesn't reside there any longer, or that there's a problem with your system.

Arguement 4 points to ntkrpamp (a Windows system file) but there's no mention if this is just a symbol issue, or it's related to the problem at hand (which you'd assume was the case since it's included in the arguments).

Interesting, a Google for " ASUS Crosshair 0x000000F4 " (without the quotes) gives these results: http://www.google.com/search?hl=en&cli...amp;btnG=Search A good long read of just the first page of results has many, many suggestions. Most relate to memory issues and various fixes for them.

So, it seems that this is a fairly common issue with this model of motherboard. I would perform the Vista memory diagnostic in order to rule out the memory ( http://www.bleepingcomputer.com/tutorials/using-vista-windows-memory-diagnostics-tool/ ). I would check in your BIOS to ensure the memory timings and voltage where adequate for your RAM (you can get the proper settings for your RAM from the RAM manufacturer's website).

Also, check the Asus website for BIOS updates that may address this issue. If you're unsure, post the version of your BIOS and we'll have a look here: http://support.asus.com/download/download....model=CROSSHAIR

tb39 ,


What features of the board are you using? CPU Level Up?? Have you overclocked the system manually?

I think you want to enter safe mode, un-install all drivers, then Re-install starting with the Chipset drivers, then
go back and Update the bios. Turn off overclocking features before doing this, as you'll want to doing this under
the easiest cirumstances.

I didn't think about this until seeing the board features.

Further, If you go into the BIOS, is there an Option to change the HPET feature? (High Precision Event Timer)
If so, what's the current setting?

usasma & RandomUser,

Event Viewer did not show anything unusual at time of BSOD (no DLL, ACPI, SMBIOS or disk errors).

I have read a few of the articles in the google search link you provided. Will do more research on that as soon as possible.

I ran the Vista memory diagnostic on my Corsair XMS2 memory modules (2 X 1024). I let it run the entire time I went over to the parents for Thanksgiving dinner (3.5 hours). 35 passes later, it showed no errors. I also ran Memtest86 for a single pass and it reported no errors either. My next task would be to update the BIOS and possibly uninstall / reinstall MB drivers. I am running Version 121 (the initial BIOS). I never bothered to update it as my system never encountered a problem until 2 to 3 months ago. I have downloaded all of the updates plus the Award Flash Utility (unfortunately this has to be copied to a floppy and my system has no floppy drive). Now all I have to do is locate the MB DVD which has a utility that will let me update the BIOS in a Windows environment. I placed it aside as all it had were drivers for XP and were not compatible with Vista. When I do update the BIOS, should I go to the latest one or should I do it in increments? There have been 9 revisions since the one I am using.

My initial reason for getting this board was for the overclocking features but I decided against it and left everything at the default settings. I did not notice anything in the BIOS about a HPET feature. I will take another, closer look and get back to you.

Thanks again for all your help and suggestions. I can not wait to tell you that all is well again and no more BSOD! I am moving this weekend and will have a limited amount of time where I can check this forum. If I go silent for a couple of days, that is why.

Two notes,

1) you may want to pick a an external USB Floppy drive to update the BIOS. You might be able to do this from a thumb drive instead.

2) Read the bios notes and see if any of them list resolution to your specific issue. IF you aren't able to determine this, use the current version..


Good luck with your move this wknd.

DO NOT JUMP ALL 9 versions of the BIOS. While it's supposed to work, there have been too many horror stories that I have heard. Generally it's recommended to jump no more than 3 versions - but in your case I'd jump as little as possible - with the last 2 being done for sure.

BIOS flashes are dangerous - so be very careful and triple check everything to make sure that you've got the right files to flash with. Don't let anything interrupt the flash, and don't get antsy fingers when it's running. Print out the directions and follow them exactly.

usasma & RandomUser,

In terms of the BIOS... in the past, if there was quite the jump in versions, I always did it incremental for that same reason. The nice thing about my previous MB's was that they were Gigabyte boards with dual BIOS setup so if one failed an update, you had the other one as a back up. Even the boards that I had that did not have a dual BIOS, upgrading them was never a problem (knock on wood) so I'm not that worried about it. I will only jump a couple of revisions at a time. I know to follow the instructions to a "T" and to always play it cautious.

I have a 8GB USB thumb drive but the bios would not recognize it even though the instructions said that could work. Maybe I just have to enable something to get that to work. One of the revisions mentioned something about memory handling and a SATA update so I'll at least go up to that version or make sure that update is installed before going on to the next one. Once I do that I will report to you all to let you know how it went.

Thanks for the "Luck" with my moving. Moving really stinks!

Thanks again for all of your suggestions. I'll report back to you soon.

Good day all... especially usasma & RandomUser,

All right... I did my bios updates via a bootable cd. Did every other one until I came to the last one. Then it happened... I got a CMOS checksum error and could not even enter the BIOS setup screen or boot from the CD. At that point I thought I had jacked the computer up but a simple reset of the CMOS allowed me to enter into the BIOS again along with booting from the CD. I reinstalled one of the older BIOS updates over the latest one and all was good. One of the BIOS updates had an update for the SATA controller, so I made sure that it was one of the ones that I used for an update. According to Windows, the SATA controller driver was the cause of all the BSOD's.

To this point, I have not encountered any BSOD's and I have let my computer sit idle on several occasions with different programs running or none at all. So, at this point, I would consider it a success. Thanks for all your help and suggestions! If anything further happens, I'll be sure to let you all know.

TTFN...

tb39