BSOD Issues - Worse whilst gaming/streaming, can crash on desktop.

[ptERR]

Hi guys,
Let me start off by giving filling you in on the history of the system. The PC was built roughly back in August 2012, using mainly brand new components. I used my old power supply and GPU.

The computer has run fine since the initial build, but has recently started to BSOD, and I can't seem to find a solution.

My problems first arose roughly two months ago, my computer reported a failing hard drive, luckily it was still under warranty so was promptly replaced. Soon after the replacement my computer started to randomly blue screen, and continued to become more frequent, to the stage that my PC could barely render or run photoshop.

Suspecting a RAM issue I tried removing a RAM stick, the issued ceased for roughly a month, with no hiccups. Roll forward a month and the issues started up again, and here I am.

Steps taken since BSOD issues started:

* Installed new RAM
* Installed new power supply
* Tried installing up to date GPU drivers, BIOS & chipset drivers.
* Performed a clean reformat.
* Tried running on separate hard drives.

I have run a prime95 test for a thirty minute duration, with no issues. You can find the temps below:

Image - TinyPic - Free Image Hosting, Photo Sharing & Video Hosting

I did however receive a few errors, not quite sure what they mean.

Image - TinyPic - Free Image Hosting, Photo Sharing & Video Hosting

I ran a furmark test on my GPU for twenty minutes without any screen tearing, it settled on 94 degrees with the fans running at 92%.

My computer specifications:

* RAM: 16GB DDR3 (brand new)
* PSU: 800w Corsair (brand new)
* MB: Z68x-UD5-B3 (Less than a year old)
* GPU: Nvidea GTX480 (Two-three years old)
* CPU: i7-2700k CPU @ 3.5gz (Less than a year old)

Nothing has ever been overclocked.

Mini dumps before reformat:
Download pccrashes.zip from Sendspace.com - send big files the easy way

DXDiag:
Zippyshare.com -

Another thing to note, alongside blue screening a lot of my programs keep failing to respond, including, but not limited to; firefox, teamspeak3, Firefall Beta and flash.

Hoping you guys can help me out, really not quite sure what to do next. Pretty sure it is a hard ware issue after the reformat, but not quite sure what to do next.

What I have done since creating this thread:

* Updated Realtek network driver (Realtek RTL8168D/8111D)
* Updated windows to SP1

Thanks,
Peter

 

[x BlueRobot]

Welcome to the forums ptERR and thanks for the information you have provided, let's begin with the analysis:

[COLOR="Red"]BugCheck D1[/COLOR], {[COLOR="Blue"]e0000000[/COLOR], 2, 1, fffff88002c54a5b}

Probably caused by : [COLOR="Red"]hardware[/COLOR] ( afd!AfdBFillPendingIrps+1b )

Stop 0xD1 is usually caused by drivers referencing invalid memory addresses and causing interrupts at IRQL levels which are too high. However, from the excellent information you have already provided, and the information from the Minidump, the first parameter tells us the memory address being referenced, and it appears to be within one of the CPU caches.

TRAP_FRAME:  fffff880043ef040 -- ([COLOR="SeaGreen"].trap 0xfffff880043ef040[/COLOR])
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
[COLOR="Blue"]rax=00000000e0000000[/COLOR] rbx=0000000000000000 rcx=fffffa800fdc8530
rdx=fffffa800e59e520 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002c54a5b rsp=fffff880043ef1d8 rbp=00000000000005a4
 r8=0000000000000000  r9=000000000000003e r10=fffffa800d5cef40
r11=000000000000afd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
afd!AfdBFillPendingIrps+0x1b:
fffff880`02c54a5b 0000            add     byte ptr [COLOR="red"][rax][/COLOR],al ds:00000000`e0000000=??

The CPU register being read from, is the memory address which was referenced, therefore I believe it is most likely a CPU issue.

The driver referencing the address seems to be your Realtek network driver (Realtek RTL8168D/8111D), I suggest you update this driver from here: Realtek

6: kd> [COLOR="SeaGreen"]lmvm Rt64win7[/COLOR]
start             end                 module name
fffff880`05335000 fffff880`053d5000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="Red"]Tue Sep 27 15:50:33 2011[/COLOR] (4E81E2B9)
    CheckSum:         0009FB77
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Install Service Pack 1:

• Learn how to install Windows 7 Service Pack 1 (SP1)

Service Pack 1 has provided many security and stability updates for Windows 7, which would be highly beneficial for your system.

 

[ptERR]

Hi BlueRobot,
I have just reinstalled the Realtek driver and am currently in the process of updating my windows. My windows was fully updated prior to my reformat, so I do not believe that this is an issue. Will get back to you as soon as I experience a crash or instability.

Thanks for the feedback so far,
Peter

 

[x BlueRobot]

Thanks for the update Peter

 

[ptERR]

Since we last spoke I have updated the Realtek Driver and updated windows to SP1.

Today I experienced a blue screen alongside system instability.

My crash analyzer provided me with the following information:

[FONT=Segoe UI, Arial]On Sun 16/06/2013 15:37:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061613-20592-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF88002301350, 0xFFFFF88002301350, 0x36FFF88002301350)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

The bluescreen occurred whilst playing Guild Wars 2, the first crash in this program. Alongside this crash I have also had the following issues occur whilst using my computer TODAY:

* Sound both mic and headphone stopped working, was a jarred sound followed by silence. Sound worked again after reattaching the headset.
* Firefall has crashed twice whilst playing.
* GW2 has crashed once whilst playing.

The temperature of my hardware whilst using these applications appeared normal. The CPU was around 70 degrees with my GPU hovering around 80 degrees. Idle temperatures outside of these games have been 40-60 degrees.

I have uploaded the minidump file here: Download 061613-20592-01.dmp from Sendspace.com - send big files the easy way

When my firefall crashed I tried to re-launch, it came up with the following error: http://i43.tinypic.com/ossrkh.png - I tried 10 seconds later and it launched.

Thanks,
Peter
[/FONT]

 

[x BlueRobot]

The TinyPic link is broken for some reason :huh: You can upload files and folders to this thread using this tutorial - http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

70*C to 80*C is quite hot, have you checked the fans and heatsinks for accumulation of dust? There may be a possible overheating issue, which may explain the warnings used by Prime95 earlier in this thread. The CPU could be at fault here.

[COLOR="Red"]BugCheck 19[/COLOR], {[COLOR="Blue"]3[/COLOR], fffff88002301350, fffff88002301350, [COLOR="SeaGreen"]36[/COLOR]fff88002301350}

Probably caused by : [COLOR="Red"]Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+a53 )

Usual causes:  Device driver

A corrupted pool header indicates there are issues with the Windows memory allocation, from the first paratmer we can that the pool freelist has become corrupt, this is a data structure used by the operating system to allocate a continuous chunk of memory for a request.

The usual suspects for this BSOD are device drivers, RAM and the hard-drive.

I couldn't see any issues within the stack which were driver-related, I would suggest following this step to test for any possibility of buggy drivers:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

You have a new hard-drive and new RAM, although, new hardware doesn't seem it is necessarily working, I feel it is not likely to be the issue at the moment.

I noticed a random 36 within the blink freelist address, I'm not sure if it could potentially be flipped bit, which is often related to a failing CPU. The address in parameter 3 should be same as the address in parameter 2.

 

[ptERR]

Attached the file and am rebooting now to enable driver verifier.

Update: After enabling driver verifier I rebooted my PC and failed to boot, crashing on windows start up repeatedly. I had to roll back to a previous restore point to re-gain access to my desktop.

The BSOD error (unfortunately I can't remember it specifically) began with driver and refereed to memory. I cannot see any new mini dump files, but I re-ran the diagnostic tool to see if it can pick anything up.

You can find the file attached.

 

[x BlueRobot]

You have been lucky and the Minidump was saved

[COLOR="Red"]BugCheck D6[/COLOR], {[COLOR="Blue"]fffff98001563000[/COLOR], [COLOR="SeaGreen"]0[/COLOR], fffff88003c5b192, 0}

*** WARNING: Unable to verify timestamp for ATITool64.sys
*** ERROR: Module load completed but symbols could not be loaded for ATITool64.sys

Could not read faulting driver name
Probably caused by : [COLOR="red"]ATITool64.sys [/COLOR]( ATITool64+6192 )

Usual causes:  Device driver

Okay, this bugcheck is nice and simple, the specified driver has attempted to read beyond it's pool operation, we can see from the first parameter that the driver attempted to read from the memory address stored in the rax CPU register, and from the second parameter we can see it was a read operation.

Remove:

3: kd>[COLOR="SeaGreen"] lmvm ATITool64[/COLOR]
start             end                 module name
fffff880`03c55000 fffff880`03c63000   ATITool64 T (no symbols)           
    Loaded symbol image file: ATITool64.sys
    Image path: \SystemRoot\system32\DRIVERS\ATITool64.sys
    Image name: ATITool64.sys
    Timestamp:        [COLOR="red"]Wed Aug 08 17:42:26 2007[/COLOR] (46B9F272)
    CheckSum:         0001540C
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The driver which seems to be causing the problem, is a overclocking utility for ATI/nVidia cards and is only compatible with Windows 2000/Windows XP and Windows Server 2003. Please remove the software completely using Revo Uninstaller Pro - Uninstall Software, Remove Programs easily, Forced Uninstall, Leftovers Uninstaller

TRAP_FRAME:  fffff8800336f9f0 -- ([COLOR="SeaGreen"].trap 0xfffff8800336f9f0[/COLOR])
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
[COLOR="Blue"]rax=fffff98001563000[/COLOR] rbx=0000000000000000 rcx=fffff88003c5b0fb
rdx=0000000000000046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003c5b192 rsp=fffff8800336fb80 rbp=0000000000000010
 r8=0000000000000000  r9=fffff88003370110 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ATITool64+0x6192:
fffff880`03c5b192 66833800        cmp     word ptr [COLOR="Red"][rax][/COLOR],0 ds:fffff980`01563000=????

I suggest you stop overclocking your CPU and any other hardware during this debugging session, please reset the BIOS back to factory defaults - How To Clear CMOS - 3 Easy Ways To Clear Your Motherboard CMOS Memory

3: kd> [COLOR="SeaGreen"]!sysinfo cpuspeed[/COLOR]
CPUID:        "Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz"
MaxSpeed:     [COLOR="Red"]3500[/COLOR]
CurrentSpeed: [COLOR="red"]3510[/COLOR]

 

[ptERR]

Uninstalled the utility, I believe I used it to check my graphics card ram. I haven't overclocked any components, never changed any of my components throughout the time I have owned them, so weird, very weird.

I un-installed the software via the program you recommended, but I think it may still have been in the driver verifier software. After the uninstall I rebooted, then ran the verifier.

I went into the bios and set my bios to "Load fail-safe defaults".

My computer blue screened, I think it was a different error than before but I cannot be sure. I let it blue screen a few times so hopefully there will be a crash file for you to find.

Also included an image of programs I currently have installed that are recognized by your recommended installer.

Thanks again,
Peter

 

[x BlueRobot]

[COLOR="red"]BugCheck D6[/COLOR], {fffff9800140b000, 0, fffff88004017192, 0}

*** WARNING: Unable to verify timestamp for ATITool64.sys
*** ERROR: Module load completed but symbols could not be loaded for ATITool64.sys

Could not read faulting driver name
Probably caused by : [COLOR="Red"]ATITool64.sys [/COLOR]( ATITool64+6192 )

It seems to be the exact same BSOD :huh: and it's the most recent one:

7: kd> [COLOR="SeaGreen"].time[/COLOR]
Debug session time: [COLOR="Red"]Sun Jun 16 22:16:36.454 2013[/COLOR] (UTC + 1:00)
System Uptime: 0 days 0:00:10.297

Disable Driver Verifier, and then run Revo again to make sure the software and it's drivers are completely removed.

 

[ptERR]

Removed the driver manually from system32 as it wasn't appearing in Revo after uninstalling it, running Driver Verifier now. Will get back to you in roughly twenty four hours, what file do I need to upload once it is complete?

Oh, and if I crash will it continue to run?

In relation to my CPU being overclocked, do the I7's not turbo boost as standard?

Thanks for everything so far,
Peter

Edit:
Since running driver verifier I have received another system crash, whilst playing Guild Wars 2. You can find the crash report below.

 

[x BlueRobot]

Driver Verifier will create a BSOD if it finds a violation against the settings it's testing, such as pool allocations etc.

I think TurboBoost is most likely to be enabled by default, the i5's have TurboBoost too. I would disable TurboBoost for now.

Here's the latest:

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="seagreen"]c0000005[/COLOR], fffff80002e4fbe6, fffff88008781f60, 0}

Probably caused by : ntkrnlmp.exe ( nt!PoDestroyReasonContext+6 )

Usual causes:  System service, Device driver, graphics driver, memory

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`048cb000 fffff880`05373000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Sat Feb 09 23:13:08 2013[/COLOR] (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your nVidia graphics card driver seems to be a possible cause, please update to the latest WHQL version, by following these steps:

Version: 320.18
Release Date for Desktops and Notebooks : May 23rd 2013
In Device Manager: 9.18.13.2018

• http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

 

[ptERR]

Hi BlueRobot,
I Re-installed the drivers as you requested, but the problems still ensued. I left the computer running over the course of night and throughout the day with driver verifier and it did not crash.

I opened up Firefall (game) and the game crashed twice in the space of 10 minutes. On the third attempt to load it blue screened, I will post the mini dump below.

I keep getting applications crashing, will post what I think is a report for that below as well.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {c0000005, fffff80002e4fbe6, fffff88008781f60, 0}

Probably caused by : ntkrnlmp.exe ( nt!PoDestroyReasonContext+6 )

Usual causes:  System service, Device driver, graphics driver, memory

Okay, so I looked at the log file you uploaded, and managed to search the Vendor ID and Device ID codes to match it to your MSI GTX 480 graphics card, the dumps also support this information:

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`048cb000 fffff880`05373000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="red"]Sat Feb 09 23:13:08 2013[/COLOR] (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The dump shows the graphics card drivers are outdated, the dump may been before the update, or sometimes the dumps can have the old timestamps still attached for some reason, check within Device Manager that the version of the driver matches the latest driver version.

It should be listed with - 9.18.13.2018

If it's the latest version, then I suspect a hardware related error, it could be overheating from the temperatures you posted earlier or a problem with the actual graphics card.

Run http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html to test for any issues, if it BSODs upon the test then it most likely a hardware fault.

 

[ptERR]

Hi BlueRobot thanks for getting back to me again.

I ran the furmark test as requested and found no errors, temperature averaged out at around 92 degrees with fans running around 80%. I have attached a screenshot of the test.

I checked the driver version, and is listed as 9.18.13.2018, matching the one you listed above. I have also attached a screenshot of this driver version.

Any ideas?

 

[x BlueRobot]

How long did you manage to run the test for? I would remove the side panels, and attempt to run the test again, it will need to run for least a hour.

It seems to be more of a hardware issue, do you have a spare graphics card or a onboard graphics card you could switch to to save running the test?

Have you tried placing the card in a different PCI/PCIe slot? I would check to see if any dust has blocked the slot, even simple things like that, can cause problems unfortunately.

 

[ptERR]

I ran the test for ten minutes, I will attempt to run it for one hour. I removed the side panels a few days ago suspecting a heating issue, will try a different PCI slot after the furmark.

Unfortunately this motherboard does not support on-board graphics, despite there being a GPU being built into the CPU. Will get back to you in an hour.

Thanks again,
Peter

 

[ptERR]

Ran the test for over an hour with no artifacting and no blue screens.

Following this I switched my graphics card into a different PCI slot, on boot up it appeared that I had lost my drivers, and blue screened roughly two minutes later. I have attached the crash log.

I just tried to open Firefall and was greeted with this message again, the program worked around 10 seconds later. Attached pictures below.

Edit: Once rebooted the drivers were working.

Edit2: I booted up today and launched Firefall, the computer blue screened within two minutes, there didn't appear to be an error code on the blue screen. I have attached the dump file.

 

[ptERR]

I minimized firefall, and upon maximizing the game crashed to a blue screen, I have attached the crash report below.

So do we think it is a GPU or CPU issue? To replace either part is going to be a pretty expensive ordeal, so want to make sure before I take the plunge. Could it even be a motherboard issue?

 

[x BlueRobot]

I don't think it's a motherboard issue if crashed in both PCI/PCIe slots. It managed to run successfully with issues for an hour.

Remove the GPU completely, and then reboot the computer, see if it manages to detect the graphics built into your CPU, if it does, then wait and see if it crashes again, see will definitely determine if the card is bad.

Anyhow, here's the most worthwhile dump:

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff88006ff8269, fffff8800679cfa0, 0}

Probably caused by : [COLOR="Red"]danew.sys [/COLOR]( danew+1269 )

4: kd> [COLOR="SeaGreen"]lmvm danew[/COLOR]
start             end                 module name
fffff880`06ff7000 fffff880`06ff9f00   danew    T (no symbols)           
    Loaded symbol image file: danew.sys
    Image path: \SystemRoot\system32\drivers\danew.sys
    Image name: danew.sys
    Timestamp:        [COLOR="red"]Tue Mar 23 08:37:33 2010[/COLOR] (4BA87DCD)
    CheckSum:         0000D71C
    ImageSize:        00002F00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your New DeathAdder Mouse driver seems to be a possible cause and creating problems, please update the driver from here - Razer Support

Could you enter your BIOS, and post the values for 3.3V, 5V a 12V?