Solved BSOD 0x0000000a 0x0000001e 0x00000050 0x0000003b

[Useless User]

Dear experts,

after just too many days of troubleshooting (please disregard the former thread) I decided to flash the BIOS, then re-format my SSD and re-install Windows 7 including all drivers the device manager asked for. Apart from BlueScreenView, SF Diagnostic Tool, 7zip and Dropbox, I installed/ran no other software or drivers. Windows update shows me that Windows is updated. I have currently only one bar of 8GB RAM installed; I have a 4-bar 16GB and a 2-bar 16GB kit available that ran fine in an identical PC. The QVL from Asus is from 2011 and outdated; the recommended RAM is no longer commercially available.

Do I need a new processor, mainboard or RAM? A new PC? I sincerely hope not the latter!

I have attached the output from the SF Diagnostic Tool as required. What should I proceed with?

Thanks in advance for any insights!

 

[Useless User]

I downloaded and installed one additional software, IntelProcessorDiagnosticTool and ran it. Result: Another old chap reared its ugly head - the BSOD 0x00000124 where the BSOD display freezes and thus no minidump is being written - I have to push the reset-button each time this particular BSOD occurs.

I mean, being a useless user, I can't tell shit from shinola as far as PCs are concerned, but does this indicate a hardware fault? Such as mainboard, memory or processor?

How can I pinpoint what it is, so at least I know what, in the worst case, I have to buy anew?

 

[Arc]

Hi Useless User (you should change your username. Ask the Admins for it!!).

The series of different BSODs gives a primary sense that there might be something going wrong with the RAM. Make it sure at first.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

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

Let us know the result. Then we will start for stop 0x124.

 

[Useless User]

Thanks. Well, I seem to be pretty useless, a troublehooting twerp, so I leave it as is. Meanwhile, Memtest86+ is doing its thing.

I get back after eight passes, or if another BSOD/freeze ensues while that test is running.

 

[Useless User]

Ok, the PC has done its eight passes of Memtest86+ that took 22 hours and 10 minutes, without an error. What do you recommend me to do next?

 

[Arc]

Ok, the PC has done its eight passes of Memtest86+ that took 22 hours and 10 minutes, without an error. What do you recommend me to do next?

So we may now say that RAM is not failing, apparently.

Next attempt will be to 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.

 

[Useless User]

Yes, the RAM and/or the two mainboard slots it's installed in seem ok. I restarted the PC in normal mode, and after not even a minute, obtained another beautiful BSOD 0x0000001e. I have Driver Verifier enabled as per the instruction linked; let's see what happens next!

 

[Useless User]

Since I have no software installed, other than the above mentioned, I ran IPDT again, so the PC has something to do. Like above, it either ends prematurely or I obtain a BSOD 0x00000124.

Now, I have the Task Manager and IE open to have something going on while Driver Verifier is on. I let it run over night, maybe a useful crash happens.

 

[Useless User]

I got a BSOD 0x000000d1 now, while the PC was idling away, hopefully by way of Driver Identifier.

What's next?

 

[Arc]

Next. let us see it, following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Useless User]

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

 

[Arc]

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

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.

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 http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696.

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

 

[Useless User]

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]

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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

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

 

[Useless User]

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]

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]

Pump...

 

[Useless User]

Thump...

 

[Arc]

Pump...

Thump...

Pump...

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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

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

#14

 

[Useless User]

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