Well to be honest, from the crash reports, there are several things it could be. Have you installed any drivers/software lately?
Well to be honest, from the crash reports, there are several things it could be. Have you installed any drivers/software lately?
Jon
The guys that created WhoCrashed, Resplendence offer this advice for troubleshooting, updating Windows, drivers and then checking hardware and temperatures are amongst the earliest of the stages you need to get through in order to identify the cause and fix it. The suggestion for either trying a CD or USB key to check your RAM is to help eliminate or identify hardware faults, if your hardware is faulty there are no software fixes that will correct it and you could end up making things worse trying to fix symptoms without fixing the cause.
If you are not comfortable with trying a fix suggested tell us why we might be able to help you overcome this by giving you detailed explanations on how to tackle any issues you encounter, such as how to boot from a USB drive etc...
The issue you could get with running a memory test from in Windows is that if the program crashes and leads to a BSOD then you might assume it's a RAM issues when it could be a Windows issue or a Windows issue might lead to the program reporting a fasle positive, running it from a CD or USB key eliminates Windows and so it is purely a test to check for integrity of the RAM.
Thank you. I tried to boot from USB by changing the bios and its not having it, I set the boot order as USB 1 and it loaded straight into windows. I then disabled everything other than the USB and it just loads in to the bios without starting windows. Not having it at all.
Anyone?
Why wont the motherboard boot off the USB?
Did you make your usb key bootable?
Jon
Ended up grabbing a blank CD from a friend. I did two passes on memtest which took over an hour, there were no errors at all. Hopefully this means no hardware issues because I'd rather just sort it with what I have here.
What is the next step to identifying what it is?
Check you GPU for overheating by running Furmark or stress test your CPU. Stress testing one component at a time usually helps narrow down the possibilities. Divide and conquer being the philosophy there.
For Windows issues you could try AdvancedSystemCare 5 which is a great suite of programs that will clear out your registry, defrag your HDD, resolve many issues and optimise the PC etc...
I don't see how it could be stressing the GPU or CPU, it crashes when I am not even playing games. I can be watching a youtube video or loading the steam client, the temps are all low and POP....blue screen. Another one....
On Fri 7/13/2012 10:00:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071312-10046-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF800030951C0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008842028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown WHEA_UNCORRECTABLE_ERROR
Ok. So it's not RAM, you think that both your CPU and GPU are fine, a scientific approach might test that assumption but I'll go with a wet finger in the air approach and say you're right.
Temperatures recorded suggest overheating is not an issue.
Have you disabled the throttling features on your motherboard, as in turned off the Intel Speedstep or AMD Cool'n'Quiet as these could be causing the crashes.
Have you run CHKDSK to ensure that you have no disk errors?
Is all of your Anti virus or Internet Security up to date?
I think the OC settings. It needs a kindly re-fettle.
Society's to blame,
Or possibly Atari.
Indeed, I agree with Phage.
I had a similar issues on a Q6600 which I had overclocked myself, it runned flawlessly for a couple of years then I had the hal.dll stop screen. After blaming everything and thinking to myself that it couldn't be my rock solid 2 year old overclock, it turned out that upping the voltage by just .04 stabilised it and no new blue screens after that.
My conclusion was that overtime components come stressed and worn and just need that little extra to remain stable.
Jon
Alrite well if needed i'll run the stress tests. I used furmark...set it on native resolution and left if for 20 minutes doing an x-treme burn in. The GPU temp maxed at about 76c with a 99% workload. How long do I run this for? Also, anyone recommend something to stress test my CPU?
I used to frun 3dmark11 for benchmarking and it always ran ok it that.
sinbeast,
To test the system I recommend running a Prime95 torture test selecting small FFT's for several hours and also Intel Burn in test for up to 20 passes. However please keep a close eye on CPU temperatures when running Intel Burn in test, I would also ensure any dust is cleared out of the system before stressing the CPU as Intel burn in can produce a lot of heat.
Please ensure you reply to our emails as that way we can get back to you more quickly, the blue screen error messages point towards CPU voltage so if the CPU is falling over during stress we may need to re-tweak some settings with you.
Kind regards,
Sorry ill reply purely by email now.
There are currently 1 users browsing this thread. (0 members and 1 guests)