BSOD that is random and unpredictable

Hi guys,

Recently, I have been experiencing BSOD a couple of times, it started a few months back, maybe once or twice a month, i tried to isolate the hardware to find out what is causing the BSOD but to no avail.

It was hard to do troubleshooting as it does not always happen. However when it does, after the BSOD, the computer will attempt to reboot again, but it will keep booting up and then shutdown again, repeating a few times before successfully booting it back to the user log in. The phase where it boots up and shutdown repeatedly, to put in more details, it's like when you turn on your computer, you will hear the fans running, LEDs coming on etc etc, then it will immediately shut back down, and repeat again.

Since yesterday, i have already experience BSOD about 3 times, and now, my computer has been restarting on it's own, no BSOD nothing, no warning as well.

To add on, the BSOD happens as and when it likes, sometimes gaming, web browsing, etc etc, even when it's just idling.

I'm not sure what is causing it as I do not have much knowledge on problems like these. Will appreciate all help, below is the log generated.

Thanks in advance.


Update 1

I have run the memtest86 and have 8 consecutive passes, guess we can eliminate the suspect of the RAM.

Update 2

The BSOD is very random, everytime it happens, the error is completely different, sometime services, sometime some initialisation isssues. Therefore I decided to do a reformat to eliminate the software suspect, and it is still happening, but far lesser than before reformat, I seem to notice the frequency tends to increase if I'm using anything that has got to do with Java.

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88004628812, fffff880009a9128, fffff880009a8980}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

Code:

BugCheck 1A, {5003, fffff70001080000, 630, 772e0005}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29041 )

Followup: MachineOwner
---------

Code:

BugCheck A, {fffff70405006c30, 2, 0, fffff800032bd492}

Probably caused by : memory_corruption ( nt!MiReplenishBitMap+48 )

Followup: MachineOwner
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

** EDIT: Before enabling Driver Verifier, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Otherwise windows will refuse to go to the desktop with DV enabled.