Random BSOD: STOP 0x000000f4

[JoeDBean]

Hi all.

Just built my new system 3 weeks ago:
Windows 7 Home Premium Retail 64-bit
i5 2500k
ASrock Z68 Extreme4 Gen3
8GB G.Skill RipjawsX 1600MHz RAM 9-9-9-24
60GB OCZ Agility 3 SSD
1TB Western Digital Caviar Black
MSI GTX 560 Ti 2GB Twin Frozr II

The BSOD has been happening randomly, but most frequently when in Google Chrome. In which case, an error message would appear saying something along the lines of 'Chrome has crashed'. This was shortly followed by a BSOD.

I downloaded BlueScreenView from nirsoft.net and ran the test on my latest dump file. The result came back with this: 476ba0efaf03464f259cb3379b6696cd.png

Something called 'ntoskrnl.exe' is highlighted in red.

What is this file? Is there a fix for this? The only thing on ms 60GB SSD is Win7 and a few programs, therefore a fresh install isn't too much trouble (if a fresh install would be the be all and end all of the issue).

If any more info is required, please ask and I shall provide.

Cheers
Joe.

 

[JMH]

Hello JoeDBean,

> FYI
Please refer to a similar issue / thread worked on over the last few days here...
http://www.sevenforums.com/crashes-debugging/205970-bsod-0x00000f4.html


> We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[JoeDBean]

Ok, thanks for that.
Just an update, I did a fresh install of Windows 7. I installed all drivers again, and then installed windows updates until none were left.
During the process of updating, the same BSOD happened again.

I have attached the dump file from this BSOD as you said.

Could this be keyboard related? I watched a video linked in another thread that said when 'ntoskrnl.exe' appears to be the problem (thats what BlueScreenView said), the keyboard may be the issue. I just wondered as I sometimes (only for a few seconds) experience brief periods where the keyboard doesnt work and I hear a sound as if I just unplugged a USB and plugged it in again. I have a Microsoft keyboard, however, so I don't expect this to be the issue.

Cheers
Joe.

 

[JoeDBean]

Okay, I did a 'CHKDSK /R /F' on my C: drive from an elevated command prompt.
Here is the result:



Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
86016 file records processed. File verification completed.
93 large file records processed. 0 bad file records processed. 0 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
121328 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
86016 file SDs/SIDs processed. Cleaning up 292 unused index entries from index $SII of file 0x9.
Cleaning up 292 unused index entries from index $SDH of file 0x9.
Cleaning up 292 unused security descriptors.
Security descriptor verification completed.
17657 data files processed. CHKDSK is verifying Usn Journal...
35360040 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
86000 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
7124192 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

58510335 KB total disk space.
29774504 KB in 68196 files.
49632 KB in 17658 indexes.
0 KB in bad sectors.
189427 KB in use by the system.
65536 KB occupied by the log file.
28496772 KB available on disk.

4096 bytes in each allocation unit.
14627583 total allocation units on disk.
7124193 allocation units available on disk.

Internal Info:
00 50 01 00 6a 4f 01 00 61 98 02 00 00 00 00 00 .P..jO..a.......
47 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 G...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[JMH]

Joe,

If you are overclocking STOP!

Your crash occurred at a very early stage.
Please boot in to Safe Mode & run SFC.
Let us know the results at the end.


http://www.sevenforums.com/tutorials/69585-safe-mode.html

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[JoeDBean]

How did you know I had overclocked previously?
Since I have overclocked, I have reinstalled Win7 twice, changed the BIOS from v1.00 to v1.10 and back to v1.00 and cleared CMOS on my motherboard (not in that order). My overclock is no longer being used, either.
I will run a SFC when I get home; I'm leaving for school now (I'm in the UK).

Cheers,
Joe.

PS, in the file I attached, there is a second dump file. This happened while doing a 'chkdsk D: /r /f' (on my D: drive). Different error code: 0x0000007A.

 

[JMH]

Joe,

Real life calls me.
>Will check your new DMP my tomorrow.

> Remember to post the SFC results.

> In the interim check your hard disk for errors.
http://www.sevenforums.com/tutorials/433-disk-check.html

 

[JoeDBean]

I have attached the SFC results. I didn't want to copy/paste them all as the post would have been really long

I will edit this post after I have finished checking my hard disk.

Cheers,
Joe.

 

[JMH]

Joe,
If SFC scans without finding any problems, you should receive the following message: "Windows resource protection did not find any integrity violations". {or similar wording}
Please re scan using Option 2 in the Tutorial.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[JoeDBean]

Yes, that was the message I received. When I did the scan, I repeated it 3 times anyway, all with the same result.

 

[JoeDBean]

WOAH just had two BSODs within about 3 minutes of each other. One was the code 0x000000f4 and one was 0x0000007A.
Dump files attached.
I'm thinking its my D: drive. I've left my system to idle all day and used it for general use for about 4 hours when I got home without the D: drive connected and no BSODs to report. Connected the D: drive and I get two after just a couple of hours.

EDIT: I'm gonna go to all lengths to get this fixed. I'm formatting my D: drive. I'm re-installing Windows on my C: drive. BIOs v1.00 is on the motherboard. CMOS is cleared. Hopefully all this should rule out software error.

 

[JoeDBean]

Another BSOD for someone to take a look at. Sorry for the bombardment.
This happened during the formatting of my D: drive.

 

[JMH]

Your DMP analysis was inconclusive.

If you are overclocking anything reset to default before running this test.
In other words STOP!!!

As a driver appears to be the culprit please run ....

> Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users