BSOD 0x0000000a 0x0000001e 0x00000050 0x0000003b

Useless User · 08 Sep 2014

Sorry, sure, here the SF Diagnostic Tool ZIP-folder comes attached.

Arc · 08 Sep 2014

The DV enabled driver is also failing to identify a driver to be the probable cause.

Code:

BugCheck D1, {0, e, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

So it is not a driver caused BSOD, and here is the proof.

Code:

BugCheck 124, {0, fffffa801168c028, f2000000, 20001}

Probably caused by : GenuineIntel

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

Stop 0x124 indicates hardware failure. Technically it is called WHEA_UNCORRECTABLE_ERROR; where WHEA means Windows Hardware Error Architecture.

Follow Stop 0x124 - what it means and what to try.

If if have any questions relating to it, let us know. Also let us know about your advancements.

Useless User · 08 Sep 2014

Thanks, that's really good to know. Since the memory memtest86+'ed ok, it can "only" be the processor or mainboard, right? So, which of the two is it? I looked at your link regarding BSOD 0x124 - please see my answers below:

1) No overclocking takes place.

2) Temperature never exceeded 57° to my knowledge (HWMonitor, Core Temp) prior to the re-install.

3) I updated the drivers as part of the re-install.

4) I flashed the BIOS to the latest version and left it well alone.

5) Windows is updated.

6) I ran mdsched and memtest86+ with no negative result and chkdsk /r found no problems.

7) I encountered the BSOD 0x124 first time after the initial re-installation of Windows. My hardware components were purchased in December 2012, so the warranty on the processor and mainboard has long since expired : (

8) Before re-installing, I cleaned the PC's interior so it looked like new. It was very clean in the first place, running in a nearly dust-free room. I checked all connectors and re-seated the RAM bars as part of the memory testing procedure.

9) I do not have a spare processor or mainboard to swap them out : (

"Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware."

Yes, something seems fundamentally wrong with my machine's hardware. But what is it? Knowing my luck, I know what will happen: I order a new processor tomorrow, swap it out, and then find out the mainboard is the culprit or vice versa. Or, even worse, the processor and mainboard are both defective.

I hate computers. I was born in an era where the fax machine seemed science fiction to most. Society needs self-diagnosing computers with auto-repair option; too much time goes into troubleshooting these things, doesn't it?

You have experience - what would you do in my case? Buy a new processor first or a new mainboard? If I must buy a new processor, would you buy the same or is there a faster one for this type of mainboard? Or should I be bold and buy a newer processor AND mainboard and consign the "old" parts to the attic?

Thanks!

Arc · 09 Sep 2014

You cleaned the inside of the computer. Did you clean the fan of the CPU too? Did you remove the fan while cleaning it? Have you applied thermal paste to the heatsneak before seating it again?

Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

After knowing the heat, we will decide the next step.

Useless User · 09 Sep 2014

Sure, I cleaned the PC's innards like a clean-room facility clerk.

I shall download and install HWMonitor, Real Temp and Core Temp and Speccy and install a simulation software so I can mimick regular use whilst recording temperature; next weekend, once back home, I upload the results plus whatever new BSOD occurred.

Useless User · 13 Sep 2014

Ok, back on the PC. While I was away, the PC was idle and one BSOD occurred. I installed Speccy (text file attached) and monitored the temperature. You can see from the attached screenshot that with prime95 & IntelBurnTest running together, I manage to raise the CPU temperature to 60°C. Attached is also the zipped SF Diagnostics Tool information with two new BSODs that occurred today.

By the way, I don't quite understand why my 3.2GHz CPU is shown running at 3.5GHz? If you remember, before the reinstallation of everything, I flashed the BIOS and never touched it (I wouldn't know how to fiddle around with it anyway).

Is it possible with the newly attached information to find out, whether I should buy a new mainboard, processor or both?

Thanks!

Useless User · 13 Sep 2014

Pump...

Useless User · 14 Sep 2014

Thump...

Arc · 14 Sep 2014

Useless User said:

Pump...

Useless User said:

Thump...

Useless User said:

Pump...

Arc said:

Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

After knowing the heat, we will decide the next step.

#14

Useless User · 14 Sep 2014

Speccy file was attached... ain't it readable? I can open it in Word Pad. I attach a fresh one...