Stop Code Help

Bruggs · September 22, 2014

I keep getting BSOD on a machine I just built. It's my first build, and I don't know what to do. Everywhere I look it says to run the Win 7 disk and click repair. But, when I do, it says it's not needed.

OS: Windows 7 Pro 64Bit Debugged SP1 (Had to edit)

Specs of my machine...

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

Now, no hating on this, but it crashes when I try to run .exe's. Norton Utilities tells me I don't have the minimum req's, and HD Sentinal loads, then I get the BSOD

RAM seems to be just fine, flashed the BIOS to the latest version 6XXX(Can't remember the whole thing), and the GPU is updated. I ran the latest version of Realtek last night, also. Any help would be awesome...

Lavachyste · September 22, 2014

It crash on every .exe you clic?

Bruggs · September 22, 2014

So far, just the two. I was able to put Steam and some games on my 500GB D drive. I also cannot install some programs, like Flash Player. This was a clean and new OS that I got from DeVry Student Store. And, if need be, I bought a new copy of 7 Ultimate off Amazon. My one buddy said to try to run the MD5 Hash and see if it matches up. Well, I downloaded MD5Summer and got the hash off there, but don't know how to do it through the OS. I ran a sfc /scannow and it came back clear (Have it copied on my laptop at home).

I'm just stumpted.

Bruggs · September 22, 2014

Then, we've got this.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

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.