Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD - Clean Install - Bugcheck code: 0xF4

21 May 2015   #1

Windows 7 Ultimate x64
BSOD - Clean Install - Bugcheck code: 0xF4


First time posting here so thanks in advance for any help, I'm pretty stuck, got a little bit of experience with PC repair so not an idiot (you can judge that haha) but not as much as all of you so bear with me please!

Initially had an issue with the PC Being stuck in a loop and I use it for work. So decided to play it safe and buy a new hard drive start off fresh with a clean install. This is my second attempt at the install now after sluggish behaviour and some BSOD's last time round. Decided to start again and only do the Important updates not the optional ones and still having the same issues. May possible inclination may be due to having a 2tb Drive as OS drive after reading a few threads but i'll see what you all think.
Previously to these issues the PC has been running great for over 2years.

All that I'm doing previous to the BSOD is running the windows updater trying to get to the stage where I can start to copy my files back.
As far as I'm aware the memory is okay after using the windows memory diagnostic test
Looking at 'Speccy' nothing seems to be overheating or overworked.
To add boot time takes a good five minutes but shutdowns in seconds
I don't know how relative all the above info is but trying to be as concise as possible and give as much info.
After enabling minidumps I used Whocrashed for some help diagnosing (ended up gibberish to me)
The report I ran from WhoCrashed provided the following:

On Thu 21/05/2015 11:39:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052115-27955-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DA0DB30, 0xFFFFFA800DA0DE10, 0xFFFFF80002DC1940)
file path: C:\Windows\system32\ntoskrnl.exe
Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Minidump zip attached - again thanks in advance for any help.

My System SpecsSystem Spec
21 May 2015   #2

Windows 10 Pro/ Windows 10 Pro Insider

Hello, CJG and welcome to the forums. I will try to help with your problem. You only had 2 dump files, but they were both the same.

A process or thread crucial to system operation has unexpectedly exited or been
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.
Arg1: 0000000000000003, Process
Arg2: fffffa800da22b30, Terminating object
Arg3: fffffa800da22e10, Process image file name
Arg4: fffff80002d8b940, Explanatory message (ascii)
Please run Seatools for DOS on your hard drive. Run the short and the long test on any internal or external drives you have.SeaTools for DOS and Windows - How to Use

After that please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Let me know the results of the scans. Do you have your older hard drive connected to your computer. What else is connected other than keyboard and mouse?
My System SpecsSystem Spec
21 May 2015   #3

Windows 7 Ultimate x64

Hi essenbe,

Thanks for helping i saw you pop up on a few threads. I'm out right now but will do as you requested and post the results soon as i can.
With regards to the last question you asked i can confirm that nothing other than keyboard and mouse are connected (wireless - but drivers were downloaded and running smoothly it seems). Old hard drive as well as any other storage drives were disconnected previous to fresh install.
Only other connections are internal components - Graphics Card, RAM and Wireless Card.

Will run tests later this evening and post back,

My System SpecsSystem Spec

21 May 2015   #4

Windows 10 Pro/ Windows 10 Pro Insider

Ok, no hurry, just whenever you have time. A stop code of F4 is in many cases a hard drive problem, but not always.
My System SpecsSystem Spec
21 May 2015   #5

Windows 7 Ultimate x64

Well Just in and ran the Seatools short test with a failure and error code. Havent done the long test or the other test you suggested as i guess its not worth it? I guess my best move is to contact the supplier of the HDD and ask for a replacement as its brand new. Really annoying as i have taken great care on install and its been a fail from the start :/
Although at least its not like one i bought from Misco who sold me a NEW hard drive which jsut so happened to have someone elses Windows 7 and files on it..... had to double check i hadnt bought B-stock lol they then took forever to give me cashback as i refused to do business with them over a fault like that haha

So yeh Essenbe... should i run the other tests? :S
My System SpecsSystem Spec
21 May 2015   #6

Windows 10 Pro/ Windows 10 Pro Insider

No reason I can think of. It has already told you what you wanted to know. Just exchange the Hard drive for a new one. I certainly hope you can. I would clean the hard drive as well as I can before returning it. I can tell you how to clean it pretty well, if you need help. By cleaning it, I mean wipe all of the data off of it.
My System SpecsSystem Spec

 BSOD - Clean Install - Bugcheck code: 0xF4

Thread Tools

Similar help and support threads
Thread Forum
Multiple BSOD's. Latest Bugcheck code: 0xF4
Hello All, My computer has been suffering BSOD's for months and I'm at wits end. I built a new system awhile back and the only thing carried over was the SSD. Crashes were happening on the old computer too. Crashes happen randomly so I can't say "if I do this then it crashes". Thought it was...
BSOD Help and Support
Problems with booting (The bugcheck was: 0xF4)
Hi I've got a Windows 7 Home Premium x64 computer that occasionally can't be booted. When its power if first turned off and then on it boots. Subsequently though, when it's shut down from Windows, it won't boot again. It will show the "Starting Windows" screen with the windows logo animation as...
BSOD Help and Support
Random BSOD occuring only in a particular account. Bugcheck code: 0xF4
I have been getting random BSOD only in a particular account. The BSOD is very random. In the other account I have tried running Driver verifier however I could not see any crashes. Here is a short report on the bugcheck This was probably caused by the following module: ntoskrnl.exe...
BSOD Help and Support
BSOD Installing drivers after a fresh windows install, Code 0xf4
My computer was suffering from random bsods and viruses before. I atributed the bsods to viruses, but after reinstalling windows 7, I found that the bsods still happened. It seems to happen when installing drivers, or running prime95. Booting into safe mode allows me to pretty much do anything. ...
BSOD Help and Support
BSOD again. Bugcheck 0xF4 Unknown Critical Object.
Once again I humbly approach the alter of debuggers. BSOD have begun again at random times. I've run Malewarebytes and found nothing. Whocrashed doesn't help much: crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown () Bugcheck code:...
BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 13:33.
Twitter Facebook Google+