BSOD on startup, several startups and repairs required to boot Windows

[jurhill]

Hello, This is my first custom built computer. I've had the same similar problem for the past year. I have continuous problems starting up and BSOD. My computer will not start up properly at times. It also seems like this problem happens if my computer is off, not in sleep mode, for longer than 24 hours. It involves several restarts. I've checked my hard drive and memory for bad sectors and not found anything. I've run both the memtest and the windows memory test several times and found no problems.

There was one post I found on a seperate site that talked about ASRock m/b having problem with Ram voltage so I've manually changed the BIOS to be the voltage required for the Ram. Seemed like it fixed it temporarily but quickly started getting more BSOD.

Recently updated AMD drivers and was completely unable to get into Windows. When I restored the system to before the AMD updates I was able to get into Windows.





Some of the BSOD:

• Bad_Pool_Header
• Bug_Code
• Memory_Management

Below are my system specs:

• Processor: AMD Phenom II X4 840 3.2GHz Socket AM3 95W Quad-Core
• Motherboard: ASRock 890GX PRO3 AM3+ AMD 890GX
• RAM: 4 GB - Patriot G Series ‘Sector 5’ Edition 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600
• Hard Drive: 2 TB - HITACHI Deskstar 7K2000
• Graphics Card: Visiontek 900299 Radeon HD 4670 Graphic Card - 750 MHz Core - 1 GB DDR3 SDRAM - PCI Express 2.0 x16 - 1600 MHz Memory Clock - 2560 x 1600 - CrossFireX
• DVD Drive: ASUS 24X DVD Burner

Windows 7 . . .
- x86 (x64)
- Professional
- Full retail version
- Age of system (hardware)? 1 Year
- What is the age of OS installation - 1 Year (reinstalled once)


I've attached the dump files and system health report.

Can anyone help with this ongoing problem?

 

[writhziden]

Software Concerns:

Recommend removing your ASRock utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.

Remove any fast USB charging utilities. Such utilities put the usb ports in an unnatural power state that can cause instability and crashes.​

Analysis:

Crashes primarily point to memory issues.

• If you are overclocking any hardware, please stop.
  
  
• 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.
  
  
• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

 

[jurhill]

Thx writhziden!

Is the BIOS the only place I need to turn overclocking off? If anything is overclocking it would be from a default setting because I barely know what overclocking is.

I've uninstalled all the ASRock utilities. Today I also ran the extended Windows Memory Diagnostic Tool with 5 passes. No errors came up in the event display. However, I did notice there were several errors in the event viewer and have attached a screenshot of that. Not sure if that gives you any ideas about what could be going on. I've also attached a file with all screenshots from the CPU-Z program.

I'll try and run the windows diagnostic tool again and see if anything comes out.

What would next steps be?

Thanks,

Jurhill

 

[jurhill]

FYI...While looking into the overclocking in my BIOS I realized that it could be updated. The BIOS has been updated from 1.1 to 1.4. Hopefully that will help some of this along.

 

[writhziden]

Yes, a BIOS update can provide more stability. Let us know how the system responds to that treatment.

Also, it is unlikely you are overclocking if you have not changed any settings. ASRock utilities were the only way you might have been overclocking without being aware of it, so good job in removing those.

 

[jurhill]

The newest BIOS is working. However, I'm still getting BSOD.

The second extended Ram test came up with no errors. However, when I came home today a BSOD was waiting for me.

I've attached the newest dump file.

One other thing: I've had problems leaving my computer on overnight and it randomly crashes and shutsdown. Even in sleep state. Does that give any clues? Does the new dump file point at anything?

 

[writhziden]

Crash still points to memory. Your RAM does not appear to be compatible with your processor. XMP RAM is designed for newer processors and does not work well with Phenom II processors. You can try changing the RAM timings in the BIOS so the first four timings are 7-7-7-20 with the remaining timings automatic. Also set the frequency to 533 MHz if possible, or auto if you cannot manually set it to that frequency.

If you need help doing the above, let us know.


Further reading:

AMD Phenom

System Building and Compatibility

AMD Memory for Systems​

 

[jurhill]

I changed the frequency to 1066 (533hz) and believe I got the timing as you asked however still BSOD. I have the voltage on auto and will try making it 1.6v which is a little lower than what it asks for at 1600.

As I said, Two more BSOD, they are attached. Are these still pointing to RAM? If the voltage thing doesn't work is this something where I should consider buying different RAM? Is there any other fixits out there?

 

[writhziden]

Yes, crashes still point to memory as the likely cause. Please upload the cpu-z memory tab screenshot again. The other tabs do not need to be uploaded again.


Also, set the DRAM voltage back to 1.5 Volts. Increasing to 1.6 Volts will not likely improve stability and may damage components. If you want help with voltage settings:

Access your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability​

 

[jurhill]

Hello,

I did reset it to 1.5v. All other power settings were on auto.

I've attached the screeen shot you asked for.

I doubt this means anything but I've noticed when the BSOD come up and I try to restart the computer, the windows repair usually works much better if i power everything off and then power back on rather than just reset.

Any other thoughts? I really appreciate the help with this

 

[jurhill]

I don't know what just happened but my desktop just went nuts with errors. Everything error out and error reports were flying like mad. Could this be related to the changes? I didn't change anything other than the volts.

Attached are the minidumps:

 

[writhziden]

Analysis:

Crashes still point to memory. Given the extent of the crashes and what you have described for repairs, I suspect a bad module is at work.

Test the memory slots and modules as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.
​

 

[jurhill]

Wow, you really have 11,000 posts! Wow, I'll try your steps but had to comment

 

[jurhill]

I was trying your steps yesterday and decided to run Memtest one more time overnight on the first stick of RAM. No errors came up. However, when I tried restarting chkdsk came up and populated several lines of

"Deleting Corrupt Attribute Record......"
"Recovering Orphaned File...."
"Inserting Data attribute into file....."

Is something corrupt? I don't see any minidumps associated from it and from what I can tell my files look okay.

 

[jurhill]

I was literally typing my "Resolved" post when I got another BSOD....

For sure one stick is bad. I put too much faith in Memtest. Each slot gave a BSOD on startup for the first stick. I tested one a day for the last week and a half as my problems came when the computer was off for an extended period of time. The second stick was able to boot into Windows without any problems in each slot. Today was the last test and it booted fine.

I was just downloading a few updates, specifically a new AMD video drivers from the Vision Center, when everything crashed. This happened twice today and I've attached the minidumps.

Any thoughts? Should I buy entirely new RAM or is this related to a different issue like the video card? I'm extremely happy that I'm able to boot without error as I've never been able to do that. However, it seems as though the problem is not fully resolved.

 

[jurhill]

Or would anything be related to the "Deleting Corrupt Attribute Record" that I typed earlier? I've been testing my hard drive and it looks okay. However, I have noticed certain things are either gone or partially missing.

Do I need to re-install something?

 

[jurhill]

Analysis:

Crashes still point to memory. Given the extent of the crashes and what you have described for repairs, I suspect a bad module is at work.



Test the memory slots and modules as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.
​

I found that one module is fine and the slots don't seem to be the problem yet. Did you have any feedback?

 

[jurhill]

I think writhziden is MIA, does anyone have any ideas?