Multiple BSOD Errors when gaming/youtubing and failed startups

JamesNasium · 20 Aug 2013

Hi all, first time SevenForumer, but looks like a good place to get some expert advice!

I'm having issues with my custom build. This is a long, historic problem with this build. I get BSODs (multiple types, minidumps attached) generally when gaming or watching youtube. Right after this happens, when I reboot, I will have trouble getting my computer to startup successfully. It will either fail to post, or windows will freeze again when it is starting up (but no BSOD here I believe, just a freeze).

This type of problem has been happening with this computer for about a year on and off. When it originally started happening, I had run memtest and saw errors so I actually ended up buying new RAM (the ones I have installed now). I have re-run memtest with this RAM and it too got memtest errors. At that point I figured it might be the mobo slot so I took out one of the sticks and ran memtest with with the single DIMM in different slots until I didn't get errors. That's the way I have it now. Everything was peachy until about a month ago when these problems started popping up again. So now I am just confused and uncertain about whats happening with my computer! Should I get a new mobo? That will be a headache, so hoping there might be another solution.

I'm attaching all my minidumps. They include some from back in March but i guess I would like to focus on the ones since late July to now. The most recent one, from Aug. 20th I believe I had driver verifier running FYI.

Appreciate any help with this!

Thanks

koolkat77 · 21 Aug 2013

Update or remove the drivers listed below:

UltraMonUtility.sys Fri Nov 14 07:10:30 2008
UltraMon multi-monitor
Driver Reference Table - UltraMonUtility.sys

AsIO.sys Mon Apr 6 13:21:08 2009
Asus PCProbe Utility
Driver Reference Table - AsIO.sys

ASACPI.sys Thu May 14 07:25:17 2009
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

AODDriver2.sys Thu Apr 5 15:23:37 2012
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys

(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 (but DO NOT 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) Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Upload a screenshot using:

CrystalDiskInfo

For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+

Tip

Pay close attention to part 3 of the tutorial "If you have errors"
Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Test your Hardware for Stability and Heat Problems with Prime95:

Stress Test With Prime95

How to Stress Test a Video Card with Furmark:

Video Card - Stress Test with Furmark

Test your CPU Stability with IntelBurnTest:

CPU - Stress Test Using IntelBurnTest

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:

Piriform - Speccy

CPUID - HWMonitor

Dumps...

Code:

Debug session time: Wed Aug 21 04:49:25.471 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:00:09.157
Probably caused by : AuthenticAMD
BugCheck 124, {0, fffff980056c08f8, 0, 0}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffff980056c08f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Aug 18 10:54:04.042 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 21:32:50.783
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
BugCheck 1000007E, {ffffffffc0000005, fffff88005399ec8, fffff88003ccd6a8, fffff88003cccf00}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88005399ec8, The address that the exception occurred at
Arg3: fffff88003ccd6a8, Exception Record Address
Arg4: fffff88003cccf00, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Aug  7 06:08:42.622 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 1:32:46.292
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by : usbohci.sys ( usbohci+2a45 )
BugCheck FE, {5, fffffa8004ca11a0, 10024397, fffffa8004b66258}
BugCheck Info: BUGCODE_USB_DRIVER (fe)
Bugcheck code 000000fE
Arguments: 
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
	using a physical memory address that was not allocated by
	the USBport driver.
Arg2: fffffa8004ca11a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa8004b66258, Pointer to Endpoint data structure
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci+2a45
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Aug  4 03:42:20.305 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 3:48:20.585
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BugCheck FE, {5, fffffa8004c901a0, 10024397, fffffa80039f8968}
BugCheck Info: BUGCODE_USB_DRIVER (fe)
Bugcheck code 000000fE
Arguments: 
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
	using a physical memory address that was not allocated by
	the USBport driver.
Arg2: fffffa8004c901a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa80039f8968, Pointer to Endpoint data structure
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_nt!PoIdle+52a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Aug  3 23:53:40.747 2013 (UTC + 6:00)
*** WARNING: Unable to verify timestamp for fvevol.s
*** ERROR: Module load completed but symbols could not be loaded for fvevol.s
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:00:13.027
*** WARNING: Unable to verify timestamp for fvevol.s
*** ERROR: Module load completed but symbols could not be loaded for fvevol.s
Probably caused by : memory_corruption
BugCheck 4E, {7, 83e7e, 83f7e, 0}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 0000000000083e7e, page frame number
Arg3: 0000000000083f7e, current share count
Arg4: 0000000000000000, 0
BUGCHECK_STR:  0x4E_7
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Aug  3 23:40:15.523 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 1:53:39.193
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BugCheck FC, {fffff88004808c70, 80000001274ea121, fffff88003cc5ec0, 0}
BugCheck Info: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
Bugcheck code 000000fC
Arguments: 
Arg1: fffff88004808c70, Virtual address for the attempted execute.
Arg2: 80000001274ea121, PTE contents.
Arg3: fffff88003cc5ec0, (reserved)
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  0xFC
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFC_nt!PoIdle+52a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Aug  2 05:38:54.093 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:27:53.763
Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 )
BugCheck 50, {ffffffffffffffe3, 0, fffff80002c6544b, 0}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: ffffffffffffffe3, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c6544b, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ExQueryPoolUsage+e0
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

JamesNasium · 22 Aug 2013

Thanks for taking the time to look into this and for your reply, koolkat77.

I'm going to get started on going through this list of things to do you presented here. Couple questions first:

The UltraMonUtility driver is fully up to date, does this mean I need to remove it? Ultramon is a really handy piece of software and I'd like to keep it if possible.

What is the best way to remove these other drivers (AsIO.sys, ASACPI.sys)? From device manager?

Thanks

koolkat77 · 22 Aug 2013

Try uninstalling from Add/Remove Programs from control panel.
You can also try removing them using Revo Uninstaller free.

Information

Download and install Revo Uninstaller free from here:

Download Revo Uninstaller Freeware
Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Let us know when you have completed the rest of the steps.

JamesNasium · 24 Aug 2013

Posting an update on progress:

- Removed UltraMonUtility.sys driver
- Removed ATK0110 ACPI Utility Driver (ASACPI.sys)

- I had the latest version (5/5/2009 1043.6.0.0), no new updates found, so I uninstalled it

- AsIO.sys driver seemed to be removed after I uninstalled ASACPI.sys
- AODriver2.sys has been removed via the removal of Catalyst Control Center

- reinstalled just the video card driver
- this had the side-effect of removing my Northbridge driver; i followed this guy's steps to install just that driver without installing catalyst again: AMD PCI Express (3GIO) Filter and PCI Bus Driver requires manually updating. - Guru3D.com Forums

- Installed CrystalMark, screens to follow:
Attachment 283069

Attachment 283070

Attachment 283071

- Ran full diagnostic utility on Intel X25M SSD using Intel SSD Toolbox program: Results were OK.

After that I skipped to doing some memtest cause that's where my suspicion was. I got through 7 passes in my current configuration (DIMM "A" in slot 4 of mobo) with no errors. Then I tried to put DIMM "B" in slot 3 and run with both sticks in. My computer would not even POST with this configuration after many attempts. I took out DIMM "A" and just tried to run with that configuration (DIMM "B" in slot 3). No POST here either. Put DIMM "B" in slot 4 and the computer booted OK. So right now I'm seeing that my mobo won't POST with a DIMM in slot 3. Not sure what's up there. Can anyone verify if my memory is compatible with this motherboard? CMZ8GX3M2A1600C9B memory, M4A79XTD EVO motherboard.

essenbe · 25 Aug 2013

The QVL for your board can be found here M4A79XTD EVO - Motherboards - ASUS
If your ram is not on the list it does not mean it is not compatible. You can also check corsair's web site. Some ram manufacturers have a list of boards they have tried it out on.

I know it is time consuming, but you need to run memtest with 1 stick in each slot, 1 at a time. Do the same for the other stick. What you are doing is checking the ram as well as checking the dimm slots on the motherboard. If both sticks, 1 at a time, can pass memtest in every slot except that 1 slot, the slot is bad. You'll have to RMA the board.