hal.dll+12818 and ntoskrnl.exe+c9e4a BSOD

[Rcktstar]

So I just made this computer installed windows and I have been getting BSOD ever since I started the computer. It just does it randomly usually 5-10 mins after I have the computer on. It doesnt BSOD while I am on safe mode. I ran a memtest for 4 passes (not sure if i should have waited some more). Computer crashes before I can finish a stress test with Prime 95 and doing a GPU test right now with Furmark. Any help would be greatly appreciated.

 

[Arc]

Crash dumps are pointing to hardware issue, out and out.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.

But your statement .....

It doesnt BSOD while I am on safe mode.

..... contradicts with the crash dump reports. If it is a hardware issue, then it should continue in safe mode, too.

At this very beginning stage of troubleshooting let us assume that the issue is being caused by any device driver. So 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:

Computer crashes before I can finish a stress test with Prime 95 and doing a GPU test right now with Furmark. Any help would be greatly appreciated.

Another strong point in favor of hardware issue.

Run Prime 95 again ..... let us see the prime95 log.

 

[Rcktstar]

My Prime 95 isn't producing a log im guessing because it blue screens

One did say something different then the usual "a problem has been detected" nonsense, it said "A clock interrupt was no received on a secondary processor within the allocated time interval" while I ran and had the computer blue screen on me after running Prime95. Not sure if this helps in any way

 

[Arc]

Download prime95 on your desktop. Extract the zip in a new folder. Now run prime95 from that folder.

Search the folder later, for any newly created text documents.

Items before running prime95 ....

View attachment 357224
​

Items after running prime95 ...

View attachment 357225
​

If you run prom95 from within the zip, you will not get the logs.

Crashes during the stress test is enough to say that the hardware is failing, by the way.

 

[Rcktstar]

Anyway to find out what part is causing the problem?

I also attached the prime.txt, and the local.txt

 

[Arc]

I would say you two things.

First, I ran prime95 for a few seconds only, to show you that it generates the logs, but none of them ate teh required log, that is prime.log.

View attachment 357301
​

Second, it the CPU is failing during a stress test, you should plan to replace it as soon as possible.