Had a Custom Built PC-Monthly BSOD, is now turning more frequently.

[yaholic]

Hey Guys. I could really use some help with an issue I've been experiencing. It's a bit of a long story so bare with me and I'll try sum it up as best as I can.

I custom built my computer almost six months ago now. Here are some basic specs:

Windows 7 Home Proffesional 64 bit,

Cpu: I7 2600K
Motherboard:Gigabyte GA-Z68XP-UD4
Graphics card: MSI GTX580
Two Hard drives, Windows is installed on a Cosair Force series solid state drive (the red one)
Cosair ATX 850 PS

I had the store I bought the parts from build it. Now, when I got it home there were issues right away, constant BSOD's. I brought it in, they figured it was a compatibility issue and fixed it. Great, however since then, about once a month, I'll recieve what seems to be a random blue screen of death. Normally, it will always fail to create a dump file, however, finally in march, it did create one which I've attached amongst all the info you guys requested.

Basically, I'll be surfing the internet, playing a game, doing whatever, and all of a sudden everything will just start to freeze up. It'll stay frozen for a good minute before finally BSOD'ing.

My event viewer has a whole bunch of weird errors, however, I check before every crash, and there's not one thing that happens right before it. It's inconstant that way.

I'm hoping you guys can help, as, over the last few days it's BSOD'd twice. Which would seem to be it's increasing in the rate this is happening.

Thanks a lot!

*edit*

forgot to mention

bsod 0x00000f4 seems to be the constant error number. I've googled online for any info but from what I can tell it seems to be somewhat of a random bsod :/

 

[Solarstarshines]

you ever check the RAM for Instability ?

 

[yaholic]

you ever check the RAM for Instability ?

There was a program I forget exactly what it's called...memtest? something like that? where it had a blue dos screen look almost and it continues to run. I ran it for a good...I believe it was 24 hours, and didn't turn up any errors.

http://www.memtest86.com/

this was the one.

P.S. I'm pre-loading Max Payne onto my pc right now. I can't wait .

 

[writhziden]

Your oldest crash was due to your New DeathAdder Mouse driver. The last two crashes both indicate an Atheros wireless driver. I currently see an ASUS wireless adapter, though...

Did you change wireless adapters at some point?

You random crashes with 0xF4 indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, uninstall it in device manager and see if the system performs better.
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

NOTE: Memtest86+ is not the same program you ran and is highly recommended instead of Memtest86.

 

[yaholic]

Thanks for your repsonse. I'll go through this all and update this with a response.

Just an FYI, I unfortunately just had another BSOD while playing Max Payne 3, this one was a new one,

0x000007A Kenrel Data Inpage Error.

Yet again, it failed trying to save the dump.

 

[writhziden]

You may want to check your hard disk cabling, as well. Look into getting a different/new cable to test.

As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.


For that Bugcheck:

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
  
  
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
  
  
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.

 

[yaholic]

Trying to run the memtest86+ however I've tried both USB and cd boots and it won't start. It gets to the actual screen where the test should start running but I just stays idle. I've waited for five-ten minutes nothing. Any idea why this would be?

 

[writhziden]

See if you can run it with your hard drive disconnected. It may be interfering with the load process.

The hard drive shouldn't interfere since Memtest86+ runs in the memory, but it is still a good idea to try it with the hard drive disconnected. I know hard drive/hard drive connection issues can sometimes interfere with the system running properly even with diagnostics loaded in memory. They can even prevent the BIOS from loading or POST from happening.

 

[yaholic]

Tried disconnecting both hard drives, still won't run



There's an error at the bottom 140k e820 off. What does that mean?

 

[writhziden]

Ah, that means one of your modules is blocking it from running. Reconnect the hard drive. Remove all but one RAM module. If that module still blocks it, swap it for another, etc.

Remember ESD safety.

 

[yaholic]

Ah, that means one of your modules is blocking it from running. Reconnect the hard drive. Remove all but one RAM module. If that module still blocks it, swap it for another, etc.

Remember ESD safety.

Ok so I did this. And not one stick of ram worked.

I have two sticks of ram, one ins lot one, one in slot three. I attempted every combination you can think of (ram#1 in slot#1, ram #1 in slot 3, ram #2 in slot #1, ram #2 in slot #3)

Not one time could I run memtest. Got that error everytime. Would this mean it's a motherboard issue?

 

[writhziden]

Quite possible.

Make sure all your power connections are good and all hardware is properly seated. You may consider taking everything out except the CPU/heasink/fan combination and then putting everything back in carefully. Then try Memtest86+ again. If that does not work, remove the heatsink/fan assembly and the CPU and check for any bent pins on the CPU.

 

[yaholic]

Quite possible.

Make sure all your power connections are good and all hardware is properly seated. You may consider taking everything out except the CPU/heasink/fan combination and then putting everything back in carefully. Then try Memtest86+ again. If that does not work, remove the heatsink/fan assembly and the CPU and check for any bent pins on the CPU.

At the risk of voiding my warrenty I probably won't do that. I still have a year warranty with the place that built my pc, so I'll probably just bring it in. Just wanted to see if it's something I coudl fix on my own, but yeah that woul dmake sense. Second times I've had issues with this motherboard should of went with the asus.

Cheers for the help, after I bring it in, I'll report back here, letcha know what it was for sure.

 

[writhziden]

Good idea to let the builder handle it. Sorry it was not something simple.


Look forward to when you know more.