Ok np I won't bump anymore. I'm definitely considering getting a new CPU. I got a new BSOD today, still a 0x124, but this time caused by driver dump_ataport.sys. I don't know if it matters or not, but here's the dump file.
That's what bluecsreenview told me
Last edited by Framack4; 20 Dec 2014 at 23:10. Reason: Bluescreenview
This BSOD I just received, according to Bluescreenview, is caused by dxgmms1.sys... I've attached the dump file... I don't understand how a faulty CPU could cause this
Probably caused by doesn't mean definately caused by.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa8808e68500, 0, fffff88011fa0a21, 5} Could not read faulting driver name Probably caused by : dxgmms1.sys ( dxgmms1!VidSchSubmitPagingCommand+29 ) Followup: MachineOwner ---------
0x50's are typically memory-related problems. Since a CPU handles some memory addressing, a faulty CPU is still feasible.
So instead of buying a new CPU straight off the bat, I decided to open up the case and take a look. What I found was that the heatsink was very clogged up with dust and so I cleaned that and gave the fans a clean too. I ran Intel burn test and it passed on standard, high and very high settings, plus the temperature of the CPU only rose to 46.0c, as opposed to 56.0c. So for now I think the problem is fixed, and I'll mark this as solved if I don't get another blue screen in the next week or so. Thanks for all your invaluable help!
Good news. Thats why the initial suggestion was to replace the thermal paste - you would have seen the heatsink needed cleaning then.
Great result
Quote