BSOD from either the Motherboard or the GPU.

Bruggs · 29 Sep 2014

BSOD from either the Motherboard or the GPU.

Okay, I'm unsure of which it is. Or, if it's a software issues, but I keep getting a rash of BSOD's. First, here are my specs.

OS: Windows 7 Pro 64Bit Debugged SP1
CPU: Intel Core i7-4790 3.6GHz Quad-Core Processor
CPU Cooler: Corsair H110 94.0 CFM Liquid CPU Cooler
Motherboard: Asus MAXIMUS VII FORMULA ATX LGA1150 Motherboard
Memory: Corsair Vengeance Pro 16GB (2 x 8GB) DDR3-2400 Memory
Storage: Samsung 840 EVO 250GB 2.5" Solid State Drive
Storage: Samsung 840 EVO 500GB 2.5" Solid State Drive
Video Card: Asus GeForce GTX 760 4GB ROG Video Card
Case: Corsair 450D ATX Mid Tower Case
Power Supply: Corsair RM 750W 80+ Gold Certified Fully-Modular ATX Power Supply

One of the most common I have been getting is a 0X0F4. But, there have been others, too. I've flashed the BIOS, flushed the CMOS and reinstalled Windows three times. I mainly the the 0X0F4 when I try to launch a .exe. I was trying to install HD Sentinal to monitor my SSD's, and also Norton Utilities. Each time, BAM! BSOD! I've run Memtest86 for six hours and no errors are found. I haven't even boosted my RAM past the default speeds. I was hoping to get her running perfectly before I started to OC and whatnot.

I'm going to add into this a dump log of a couple different crashes. It doesn't have the 0X0F4 crash, though. I've started to get rid of all the ASUS software that I installed hoping that it is the culprit, but I'm still unsure. The following are the dump logs...

On Sat 9/20/2014 4:02:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-8439-01.dmp
This was probably caused by the following module: iomap64.sys (0xFFFFF8800A7DF988)
Bugcheck code: 0x50 (0xFFFFF8800C70075C, 0x0, 0xFFFFF8800A7DF988, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\iomap64.sys
product: ASUS Kernel Mode Driver for Windows
company: ASUSTeK Computer Inc.
description: ASUS Kernel Mode Driver for NT
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iomap64.sys (ASUS Kernel Mode Driver for NT , ASUSTeK Computer Inc.).
Google query: ASUSTeK Computer Inc. PAGE_FAULT_IN_NONPAGED_AREA

On Sat 9/20/2014 4:02:16 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iomap64.sys (IOMap64+0x1988)
Bugcheck code: 0x50 (0xFFFFF8800C70075C, 0x0, 0xFFFFF8800A7DF988, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\iomap64.sys
product: ASUS Kernel Mode Driver for Windows
company: ASUSTeK Computer Inc.
description: ASUS Kernel Mode Driver for NT
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iomap64.sys (ASUS Kernel Mode Driver for NT , ASUSTeK Computer Inc.).
Google query: ASUSTeK Computer Inc. PAGE_FAULT_IN_NONPAGED_AREA

On Sat 9/20/2014 2:15:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-11325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0009F97D0, 0xFFFFF8A0009F9A30, 0x526010E)
Error: BAD_POOL_HEADER
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 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.

This is my first build, and it's all going wrong. We get a POST, the OS loads and runs, Steam on the 500GB runs fine, MS Office installed fine. But, other things just keep crashing it.

I should also mention I ran sfc /scannow and there was no integrity errors.

Any help would be appreciated.

Bruggs · 01 Oct 2014

Here is the DM log, too.

Golden · 01 Oct 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800c70075c, 0, fffff8800a7df988, 2}

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

Could not read faulting driver name
Probably caused by : IOMap64.sys ( IOMap64+1988 )

Followup: MachineOwner
---------

WinDBG blames the ASUS SmartDoctor application. See if there is an update for this application. If not, the only fix I have seen for this is to uninstall the application completely.

ASUSTeK Computer Inc. -Support-

Bruggs · 01 Oct 2014

I had removed that, along with a ton of other Asus programs. The 0X0F4 error is the only one that is giving me issues, currently. I crashed my machine last night and left it on the screen like the photo above hoping to catch the log. But, after seven hours, it stay frozen like it was. I was able to install Norton Utilities and did a quick reboot. But, if I try to launch the program, 0X0F4...

I'm attaching a .txt that came from MiniToolBox.

Golden · 02 Oct 2014

Lets go hard-core.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

Bruggs · 02 Oct 2014

Okay, I got that all going. When I get home from work, I pray it did its thing. As of this try, I just ran the GPU and Audio drivers. Those are the ones I suspect. But, I shall upload(hopefully) the dump file later today.

Bruggs · 04 Oct 2014

Okay, here's the latest one. I ran the veirifer on only a couple drivers, which didn't show anything. So, I then ran it on all drivers. Then, BAM! Right away I got a new error code of 0XC4. I'm tossing up the three most current dumps. I don't know if they're the same, though.

Golden · 05 Oct 2014

Please run the following scan for rootkits:

TDSSKiller Download

Bruggs · 05 Oct 2014

Thanks, I'll try this, too. Well, after I'm done with homework and all. Probably won't be until Monday afternoon.

Bruggs · 06 Oct 2014

Well, unfortunately, that did about nothing. It warned me of a program I installed called HDWinfo or something like that. It's to monitor my temps and stuff. Looks like I am just going to start over. I'm going to pull the SSD tonight, reformat it, and run Win 7 again.

But! This time, I'm going to go bit by bit. Add a couple drivers, reboot. Run the Verifier, reboot. So on and so forth. Maybe I'll catch what's wrong, if anything, in the next go round. This has been killing me!