Solved Freeze then BSOD(error 0x0000004F & 9c) after 1-5 minutes of use

[rkzduke]

Hello all,
For several days now I have been dealing with a BSOD that occurrs between 1 and 5 minutes after starting up windows(safe and normal modes alike).

I need help finding the solution to this problem and am hoping the experts here can assist me with that.

I have Removed and swapped the 3 RAM sticks I have and they all appear to be working(ie the comp still froze after a few minutes) no matter what configuration with 2 of the 3 I had attatched.

Originally I was getting a 0x0000009c(screenshot here) BSOD error but after I logged and changed(in my short window before freezing) the Dump setting from Kernel to Minidump along with unchecking "automatically restart on crash" it changed to a 0x0000004F(screenshot here) error code and I have been getting the F4's ever since.

When doing ChkDsk at startup, it ALWAYS freezes on "CHKDSK is verifying indexes (stage 2 of 3)... 40 percent complete." Then after roughly 4 minutes I get a message saying an Unspecified Error occurred fixing $I30 (Screenshot HERE).

Boot disk 'fixers' do not do anything useful(Windows Memory Diagnostic(no probs detected), etc) and I have resorted to attempting an sfc /scannow /offbootdir=e:\ /offwindir=e:\windows and it begins, except after 1 minute to comes back saying "Windows Resource protection could not start the repair service."(and yes, the drive is right based on the boot disk detecting where windows OS was located and not my C drive where it is when I boot up). This seems coincidental since it halts roughly the same amount of time as the chkdsk on boot takes to at the 40% mark where it freezes.

In my short window before it freezes after startup, I did manage to verify the services.msc module was on manual(not sure if that matters to the boot disk sfc) and I am at a loss as to where to go from here.

My Crash Dump files: View attachment 302106

 

[Arc]

Most of the necessary files are not there in the zip, including crash dumps.

View attachment 302156

Do it again. Do Option two, too.

 

[rkzduke]

My computer is not creating Dump files that I can find in the Minidump folder. I followed the instructions in these forums for them to put it on manual and changed Kernel to Minidump[256k]. Cannot remove 'Read Only' from my minidump and Kernel files inside Windows directory if that has any bearing on this problem.

 

[Arc]

OK, wait for the next BSOD. Check manually in C:\Windows\Minidump if there is a crash dump saved or not. If saved, follow both the option one and option two of the posting instruction. Either of them will grab the dumps.

But if there is still no dumps, go to the tutorial link again. Get the registry file for minidump and merge it.

 

[rkzduke]

I managed to get the Reg file merged successfully it said, but since then 3 crashes and no minidump file.

Also, on these Diagnostic tools I hit grab all and it says it got them all but then I see afterwards a 'System Info' window pop up and a slow green bar seems to be working still. It is way too slow for my short window before crashing to complete so it hangs up every time.

 

[rkzduke]

I give up, am going to guess that the Indexing Errors I keep receiving while doing chkdsk along with the repeated failures trying to follow the debug/graball tools equates to a failure in my SSD.

I really wish there was a good solid tool that you could boot to which could analyze your Drives and other hardware. Seems that coming to BSOD forums and the only fix they can offer requires you to run off of your boot drive is not going to work for 50% of people.

Anyhow, thanks for the attempts at helping me and I will report back when I install the new SSD.

 

[rkzduke]

Bought a new Samsung 840 EVO SSD and it fixed the problem. Thanks for the help.

I suspect the Dump files could NOT be written because my SSD(boot drive) was completely frozen up because it only crashed when it did freeze up and thus no Dump file could be written onto it. Hopefully you all learned something too for helping people out in the future.