You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

computer keeps giving me a BSOD, need help fixing

i just built this computer about 4 months ago, 2 months after building it my HD crashed so i bought a new one[the one that crashed was around 8-10 years old]. after i installed all my programs and drivers n such, about a month ago the computer started to bsod once a week or so, then it finally got to where it is BSOD after being running for 15mins-1 hr and after it does it the first time it continues to every 5 mins after restarting, i looked it up best i could and the error im getting says its either 1 of 2 things: my software wasnt up to date, or my pc isnt reading one of my sata items correctly[HS, and DVDr/w] properly and that i needed to swap the sata slots they were plugged in to, which also didnt help. So any help i could get would be much appreciated, just let me know what logs or whatever information is needed to help me fix this thing so i can have my free time to play my pc games again, that way i dont go postal on some1! lol

the error code i get on the BSOD 90% of the time is this: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa80057bdb30, 0xfffffa80057bde10, 0xfffff80002bdc270). A dump was saved in: C:\Windows\MEMORY.DMP. [thius came from the event viewer program on my pc]

Description: The program GFExperience.exe version 12.4.67.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Description: wuaueng.dll (1000) SUS20ClientDataStore: Corruption was detected during soft recovery in logfile C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log. The failing checksum record is located at position 2111:426. Data not matching the log-file fill pattern first appeared in sector 2304. This logfile has been damaged and is unusable.

Error: (07/09/2014 09:24:02 PM) (Source: ESENT) (User: )

Description: wuaueng.dll (1000) SUS20ClientDataStore: The log range read from the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 1080832 (0x0000000000107e00) for 512 (0x00000200) bytes failed verification due to a corrupted checksum log record. The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.

Error: (07/09/2014 09:24:02 PM) (Source: ESENT) (User: )

Description: wuaueng.dll (1000) SUS20ClientDataStore: Corruption was detected during soft recovery in logfile C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log. The failing checksum record is located at position 2111:426. Data not matching the log-file fill pattern first appeared in sector 2304. This logfile has been damaged and is unusable.

Error: (07/09/2014 09:24:02 PM) (Source: ESENT) (User: )

Description: wuaueng.dll (1000) SUS20ClientDataStore: The log range read from the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 1080832 (0x0000000000107e00) for 512 (0x00000200) bytes failed verification due to a corrupted checksum log record. The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.

The 0xc0000005 for the NvBackend.exe driver under application errors indicates that driver is faulty, and needs to be replaced or updated.

You aren't connected to a server, are you? The wuaueng.dll SUS20ClientDataStore error under Microsoft Office errors happens when a client machine can't connect to the information store on a server, and can cause failed Windows and Microsoft updates. If you are, you need to alert the system administrator. If you aren't connected to a server or domain, try this: http://support.microsoft.com/kb/949104

The 0x0000007a error for the Ntfs.sys driver indicates the hard drive may be failing or there are bad sectors/corrupt data. Errors involving this driver can result in loss of data.

The 0x0000007a error for the ntoskrnl.exe driver cites c000009d in Parameter 2 in some of the error logs. That code usually occurs when there are connection errors with the hard drive, the result of problems with the cable connecting it to the motherboard, or the controller not being able to see the hard drive.

The 0x000000f4 errors likewise point to problems with the hard drive.

Back up any important data, then open a command prompt by typing cmd in the search bar. Right click the icon and select Run as administrator. Type in

chkdsk /f /r

and hit enter.

If that doesn't fix it, you may also want to run a memory diagnostic, either the built in Windows memory diagnostic tool or memtest86+.

If the memory tests come back clean and the blue screens still occur, your hard drive is probably failing.

May not be the hard drive itself -- could be the controller, or the cables, or errors in the file system on the drive.

But all those error codes point to something involving your hard drive causing the blue screens.

Make sure your cables are properly connected. You may want to try swapping them out for other cables that are known to be good. I would also run chkdsk on the drive. And run a memory diagnostic test, if only to rule out issues with your RAM being part of the problem.

Ive tried what you said, and I had to update my bios and chipset, it ran fine then all of a sudden it froze, blue screened again, and now when I try to start up windows it makes it to the windows loading screen the bsods. I cant see anything it says because it restarts immediately,so can I get soMe help to fix it? Or do I have to reformat?

I say I had to cuz I was checking all my drivers to make sure they were up to date cuz I read that having out of date drivers for: mobo, chipset, and having an out of date sp for windows can also cause the BSOD im dealing with. No it didnt start after I ran chk, it just started about an hr maybe 2 after I updated and ran it, then it started

I would suggest you roll back all those updates, if you can get it to boot to a stable environment.

Did you try using a new cable to connect the hard drive to the motherboard?

What kind of hard drive do you have -- solid state or a hard drive with platters? Did chkdsk find any errors?

Again, try pressing F8 when it boots and see if you can get to the recovery console to do a startup repair. If you have a recovery or installation disk, try booting from that if it won't boot to the recovery console from the hard drive, and navigate to start up repair in the recovery options on the disk.