BSOD after waking computer up

[Libram]

I woke up my computer from hibernation this morning, it ran just fine for awhile before giving me a BSOD. It created a dump file and rebooted the system. It is all working fine now, but this is a new set up and I can't stand to see it have problems! (I came from a VERY bad computer, and I want to see perfection in this one.)

-x86 32-bit Windows 7 Home Premium
-OEM (I installed it myself using a new hard drive and installing into my old computer)
-System hardware except Hard drive, power supply and graphics card is 4 years old (Yes I keep it dusted out and clean twice a month. GPU & PSU are both 2 years old. GPU has the very latest driver version. Hard drive is 7 days, never used (may have been in storage longer)
-OS Installation is 7 days old.

I would like to avoid any drastic methods such as re-installing the OS or reverting back to old data.

Programs I had left running in the background when I placed the computer into hibernation; xpadder, Steam, and SpeedFan.
Programs that start up Steam, Google Update, Side bar, and Microsoft Windows Operating System.
I haven't switched the computer off for 5 days, I just put it into Hibernate (which is like turning it off.)
If anyone can read my dump file and tell me the program or driver that may have caused this issue, I should be able to fix things from there.

-Thankyou! Libram

 

[zigzag3143]

We would prefer to work with more than one DMP file so we can spot trends etc. If you have them upload them.



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[Libram]

This is the only DMP file there is. This is the fist time windows 7 has ever crashed crashed on me.
I'll give memtest a try when I can grab hold of a CD. Also could I just use it on a USB Tumbdrive? I have a blank one. Thanks

 

[zigzag3143]

This is the only DMP file there is. This is the fist time windows 7 has ever crashed crashed on me.
I'll give memtest a try when I can grab hold of a CD. Also could I just use it on a USB Tumbdrive? I have a blank one. Thanks

Sure it runs just fine from a formatted USB

 

[Libram]

Sure it runs just fine from a formatted USB

Took a little bit to figure out how to boot USB drives since my BIOS isn't so straight forward about it. (It thinks they are hard drives and not a portable drive..... T_T )

Anyhow I had another question before I start the memtest scan tonight. Most of it is speculation, but It could help in finding the problem.
If this was my power supply causing any problems could it possibly trigger a BSOD? Just this morning I woke up to find my computer had woken itself up sometime during the night from out of hibernation. Everything was frozen, (No BSOD this time) the mouse wouldn't move and the keyboard wouldn't work. Usually these work just fine (I've had windows 7 on my computer for a few days now) So I think the computer may have hung up.
I pressed the power button down and the very instant I did it shut down without me having to hold down the button. So if this could also be a power supply problem, then why doesn't it freez when ever I play video games such as Call of Duty MW3, WoW, and Skyrim? I know that when playing a game like Skyrim, this demands gpu power and the gpu demands more power from the psu so it can process the game better. (More power required then that which is required from simply waking up the computer.)Its Corsair brand power supply so I knew it wouldn't be some off brand junk.

I have a feeling that it's just the RAM that's causing problems, because my old OS had really bad freezing problems before, being the reason why I replaced the Hard drive and bought windows 7 for the new hard drive.
So far I've narrowed it down to the problems being the RAM, PSU, CPU, or GPU.
The GPU and PSU being fairly new, I don't expect them to be causing any problems. Which narrows it down a little more to the CPU & RAM. I find it rare for the processor to go bad, I don't over clock and the case is always kept clean of most dust. Now the RAM is the only one left, unless the Motherboard could also be going bad!

Thankyou very much for your help. I really hope memtest shows that the RAM is going bad so that I can finally stop this hunting on what is causing my computer to have problems. I'll give a report on the results tomarrow as I leave the scan running overnight.

 

[zigzag3143]

If it works on safe mode but not a normal boot chances are it is a driver conflict/corruption.

For this situation you need to run 2 tests. One to test the ram (memtest) and one to find the mis-behaving driver.





Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[Libram]

It's storming at my house tonight, so I'm not sure if the power will cut out or not during the middle of the scan :=[

 

[Libram]

Ok, so I ran the memtest for a short period of time since the power was cutting off from the storm.
For three hours and it wouldn't do anything but sit on 80% and not complete a single pass.... Is there something wrong if it sits like this or is it supposed to take forever like this?
At a rate of 3+ hours and not a single pass for me, I can't see how some people managed 7 passes in a 8 hours time period...

Edit: There is still a blinking cursor from memtest, but the keyboard doesn't respond to exit the scan so I have to shut it down by the button.

Pass:80%
Test:7%
Sits on this for hours =/

Also, what does it mean if the computer freezes on the welcome screen after logging in and makes a endless beep from inside the computer? I think a endless beep ment a memory error right?

 

[writhziden]

May very well be the memory is bad. How many modules do you have? Can you run one module at a time and run Memtest86+ on each?

 

[Libram]

4 modules. I got to scan them with memtest again since it wasn't storming out last night this time. The scan was able to complete 8 passes without a single Error found.

I removed the graphics card to see if any help would come from that (perhaps the PSU could have been failing, to the GPU to.) Since the computer still froze up without the GPU, i'm guessing it was neither, since the PSU had all the head room in the world without a graphics card to suck it all away.

I guess that this could be a defective motherboard, or cpu?
I can' see how the freezing and crashing is still happening, even to the fresh install of Windows 7 with a new hard drive. My only guess is that it is a hardware problem. I scanned the hard drive a number of times for defects, but all of the scans showed up as a pass to. The registry is also in good shape and there is still plenty of room to be used on the hard drive.

Edit: I love you avatar Writhziden!

I have no start up programs now, running on clean boot. Updated everything that would require it. Uninstalled and re-installed programs, and then also uninstalled and re-installed Windows 7.

 

[James7679]

Libram, as ZigZag has stated, you need to run driver verifier.

 

[writhziden]

Alright, let us know how the clean boot goes.

Also, I am curious, what do you mean by this:

The registry is also in good shape...

I should re-iterate that the problem still could be memory. Memtest86+ is not fool proof and has been known not to catch bad modules from time to time. I see that you have 3 GB of RAM. What RAM configuration do you have, i.e. one 1 GB and one 2 GB module, three 1 GB modules?

• 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.

 

[Libram]

Alright, let us know how the clean boot goes.

Also, I am curious, what do you mean by this:

The registry is also in good shape...

[/QUOTE/

Means that there are no errors on the registry.

I should re-iterate that the problem still could be memory. Memtest86+ is not fool proof and has been known not to catch bad modules from time to time. I see that you have 3 GB of RAM. What RAM configuration do you have, i.e. one 1 GB and one 2 GB module, three 1 GB modules?

• 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.

The RAM is DDR2 and two sticks are a strange number like 512MB (I don't remember exactly) and the other two are another crazy number I can't remember, but they are also the same number. They are stock with the PC.

I would run Driver Verifier, but my Restore feature isn't working on the PC. I create a restore point, but the motherboard option for recovering doesn't work and trying to recover via Windows 7 OEM Disc doesn't find a recovery file.
Is there a way I can set up a recovery feature that my BIOS would recognize instead of ignore?
(I'm looking into creating a Windows back up partition similar to the HP Factory Image portion that comes on HP machines)

EDIT: Nvm, I figured it out. Running the driver verifier now

 

[writhziden]

The question I was trying to ask is: How do you know the registry is clean? Are you using software to clean it?

Also, why was CPU-Z not run to post screenshots? That information would be helpful...

 

[Libram]

The question I was trying to ask is: How do you know the registry is clean? Are you using software to clean it?

It only finds dead path from uninstalled programs. It doesn't find corruptions. Using ccleaner, also I have ONLY used it twice after the computers freezing problems have returned. I don't like using it much, since their solution is to always remove the error instead of fixing it.

Also, why was CPU-Z not run to post screenshots? That information would be helpful...

Sorry, I forgot to include those. I don't know which you are looking for, so I uploaded them all if that is not a problem
Also driver verifier is still running. So far there hasn't been a crash/lockup yet.

Also found the slots in CPU Z: In slot one that RAM chip is 1024MB: Slot 2 is 512MB: Slot 3 is 1024MB: Slot 4 is 512MB. All four chips are clocked the same.

 

[writhziden]

Sounds like you have mix and match RAM. Try running with the two 512s removed. Before doing so, upload a screenshot of all four slots through the SPD tab of CPU-Z. In CPU-Z's SPD tab, there is a dropdown list in the upper left corner under Memory Slot Selection so you can see each RAM module installed. That information would be helpful.

Once you have uploaded the information for each slot, remove the two 512 MB modules. Avoid Static Damage to Your PC when swapping out modules.

 

[Libram]

Ok. I will have to keep the computer turned of for a few hours before re-booting it since it only tends to crash after its been left off over long extended periods of time. Turning it off and back on a few minutes later doesn't seem to bring about any crashing.
I'll boot it back up tomorrow with just two sticks.

 

[Libram]

So far there hasn't been a freeze up yet. I'll give it a week before I decide if it was the RAM or not.

 

[writhziden]

Fair enough. Let us know how the system responds over the next week.

 

[Libram]

So just this morning my computer finally freezes. It was only on for about five minutes after bringing it out of hibernation. It was followed by a infinite beep this time from the motherboard to.
I turn it off and kept it off for a few seconds, then switched it back on. It froze up again a few minutes later, so I switched it off. This time it instantly turns its self back on as soon as I let my finger off the power button, but nothing loads, not even the BIOS.
A third time I switch it off, this time from the small switch on the back of my power supply, to keep it from turning its self back on like last time. I keep it off a few seconds and switch it back on and so far its runny as normal again.

I gave it more then a week, like I said in my post above
So i'm going to buy some RAM to see if anything works out. Does anyone know a 'good' brand of RAM for my motherboard?

Here are the exact specs from the P LB Benicia Memory upgrade specs:

Dual channel memory architecture
Four 240-pin DDR2 DIMM sockets
Supported DIMM types:
PC2-5300 (667 MHz)
PC2-6400 (800 MHz)
Non-ECC memory only, unbuffered
Supports 2GB DDR2 DIMMs
Supports up to 8 GB on 64 bit PCs
Supports up to 4 GB* on 32 bit PCs
*32-bit operating systems cannot address a full 4.0 GB of memory.

You can click this link for more information on my motherboard.

Edit: Was thinking of getting G.SKILL 4GB (2x2GB) DDR2.