Daily BSOD 0x124 (few times a day)

[x BlueRobot]

The voltage is fine then, and that might be a good idea, you've basically tested everything you can

 

[Djsajmy]

One day passed with my system open and power from another PSU (up time is 1day 9h).
Most of the time the system was in idle till now no BSODs! Will run it few more days from this PSU then if no BSOD occur switch back to my primary PSU and see if the BSODs come back!

 

[x BlueRobot]

Thanks for the update

 

[Djsajmy]

Day 3 on a spare PSU! Still running without problems.
New PSU on the way!

Can someone explain to me why the old (BSOD making) PSU did that ? Why would the system be unstable in idle but not on load ?

 

[x BlueRobot]

I was just reading a little paragraph about your PSU - LC Power Arkangel 850W

It may be due to how the power saving mechanism works when attempting to reduce power consumption.

 

[Djsajmy]

Problem not solved! Got the same BSOD (100% identical) when I was away from my computer.

The only thing I can do now, is to let my friend test the Q6600 in his system for few days. And then see what I have to replace (motherboard or CPU).

 

[x BlueRobot]

Thanks for the update, please let me which part needs to be replaced

Stop 0x124's are the most difficult to debug, because they don't provide much information at all, so you end up having to swap parts out etc.

 

[Djsajmy]

Its 50/50 for CPU/Motherboard. But because all dumps are identical and on the same cpu and bank (0, 0) i would say its the CPU.

 

[x BlueRobot]

What's the CPU been like in your friend's computer?

 

[Djsajmy]

He was not at home! He will be tomorrow (will report back in 3-4days)

 

[x BlueRobot]

Okay

 

[Djsajmy]

The BSOD is back after 1 week on new MB (replaced the P5QL-E). It's still 100% identical! 0x124 with: BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)

Now the only thing left is the CPU itself! They are still not cheap Q6600 is around 50-60€

 

[x BlueRobot]

How was the CPU in the other computer?

 

[Djsajmy]

Fine for 3-4 day, but nobody was using the PC it was just running in idle. During that time no BSOD occurred. Now one week on new/used MB it's still there! There is nothing else that could be wrong, HDD is good, GPU good, RAM good (tested in another system). The last thing was overheating but as it happens on normal usage (idle, browsing...) and not on load gaming, movies... it's not the problem. Or vcore to low but it run fine on the same 1,28v for 4 years!

 

[x BlueRobot]

I would definitely consider getting that overheating issue sorted then.

 

[Djsajmy]

It's not overheating but it was the last thing that could couse the bsod.
Can't do more here. Only thing to do is to replace the CPU and see how it goes...

 

[x BlueRobot]

Alright, please post an update when it's done

 

[Djsajmy]

Nothing new! Still the same BSOD

- Replaced MB
- Replaced RAM
- Replaced CPU
- Replaced PSU
- HDD passes all tests (long, short... in seatools DOS application).

Now there is nothing left to do Maybe it's the GPU (will send it in warranty). Or maybe GPU drivers, but my friend has the same GPU, OS and drivers and no problems at all.

 

[x BlueRobot]

It's got warranty, so your not losing any money

 

[Djsajmy]

Found this: https://forums.geforce.com/default/...ies/nvidia-driver-320-49-whql-freezing-my-pc/ and this: https://forums.geforce.com/default/...00-series/400-500-series-owners-please-read-/

Don't know how I didn't see that before My drivers where updated right befor the BSOD appeared on Win 7 and after a fresh Win 8 installed (320.49). Now I am back on 314.22 that was installed previously. Hope this was the problem