BSOD-0x0000007F (and more)-usually during gaming

mack2331 · 02 Apr 2012

Alright. So I built a computer about 2 weeks ago. Since then I've gotten random restarts/freezes/BSOD.

At first I wasn't getting any minidumps. Figured that out (had to change some settings so it'd write them)

Then I figured out my MOBO had my RAM at 11-11-11-28 when it was supposed to be 9-9-9-24. Since then, no random restarts but now freezes (with sound looping) or BSOD (never writting a mini dump except this one time)

So. Symptoms: It usually happens during gaming. Either Minecraft or Realm of a Mad God. It will either BSOD out on me or Just freeze with (if sound is playing) sound looping. It's completely random. Sometimes it won't do it for hours. The last time (the time it actually gave me a minidump log) I had the computer on maybe 10 minutes and it BSOD while playing Realm of a Mad God.

System Specs:

OS: Win7 Home-64Bit
Processor: AMD Phenom II x4 955
MOBO: GIGABYTE GA-990FXA-UD3 AM3+ AMD 990FX Newegg.com - GIGABYTE GA-990FXA-UD3 AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard
RAM: G.Skill RipJaw 16GB (4x4gb) Newegg.com - G.SKILL Ripjaws X Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9Q-16GBXL
HDD: Segate 500GB Newegg.com - Seagate Barracuda ST500DM002 500GB 7200 RPM 16MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive -Bare Drive
PSU: Broadway 680W Newegg.com - Broadway Com Corp OKIA-BLACK-680 680W ATX 12V V2.2 SLI Ready CrossFire Ready Active PFC Power Supply

So I'm not sure what's going on. Here is a link to the dmp file http://dl.dropbox.com/u/55618872/040212-16614-01.dmp

here is a link of the .zip file:
http://dl.dropbox.com/u/55618872/Win...D_jcgriff2.zip

This was the BSOD report I got: 0x0000007F (0x0000000000000008, 0x0000000050031, 0x00000000000006f8, 0xfffff80000CD1D00)

I'm thinking maybe an audio issue? as I believe the 50031 or 6f8 was supposedly an audio thing (according to a website)

Also "WhoCrashed?" Gave me this:

On Mon 4/2/2012 11:43:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-16614-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80000CD1D00)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

--The reason I made "Intel" Bold as...well I'm running an AMD processor. Kinda strange to get an Intel error (unless that's just the default of whocrashed)

Also: I've ran MemTest86 (2 passes) and have done a checkdisk. Neither came up with any errors

As far as I know, I'm not overclocking unless the MOBO read that wrong as well (like it did the RAM).

Anyhow. Any help would be appreciated. Thank you ahead of time :)

mack2331 · 02 Apr 2012

So, I poked the machine some more. I ran Driver Verifier. It didn't like it. It went about 30 minutes until the first BSOD. Then it kept freezing/restarting. Had to disable in safe mode:

Here is the NT6-Report w/ mini-dumps (found below). This is #2 of the NT6-Report. The other can be found in the first post.

Here is what "WhoCrashed" had to say:

On Tue 4/3/2012 3:57:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-23306-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xC4 (0xE3, 0xFFFFFA800F0D1531, 0x73BF278, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver has made a call to a kernel-mode ZwXxx routine with a user-mode address as a parameter. 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 which cannot be identified at this time.

On Tue 4/3/2012 3:55:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-18595-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C9CC35)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.

Hope this helps :)

usasma · 03 Apr 2012

From your description (only) I suspect one of 2 things:
- overheating
- bad connections

To check for overheating, point a house fan into the case on high and see if that makes it longer until the system BSOD's

Bad connections plagued me for years when building systems. Unplug everything and carefully replug it in - making sure that you double check each connection.

Also, please check the Usual Causes section at this link for your BSOD: BSOD Index

Here's what I got from the reports:
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download and install a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC). This is a separate issue and isn't required for the AMD OverDrive removal.

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

I wonder about ESET Smart Security as I've seen it in plenty of systems that have BSOD's. It also can be involved in memory access errors because of it's firewall component. Others that I know swear by it. You can uninstall it to see if that has any effect (but be sure to use another, free antivirus so you don't get infected while testing).

Beyond that I tend to suspect a hardware problem. Please try the free hardware diagnostics here (start with the memory test): Hardware Diags

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
PxHlpa64.sys    Tue Jun 23 19:16:35 2009 (4A416253)
epfw.sys        Tue Jun 28 03:30:10 2011 (4E098302)
ehdrv.sys       Tue Jun 28 03:34:38 2011 (4E09840E)
epfwwfp.sys     Tue Jun 28 03:30:08 2011 (4E098300)
EpfwLWF.sys     Mon Jul 11 12:19:38 2011 (4E1B229A)
EtronXHCI.sys   Mon Jul 25 17:30:56 2011 (4E2DE090)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
Rt64win7.sys    Thu Jan 13 06:57:19 2011 (4D2EE89F)
hamachi.sys     Thu Feb 19 05:36:41 2009 (499D3639)
EtronHub3.sys   Mon Jul 25 17:30:59 2011 (4E2DE093)
eamonm.sys      Tue Aug 02 05:33:29 2011 (4E37C469)
RTKVHD64.sys    Fri Aug 12 01:28:04 2011 (4E44B9E4)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
AODDriver2.sys  Mon Jan 16 02:42:46 2012 (4F13D4F6)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\040212-23306-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  2 23:57:05.185 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:23.684
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_e3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ekrn.exe
FAILURE_BUCKET_ID:  X64_0xc4_e3_nt!VerifierBugCheckIfAppropriate+3c
Bugcheck code 000000C4
Arguments 00000000`000000e3 fffffa80`0f0d1531 00000000`073bf278 00000000`00000000
BiosVersion = F5
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\040212-18595-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  2 23:55:07.316 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:27.814
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  AppleMobileDev
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02c9cc35
BiosVersion = F5
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\040212-16614-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  2 19:43:24.370 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:07.853
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`00cd1d00
BiosVersion = F5
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

mack2331 · 03 Apr 2012

Thanks for the reply John.

I removed the AMD Overdrive. I'm using a Nvidia graphics card so no need to re-install or anything. I did go into device manager and didn't see any AOD driver. So I assume it has been removed.

I unplugged all connections inside the case and plugged them back them, making sure they were snug and fully in.

I've ran MemTest86+ the other day and I couldn't get any errors. Maybe I'll give it another go tonight while sleeping.

Anyhow. I played Realm of A Mad God again to see if I could get another BSOD after removing the AOD driver/program and after messing with the connections. Sure enough I got another one.

Sadly though, I went into my mini-dump file after restarting and I guess it didn't produce one. All I have is the same ones from last night. This one was different and I feel like an idiot for not writing it down and assuming that it created a log in minidump. The error was something to do with a Page_file_error or something. I'll try to reproduce it and get something that might be helpful.

I'm going to uninstall Eset now and just toss in Microsoft Sec. Essentials and see what happens.

Thanks again for the help.

EDIT: Also, I was running HWMonitor to keep a check on temps. When I play Minecraft usually the graphics card will hit around 70c. On Realm of a mad god it was only hitting 114F. Not really that high temp wise. I'll keep playing around.

usasma · 03 Apr 2012

Please run the hardware diagnostics that I suggested above.
Hardware Diags

mack2331 · 05 Apr 2012

Just a quick update:

Ran MemTest again, let it do 4 passes and produced nothing (on top of the 2 I ran before). I ran FurMark and "maxed out" at 85C with the fan maxing at 75% for about an hour. I ran it at my screens full resolution to try to push it a little harder and got it at 87c and the fan at 77-78%. Is there a way to push it harder?

I'm going to do the Prime95 test. Only one issue. On the "warnings" for it, it states that not to let the CPU to go over 60c or Prime95 could error out. I'm using HWMonitor and it's not showing a CPU temp. Just says 0c on all cores? Any way I can "fix" this issue before running this test?

I'm now going to run the SeaTools and try out my Hard drive.

Thanks

Edit: Ran SeaTools (Long Test). Finished w/ no errors.

usasma · 06 Apr 2012

With the system not reading temps on the CPU - I'd have to wonder what's wrong. You have a recent CPU and motherboard - so the sensors should be there to read the temps.

Does the BIOS read any temps for the CPU?

Please use this free tool: HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools and post a screenshot of it for us to have a look at.

Don't worry about Prime95 erroring out - but we do worry about the CPU temp.
If you can't monitor the temp, then you won't know if/when it's overheating.
You can run it anyway and keep a close eye on it. That way, should it cause problems you can shut it down before the CPU overheats to the point where it shuts itself down (don't forget that it stays in the System Tray when you close the program).

mack2331 · 06 Apr 2012

Downloaded HwINFO64 and it seems to read the CPU temps. I went into my BIOS this morning and checked to see if it was showing CPU temps and it was. I guess it must be an issue with HWMoniter. The Screenshot you requested is attached to this post.

Thanks again Usasma!

If all looks good to you, I'm going to run Prime95 tonight when I get back home.

usasma · 06 Apr 2012

I'd say have a go at Prime95 - and be sure to monitor the temps (and voltages).
Good luck!

mack2331 · 08 Apr 2012

Ran Prime95. No errors.
I ran into someone else that was having the same issue (on facebook nonetheless lol) and found that AMD and 4dimms don't get along for some reason. I did further research and found this AMD CPU + G.Skill DDR3-1600 - GSKILL TECH FORUM

I'm gonna give this a shot and will report back to see if that's the issue. Just for future ref. if this is a "fix" or not