Multiple BSODs

tom982

tom982

Emeritus
Joined
May 31, 2012
Posts
4,351
Location
New York
Hi guys,

I was wondering whether someone would be able to take a look at these dumps for me. I'm still learning about debugging and I wouldn't trust my knowledge at this point :)

I've just built a new PC and it's developed a nasty habit of BSODing. I'm fairly sure it's to do with the graphics card because it always BSODs when I try to run something that is GPU accelerated.

Here's my specs if it matters:

CPU: i7 3770K @ 4.7GHz
Motherboard: ASUS P8Z77-V PRO
Graphics: Gigabyte Radeon HD 7850 (2GB)
RAM: Corsair Vengeance 2x4GB LP (White)
Hard Drive: SeaGate Baraccuda 2TB 7200rpm
Cooling: Corsair H100 Water Cooler
OS: Windows 7 Ultimate x64 SP1
Monitor: 23" LG LCD/LED IPS Monitor (1920*1080)
Power: Corsair TX650W V2 (80+ Bronze)
Case: NZXT Phantom 410

Might be the infamous AMD drivers, but I'm running the latest version of them, so there's not a lot I can do on that front.

I've overclocked to 4.7GHz but I'm just about to go back to the stock CPU speeds and voltages to make sure the problem doesn't lie there, but I thought I might as well post these first.

Another issue I have occasionally, I'm not sure if it's related but I might as well post it anyway, every now and then (with obvious pattern) my screen will just go a grey/blue colour with lines across it. Again, I don't know if it's related, but it can't hurt to post it :)

Thanks in advance for any help!

Tom

Edit: Oops, I didn't use John's BSOD collection tool - you can really tell I'm new to this :lol: If anyone wants that information then I can upload it.

2nd Edit: I also should've noted that the first half of those dumps were from overclocking experiments (mainly, lack of voltage), so I don't think they'll show anything that's of use.
 

Attachments

Last edited:
Hello Tom982,

We're seeing various different bugchecks here, mostly PAGE_FAULT_IN_NONPAGED_AREA and IRQL_NOT_LESS_OR_EQUAL. There's mention of a D1 DRIVER_IRQL, but I am going to say your issue is likely hardware given the amount of hardware / memory corruption mentions in all of these dump files. The latest however is a x124 hardware BSOD, and if I am reading !cpuinfo correctly, it was at stock clocks (3500MHz). It could be software, and it may be... I don't trust those Asus utilities, but we'll find out soon.

First thing I am going to recommend doing is completely clearing the CMOS to ensure that everything is truly back to to stock clocks and values. After that, adjust your memory timings and such as advertised if need be. I'm then going to recommend running Memtest to be sure your RAM is not the culprit here:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I recommend no less than 6-7 passes. This will take multiple hours, so I recommend running before work or sleep.

If Memtest comes up clean, since you mentioned the odd gray lines and such that sometimes happen, run Furmark for 10-15 minutes and see how your GPU reacts to the load. Make sure there are no artifacts, obvious BSODs / freezes, etc. Also, keep a close watch on the temps. Furmark is a stress testing client moreso than its advertised benchmarking capabilities, so things get really hot. If you see the video card get higher than ~90c, hit ESC to end the test.

Regards,

Patrick
 
Hi Patrick,

Thanks for your reply!

Perhaps that was one of the dumps before I started overclocking then.

Okay, I've cleared my CMOS and I'm back to default speeds and voltages. I never changed my memory timings, they've always been 9-9-9-24.

Memtest is running as we speak, it's on 46% of the first pass. I'll let you know the results as soon as it gets to 6/7 passes.

Furmark is next on the list :)

Thank you once again for your help!

Tom
 
Hi Patrick,

Memtest completed over 7 passes and found no errors. I've just ran Furmark for 15 minutes and I had no problems there either. My graphics card hit 72C max, so the temperature wasn't a problem.

I'll take a photo of my screen next time it occurs to give you an idea of what's happening :)

Thanks again,

Tom
 
Great :)

If the system is at stock settings now, you might not BSOD if the issue was unstable OC(s), of course. I was under the impression you were at stock the entire time, but keep me updated whether or not this happens regardless!

Regards,

Patrick
 
I'll leave it at stock settings for a few more days, just to make sure any creases are ironed out before I have another fiddle with the BIOS.

Thank you, once again for all of your help so far Patrick; I really appreciate it. I'll be sure to keep you updated :)

Tom
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top