Sign in with
Sign up | Sign in
Your question

Random Blue screens might be GPU related

Last response: in Opinions and Experiences
Share
September 21, 2014 1:39:02 AM

Windows 7 Ultimate
Nvidia Gefore 680 (GV-N680OC-2GD)
ASUS Sabertooth 990FX rev 2.0
AMD FX 8350 Eight Core processor 4.01GHZ (stock speeds)
32GB Corsair Vengeance ram 1600MHZ



Hey guys, I'm not sure if this is the right place to put this, or even if you can help me. But you seem like a bunch of bright sparks, and right now I feel pretty ****ed. Essentially, I keep on getting random blue screens of death!

I've replaced my entire computer (everything!) except my graphics card and new solid state drive to try and fix this problem. Initially I thought it was my motherboard, then my ram. Now I know it can't be these, since I've replaced everything in my PC... Please, for the love of god can you shed some light on this issue. Most of the time it happens when I'm minimizing a game or doing something similar, but sometimes it happens entirely randomly. While sometimes my computer works flawlessly for a day or two, it can suddenly blue screen 2/3 times in a space of 5 minutes then proceed to work fine again. If my computer goes in to hibernation / sleep this seems to make it worse and cause a BSOD, but in no way are the BSOD's limited to this.

Honestly, i'm lost - a broken man with a broken computer.

Below is a summary of the crashes I've encountered - as you can see the program lists a range of problems. The random nature of which initially lead me to believe it was ram related. Now I'm of the belief it's something to do with the memory on the graphics card.

Here are some examples:

BSOD 1: This was probably caused by the following module: ntoskrnl.exe

BSOD 2: This was probably caused by the following module: cdd.dll

BSOD 3: This was probably caused by the following module: win32k.sys


Really, at this point I'd appreciate any assistance you can offer as I've really reached my wits end, and I've spent way over £800 replacing my entire computer to try and stem this problem. I'm not too annoyed at the expenditure since I needed to upgrade anyway, but it's still bloody annoying!

What do you think this error is?

Cheers in Advance
George Allen

Kill me now x

¬A summary of all crash reports

Spoiler
On Sat 20/09/2014 10:57:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-11434-01.dmp
This was probably caused by the following module: cdd.dll (0xFFFFF960006DDC51)
Bugcheck code: 0x50 (0xFFFFF900C35A27A0, 0x0, 0xFFFFF960006DDC51, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 20/09/2014 08:31:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-11356-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000124283, 0xFFFFF88007F69060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 20/09/2014 05:38:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-12136-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000134283, 0xFFFFF880083B3060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 16/09/2014 00:40:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091614-11918-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600034C69D)
Bugcheck code: 0x50 (0xFFFFF900C27A3030, 0x0, 0xFFFFF9600034C69D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 11/09/2014 19:14:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091114-11091-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001A4283, 0xFFFFF880088C2060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/09/2014 17:10:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091014-12261-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000114283, 0xFFFFF88007F9B060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/09/2014 01:50:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091014-11653-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000144283, 0xFFFFF88008CD5060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/09/2014 01:35:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091014-10935-01.dmp
This was probably caused by the following module: cdd.dll (0xFFFFF96000776D15)
Bugcheck code: 0x50 (0xFFFFF900C23B0770, 0x0, 0xFFFFF96000776D15, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/09/2014 00:36:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091014-12542-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003190075, 0xFFFFF88007A58EB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

More about : random blue screens gpu related

September 21, 2014 1:45:52 AM

Can you upload the dmp files somewhere / zipped and post the link?
m
0
l
September 21, 2014 1:48:53 AM

Sure thing, here's a zip of all the recent crashes I've experienced. It's a bundle of joy.

http://ge.tt/9ULHZby1/v/0?c
m
0
l
Related resources
September 21, 2014 1:54:12 AM

Nothing works, how do you download it. Clicked on the side the middle nada

Got it stupid adblock was blocking it !
m
0
l
September 21, 2014 1:59:14 AM

I was under the impression you just clicked "download" in the middle and it worked, but that may just be for my IP? Gah, sorry.

Here's an alternate link nonetheless, bear with it - it's pretty slow.

http://www.fast-files.com/getfile.aspx?file=79261
m
0
l
September 21, 2014 2:08:09 AM

There are suss / dodgy files on your system aut5hof4.SYS.

Google brings up nothing. I would also uninstall AMD overdrive, it's known for crashes

You may have malware or something. Here's another suss file axoapbbd.SYS,

Your video drivers maybe crashing nvlddmkm.sys. another suss file ah94evzr.SYS, a5hhqizx.SYS, directx maybe crashing dxgkrnl.sys

There's 1 suss file in every dmp file ae1h8osg.SYS, aopc9tqr.SYS, a5ltywh5.SYS, asxc8h6t.SYS, aco5r5ae.SYS, auregv09.SYS, auma03on.SYS, a2ck0i5z.SYS, a4c1l67d.SYS, a084ivou.SYS

There's 6 0x50 stop errors which may mean faulty ram









m
0
l
September 21, 2014 2:15:27 AM

Hmm interesting, thank you for looking in to the problem for me, this stuff goes way over my head - so it's really much appreciated... I removed AMD overdrive.

It's also worth noting that this problem has persisted over multiple HD's and installations of windows. However I have always backed up all my data on to a slave HD before formatting my computer - so if any malware was present it would have to have been transferred between installations. I've already scanned with malwarebytes - shall I install something else and give it another crack?
m
0
l
September 21, 2014 2:17:33 AM

I would if this boots run memtest and test the memory overnight. See if it picks up any errors

Is ccleaner installed? If it is go to tools/startup and uninstall save a txt file. Post both so we can see whats in startup and whats installed. I would disable system restore then turn it back on if you use it.

In case something is in the system restore folders. Do a full scan with the AV program whatever it is

Did you do a full scan with malwarebytes?

Just to be safe run tdsskiller to see it this has rootkits

http://media.kaspersky.com/utilities/VirusUtilities/EN/...

m
0
l
September 21, 2014 2:22:46 AM

I've already spoken to corsair and had all the memory sticks replaced. I ran a quick memtest on my old sticks and it didn't find any errors.

yeah I did a full scan with Malwarebytes - a few registry things, but nothing serious.
m
0
l
September 21, 2014 2:25:28 AM

How long did you run memtest for? Did you use the memtest from here. www.memtest.org Windows memory diag program wont do much
m
0
l
September 21, 2014 2:27:08 AM

It ran for around an hour, not long considering I have 32gb's of ram. But as mentioned, I've literally replaced all the sticks of ram on warranty anyway (thinking that was the problem).

The problem has persisted through 2 entirely different sets of ram sticks / Mobo.

Or is there another reason for running a more prolonged memtest?
m
0
l
September 21, 2014 2:28:21 AM

I think it would take longer, than 2 hrs to check 4 sticks
m
0
l
September 21, 2014 2:42:26 AM

It definitely would. But why would I need to check them, if they've already been replaced?

Running AVG virus scan as we speak.
m
0
l
September 21, 2014 4:10:04 AM

Just got another BSOD. It's none of the aforementioned. I think it's a faulty GPU.
m
0
l
!