Solved BSOD 0x51 shortly after startup

[dalmacietis]

This week I have been using my PC normally, but today I suddenly started getting BSOD some 30-60 seconds after Windows is started. This happened for 3-4 times, I tried going into safe mode, but the screen froze for more than 1 minute with glitchy textures at the top. I did a hard reboot, then let the automatic CHKDSK on boot run, didnt see anything suspicious, but after it was done got BSOD again. Finally did a hard reboot and tried safe mode again, and this time it worked. I left the PC for some time and it was fine. Now I restarted it normally and it seems to work for the time being.
I will appreciate any help analyzing the logs. Zip file is attached.
Thanks,
Arnis

 

[axe0]

I would like to have a look at the health of the drives.
Please go to Download – Crystal Dew World and click the blue zip button which will download a portable version of CrystalDiskInfo. Extract the zip file and run diskinfo64.exe which will ask for administrator rights, please allow it.
CrystalDiskInfo uses 3 colors for indication
Blue = good
Yellow = warning
Red = bad

A little below the menu you'll see drives with each a circle with color, if any of these is NOT blue please click it.
Before making a screenshot, please do the following
- Go to function > Advanced feature > raw values, change it to 10 [DEC]
- Make sure all attributes are clearly visible
Make a screenshot of CrystalDiskInfo and post this screenshot in your next post.

 

[dalmacietis]

Thanks for the reply.
One of the drives (X) does have 2 warnings, screenshots are attached.
One thing that I didn't make clear is CHKDSK only ran on drive C where Windows is. So I'm guessing I will need to do some checking for drive X?

FYI I am getting BSOD after startup most of the time, but I can launch safe mode with networking. I also tried a clean launch, and still get BSOD.

 

[axe0]

You could run chkdsk on X, but it won't resolve all of the problems. Chkdsk will fix any file system problems and some physical problems, but it can't solve all physical problems.

You can see there are 24 pending sectors that need to be addressed, but your hard drive can only address 10 sectors total and 14 sectors will be left alone. Since 14 sectors cannot be addressed there's a chance that data could become corrupted when they're stored in any of those 14 sectors. It's only a matter of time before that happens which will result in either program crashes, more BSOD crashes or file corruption.

My recommendation is to replace the drive asap, after backing up any data you don't want to lose. After the drive is replaced, please let me know whether the crashes continue or not. While replacing the drive is likely going to solve the crashes, we will need to confirm it still.

 

[dalmacietis]

Hi, I did chkdsk /r /f on the X: drive, which I believe found some bad clusters but otherwise finished without anything interesting.
After launching the PC after the chkdsk i got crash again.

So I disconnected the X drive and tried launching (twice), but I am getting the same crashes anyway. What would be the next steps?

 

[axe0]

The next step would be testing the memory with memtest86+ :ar: RAM - Test with Memtest86+

 

[Dovahkiin958]

This week I have been using my PC normally, but today I suddenly started getting BSOD some 30-60 seconds after Windows is started. This happened for 3-4 times, I tried going into safe mode, but the screen froze for more than 1 minute with glitchy textures at the top. I did a hard reboot, then let the automatic CHKDSK on boot run, didnt see anything suspicious, but after it was done got BSOD again. Finally did a hard reboot and tried safe mode again, and this time it worked. I left the PC for some time and it was fine. Now I restarted it normally and it seems to work for the time being.
I will appreciate any help analyzing the logs. Zip file is attached.
Thanks,
Arnis

Hello Arnis!
According to Carrona.org, The STOP 0x00000051: REGISTRY_ERROR Usual causes are: Hardware failure, File system corruption and Security issues. I honestly think its hardware starting to fail, So here is what i think you should do. You should switch your RAM or hard drives and if you want to try changing the processor to see if its that messing up!


Hope this helps,
Dovahkiinrb:

 

[dalmacietis]

So I ran memtest for 9 full passes overnight, no errors.

Then I unplugged every hard drive except C:, and it still crashes if I am not in safe mode.

I'm not sure I have a compatible processor to swap.

Also the error code changed from 0x51 to 0x50 recently for all that matters. I attached the zip with logs again; note that there are a large number of crash logs after I did chkdsk on X:, as I left the PC on its own and it managed to crash and restart around 20 times before I switched it off.

 

[axe0]

Please post the chkdsk event logs.
Check Disk (chkdsk) - Read Event Viewer Log

 

[dalmacietis]

Hi, sorry for the delay, was busy this week.
I tried starting again in safe mode with only the C drive (3 times), and now it freezes after showing "loaded CLASSPNP. SYS" and there are glitchy textures at the top of the screen.
Curiously, it does start in normal mode, but gets BSOD ~10 seconds after launching Windows.
So unfortunately I am unable to provide the logs.

 

[axe0]

Sounds like RAM failure to me, could you remove 1 module and reseat the other module to see if it makes a difference.

You ran MemTest86+ earlier, but please realize that hardware tests aren't able to test everything on the hardware they're designed to test due to complexity. Memtest, for example, needs to load itself which it does into RAM and temporarily keep track of data to show on your screen which is also done in the memory. It's simply not possible for memory tests to test the RAM 100%.

 

[dalmacietis]

Sorry, forgot to respond here. I tested both RAM sticks (separately and together) in all sensible configurations, to no luck.
I ended up getting a new machine.