BSOD while playing DOTA 2, ntoskrnl.exe

MetaVu · 26 Feb 2013

I've been crashing for a couple of months now, and it's usually been while playing Dota 2. Around the time the crashes started, I overclocked my cpu, but once I realized it was unstable I lowered the clock and the voltages. The problem doesn't seem to be heat, as I completely cleaned out my case and parts just a few days ago with a can of compressed air. What I'm going to do next is go back to default voltages for my CPU/NB, and see if that stops the crashing. Uploaded are all of my logs.

System specs for convenience:
Computer type

PC/Desktop Computer Manufacturer/Model Number

Custom build OS

Windows 7 Home Premium x64 CPU

amd phenom ii x4 955 Motherboard

gigabyte ga-870a-usb3 Memory

Kingston HyperX 4GB single stick Graphics Card(s)

Geforce 550Ti Sound Card

N/A Monitor(s) Displays

N/A Screen Resolution

N/A Hard Drives

Seagate 500gb PSU

600 watt Case

N/A Cooling

N/A Keyboard

N/A Mouse

N/A Internet Speed

N/A Antivirus

NOD32 Browser

Firefox Other Info

N/A

Dsprague · 26 Feb 2013

If stopping over clocking does not seem to help with the problem please do the following:

Update your Bios updates can be found on the motherboard manufacturers website.

Run memtest86+ for at least 8 passes: RAM - Test with Memtest86+

Run the following commands:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

then from the same command prompt issue the following to check for disk corruption:

Code:

chkdsk /r /f

and lastly please enable driver verifier and allow it ot crash your computer then post the new dump files her the way you did before:

Driver Verifier

If you can not boot normally after enabling verifier please boot into safe mode and disable verifier from safe mode.

x BlueRobot · 26 Feb 2013

Code:

BugCheck 50, {ffffffffffffffc9, 1, fffff88000e27a7c, 0}

Could not read faulting driver name
Probably caused by : Wdf01000.sys ( Wdf01000!FxMemoryObject::Release+0)

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Memory:

RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Update BIOS (if possible):

Code:

Award Software International, Inc. F4, 3/9/2011

Remove (Motherboard bloatware):

Code:

Start Menu\Programs\GIGABYTE
Start Menu\Programs\GIGABYTE\ET6