Need Help With Blue Screen of Death Problem 0x0F4

iiXeno

Commendable
May 10, 2016
4
0
1,510
Hello!

I have a custom built PC and it has been giving me problems in the the last 6 months with 0x0F4 BSOD. I looked around, I seen a few mentioning it was related to HDD issues but I let it persist a little and eventually the restarts would fail to launch windows 7. But when I pressed "Start windows normally" sometimes it would freeze in the middle of when those colored dots come together to make the windows logo, so I would have to keep restarting or shutdown and power up again until it went through to my desktop.

I wiped it a couple times and every time I wipe it, within a week it blue screens again and the first blue screen after the new wipe, it would be slow and unresponsive, especially when I open the Internet browser. So I got another HDD and the new one is not the problem because I am still getting that same code and the same symptoms after the first blue screen.

My first HDD doesn't launch anymore no matter how many times I restart and when I do press start windows normally, it does the windows logo but never goes to login, it bluescreens after the logo with a 0x0ED, I HAVE to wipe it but right now I'm using my replacement HDD. I'm thinking the motherboard is bad but I want to be sure because I am actually trying to sell this computer and I want to have this solved before I do that.

I have swapped the RAM out to the two other slots, I have switched SATA cables and power cables, and have taken the CMOS battery out and back in.

PARTS LIST: http://pcpartpicker.com/user/iiXeno/saved/4YhWGX


Any help thanks. Also, I have installed "Bluescreen View" so next time I will have the dump files to upload when it happens.
 

iiXeno

Commendable
May 10, 2016
4
0
1,510


Pro 64 bit. It's "official".
 
the error indicates that a windows component detected a error. Often it will be caused by the component being modified while in memory. This is not allowed any more and it is assumed to be malware. if windows detects the change it will shutdown with the error code.

the memory dump will show the drivers and there is a debugger command to tell you if the windows file has been modified. Sometimes it is just a few bits and is likely to be a hardware bug. Sometimes a lot of code is changed and it would likely be a hack or malware.

you can put your memory dump on a server, mark it for public access and post a link if you want me to take a quick look.
(it will also show the reason for the error)
here is the debugger command if someone want to check.
!for_each_module !chkimg @#ModuleName