GA-Z77X-UD3H BSOD all the time on new build

[rob909e]

Hello,


I'm at my wits end with a custom build from cyberpowerpc and now I'm turning to the forum for help. I purchased and received my pc about 3 months ago and it's been crashing and restarting daily since then. The BSOD mainly would happen during game play, but also would happen while surfing the web. Originally, I thought the problem could be related to a faulty install of the OS, which at the time was windows 8 64. Because I purchased my PC without an operating system, the Microsoft store was responsible for Windows 8. Microsoft had remotely installed so many times, they went and upgraded me to pro for free for the inconvenience. Needless to say, nothing Microsoft did seemed to fix the problem because it always returned.

I tried booting up from a Memtest dvd and running a memory test on each stick individually, but the test reported no errors. I tried reseating the graphics card, with no improvement. I tried many different Bios combinations with no luck. After a clean install of Windows 8 pro, I would install ONLY the essential UPDATED drivers for my GA-Z77X-UD3H Mobo, update the OS, then install the Latest graphics drivers for my AMD HD-7950. The only anti-virus software I tried was No anti-virus or MSE. Because I did so many clean installs of the OS, I tried many different combinations of settings in windows, thinking it could be a settings issue; no dice.

Because I couldn't fix it, Cyberpowerpc requested that I RMA it. I did. 1 month later I got my computer back. Cyberpowerpc has said the reason for all the BSOD was related to a improperly installed OS. To my surprise, when I booted up the PC, a Windows 7 Home Premium logo appeared. Because of the results of the RMA, I wasn't about to put Windows 8 on there again! Another call to the Microsoft Store and 2 days later, I had a Windows 7 Ultimate replacement DVD, once again, Microsoft hooked it up!

Because my issue had reached escalated status, microsoft wanted all the details about my computer, making sure they did'nt drop the ball when they put Windows 7 64 Ultimate on there. I told them that I did a secure erase of the Samsung 840 250GB SSD. Once completed, within BIOS I selected windows UEFI DVD as my boot and booted to the Windows 7 DVD where Microsoft proceed to install windows. Once installed. I express installed the mobo DVD. Microsoft finished all updates. I installed the graphics drivers. I installed steam and redownloaded Bioshock Infinite and Borderlands II. I plugged in my 360 controller, (crash would happen with or without the controller installed) check for more updates. Once everything was updated, (not much to update since since there was barely anything on the PC) I started up steam, pick a game, and within an hour or so CRASH! I made a video of it, the link is below

http://www.youtube.com/watch?v=oLYvg_UnWB4

I have mini dumps and I an 8GB FULL memory dump, which I don't even know how to look at; other than whocrashed.

MY BUILD



Motherboard - Gigabyte GA-Z77X-UD3H rev 1.1  BIOS v. F18
CPU - Intel Core i7 3770K
RAM - 2 x G.Skill 4GB DDR3 1600MHz Ripjaws X-Memory
Graphics - His IceQ X2 iPower AMD HD-7950
SSD - Samsung 840 250GB 2.5" SATA 3.0 Solid State (my only drive)
PSU - Corsair CMPSU-85-TX V2 Power Supply
Water Cooler - Asetek 510lc 120mm Watercooler
PCI Card - IEEE 1394 Firewire PCI card (due to crashing, not used)
DVD Drive - Samsung 24x DVDRW internal drive
Fans - 6 120mm fans (push pull) and 4 240mm fans
Case - AZZA Genesis 9000 Full Tower



And finally, The Crash report from Whocrashed!

Welcome to WhoCrashed (Professional Edition) v 4.01
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network...


System Information (local)
computer name: ROB909E-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8548024320 total
VM: 2147352576, free: 1891426304



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 7/12/2013 8:36:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071213-4851-01.dmp
uptime: 01:36:54
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80071E6028, 0xBE200000, 0x21136)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 7/12/2013 8:36:51 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 01:36:54
This was probably caused by the following module: wow64win.sys (wow64win+0x4164A)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80071E6028, 0xBE200000, 0x21136)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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: wow64win.sys .
Google query: wow64win.sys WHEA_UNCORRECTABLE_ERROR



On Fri 7/12/2013 6:25:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071213-5148-01.dmp
uptime: 03:16:03
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800725F028, 0xBE200000, 0x21136)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/11/2013 8:27:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071113-5210-01.dmp
uptime: 04:33:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007259028, 0xBE200000, 0x21136)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

wow64win.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


If someone actually made it this far, thank you. IF there is anything else I forgot to mention, PLEASE ask!



Rob

[absic]

Hi there,

have you tried the F19j beta BIOS available over at TweakTown? http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios.html This may be just a BIOS issue and testing with the latest beta might help. If there is no improvement of the situation you can always flash back to your current version.

I express installed the mobo DVD.

Did you let the Mobo disk install the added software such as EasyTune, XpressRecovery @BIOS etc? If you did have you tried un-installing these programs? On a personal note, I never install any of the utilities or extra software that comes with a motherboard and only use the latest drivers for the hardware I am running as I have found that sometimes, these programs can cause issues.

How is the BIOS configured? If you can grab some screenshots of BIOS and post them that would help as there might be something incorrectly configured there that is causing a problem that someone might see.

[rob909e]

First.  I really, really appreciate you trying help me out with this problem.

have you tried the F19j beta BIOS available over at TweakTown? http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios.html This may be just a BIOS issue and testing with the latest beta might help. If there is no improvement of the situation you can always flash back to your current version.

I have not tried the latest beta BIOS, but I do have the latest official release.   I'm starting to think that this is, most definitely a BIOS issue.   Not so much a bad BIOS, but possibly a misconfiguration  of the BIOS settings.  I'll be honest,  between all the hardware in the PC, I've been trying to figure out which settings will give me a stable,  system.   I've read through every user manual that came with my PC, including the on from Gigabye.   The settings and explanations are beyond the scope of anything I know. 

One thing.

I never messed with any overclocking.  but appearently I noticed that when I ran the app OCCT, it said my processor was clocking at 3900, and not 3500.  In Bios I switched the setting, Intel Turbo Boost Technology from Auto to Disable and that seamed to put my processor back at a normal clock rate.  I thought if you loaded the optimized defaults within BIOS, it would stop any overclocking?  Since making that switch in bios, I have not had a crash, but my CPU is always running at 100%

As for the Motherboard DVD.  After doing dozens a fresh installs of the OS,  I now only put the essential chipset drivers.  I scoured many forums, not to mention cyberpowerpc also suggested, only installing the chipset drivers and nothing else off the dvd.


I took pictures of Bios, but this forum wont let me upload more than 2 small files, so I zipped them up along with A readout from cpuz

[absic]

Well I would definitely try the beta BIOS as it may help resolve some of the issues.

The fact that your CPU was showing as 3.9GHz is normal and is because of the Turbo boost technology and is nothing to worry about. Disabling the feature in BIOS only means that you will not be using the full potential of your CPU.

A quick look at the BIOS pictures doesn't seem to show anything as being incorrectly set and as you say, loading Optimized Defaults should be OK for a stable system.

[rob909e]

okay..... Yesterday I was able to use my computer all day without a crash.   However,  I noticed that the mouse would lag behind at different points of operation.  So I checked Windows Task Manger, Processes and resources, it revealed a bizarre  process called mpchc64.exe  That same process also appears to be establishing an outside connection.  I've never used media player, nor have I installed any Adobe products on my computer,  MSE scan says its okay.   Here's the screen shots.....

[rob909e]

Update:

I'm almost certain I've got a bitcoin miner virus.  How?   I have no idea!  One thing is certain,  this is the cause of the high CPU.   I don't know if it's the cause of all my BSOD because I've secure erased the SSD so many times, hoping that if I reinstalled windows, maybe the BSOD would stop. 

Here is a link to a user that has the EXACT process hogging 100% of his CPU

http://superuser.com/questions/598323/a-malicious-threat-was-detected-in-media-player-classic-exe-file

Is it possible for a known infected computer to give my new computer this virus over an Ethernet connection; my home network?  Here is a map of my home network.

[rob909e]

UPDATE:

I don't know if the Virus was the cause of the BSOD I've been experiencing, so I went ahead a formatted (secure erased) the SSD, and reinstalled Windows 7 64 Ultimate again.  Also, before I erased and reinstalled Windows, I took my MacPro completely off the network, because if my pc is crashing all the time due to a virus, I don't want it hopping from the infected MacPro to my PC.

For the sake of finding the problem, I'm going to list everything I've done so far, in order.

1.   I downloaded latest drivers from Gigabyte (mobo), AMD (GPU), Samsung (SSD), and the Steam installer.   Then I saved them to a freshly formatted USB drive.

2.   I Secure Erase the Samsung 840 SSD by booting from the Samsung Secure Erase DVD.

3.   I booted to the Windosw DVD (decided to NOT go UEFI this time), since the SSD space was unallocated into the same space, I clicked next and installed windows 7 64

4.     Once Windows finished with the  install, I put in the USB  thumb drive and began installing the drivers, in order, restarting when prompted.

mb_driver_lan_atheros_813x_815x_816x
mb_driver_chipset_intel_7series
mb_driver_intel_me_7series
mb_driver_via_usb3
mb_driver_intel_usb3
mb_driver_audio_via
mb_driver_intel_irst_7series

5.      I then let Windows update until there were no more updates

6.     I installed the Samsung Magician Software 4.1 and optimized my SSD

7.     I installed the AMD HD-7950 Graphics Drivers

13-4_win7_win8_64_dd_ccc_whql

8.     I installed Microsoft Security Essentials

9.     I updated Windows

10.    I installed Steam and began downloading Borderlands II, Bioshock Infinite, PrimeWorld Defenders, Dota II. and a few other stupid games.....

11.     I plugged in my Wired 360 Controller

12.     I ran Windows Update

13.     I Installed the Games I downloaded from within the Steam App.


This is where I'm at right now.  I've run the Windows Task Manager and my CPU Usage is at 0% with no sign of the virus.  Also,  I'm using the same BIOS settings as shown in the Zip file I uploaded to this thread.   Now I will begin testing.

[absic]

Ah, the joys of troubleshooting.

Hopefully the cause has now been isolated and a clean install is always a good option if you can afford the time to do this. I know how long it can take as I do this with regular monotony due to the amount of testing/troubleshooting I do.

Thanks for the regular updates and fingers crossed that the problem doesn't come back on this system.

[rob909e]

UPDATE:

More Programs Installed

Firefox with security plugins - Ad Block Plus,  and No Script


     So far,  I've  been free from any system crashes (BSOD) However,  during the game Poker Night II I  had my very first crash to the desktop.  I'm assuming a single crash to desktop isn't worth getting upset or worried over, huh?  My CPU is always at 0% when idling and my computer seems to be running great.   As far as the Infected MacPro,  I've unplugged the RJ-45 Ethernet cable.  I also set the firewall on my new PC to block everything from my MacPro's IP Address, even though the MacPro doesn't have wireless capabilities.

     I'm not trying to Jinx myself, but I'm finding it hard to believe that a virus is the cause of all this.  Why?  Because I tried dozens of fresh installs on both Windows 7, Windows 8, and Windows 8 Pro.   Conversely,  if the BSOD's are virus related,  other then Anti-virus software and the firewall,  what other kinds of steps could I take to protect my system.  And since I've brought up the Firewall,  are there any settings, rules, or/and exceptions I should know?  I'm using Microsoft Security Essentials with the Windows Firewall.