BSOD 0x0000000a 0x0000001e 0x00000050 0x0000003b

Useless User · 16 Sep 2014

And another BSOD, the good old 0x124 is back : (

Please see the attached SF Diagnostic Tool ZIP-file...

Useless User · 16 Sep 2014

essenbe said:

before you do that please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

I have not yet installed my application software, only the SF Diagnostic Tool, after the update-saga and the first BSOD. Running sfc /scannow returns with no problems found.

essenbe · 16 Sep 2014

I;m sorry but I will be with you later on.

HarriePateman · 16 Sep 2014

Useless User said:

essenbe said:

before you do that please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

I have not yet installed my application software, only the SF Diagnostic Tool, after the update-saga and the first BSOD. Running sfc /scannow returns with no problems found.

Sorry Steve is not here right now, i will continue with the help.

Give me time to read the thread and get my head together :)

Arc · 16 Sep 2014

Useless User said:

And another BSOD, the good old 0x124 is back : (

After some days of interval, I looked at your thread again; and this one drawn my attention ....

Useless User said:

Well, using IPDT I got: pass (prompting "PASSED"), fail (prompting "FAIL") and one BSOD 0x124...

Probably we are very close to a decision, as you also said ...

Useless User said:

The processor rarely fails in non-OC'ed PCs.

Rarely or not, the thing is that the processor fails that you know; which is a single enough reason for a stop 0x124 BSOD.

Stress test the CPU again, with another stresser.

Hardware - Stress Test With Prime95

Run Small FFTs, Large FFTs and Blend, all of them. Let us know if it can recreate the stop 0x124 BSOD.

Useless User · 16 Sep 2014

I ran prime95 before the Windows reinstalls, for an entire day, going well. I also ran it for only some minutes before it failed (without a BSOD).

While hanging on, I run it again right now. How long for each of the three tests?

Useless User · 16 Sep 2014

Indeed, it's a long multi-threaded thread... ; )

HarriePateman · 16 Sep 2014

#87 Posts :)

Its a lot to read :)

Useless User · 16 Sep 2014

Well, yes, I would have thought it to be easier to pinpoint what piece of software or kit is knackered. If one sums up the hours of all you helpers plus my own time spent on this, and puts a, let's say, Polish hourly rate onto it, one could probably have purchased a nice barrel of single malt or two Xeons...

HarriePateman · 16 Sep 2014

After this, il take the malt ; )