BSOD at random times on fresh install

[romavictor]

I have reinstalled Win 7 (x64 SP1) about 5-6 times in the last day. Each time, with the basic install and no special software, except the audio and network drivers, which I got updated from the manufacturer, I get BSOD at various times for reasons unknown.
I am attaching the dump files as required.
System is an HP Pavilion 3 ghz, 8 gb RAM - ONE WEEK OLD.
I have a retail version of Win 7 Ultimate x64 that I'm using. Like I said, I've done clean installs over and over, reformatting the drive each time, and even with the basic, fresh install, I get BSOD.
Please help.

 

[zigzag3143]

I have reinstalled Win 7 (x64 SP1) about 5-6 times in the last day. Each time, with the basic install and no special software, except the audio and network drivers, which I got updated from the manufacturer, I get BSOD at various times for reasons unknown.
I am attaching the dump files as required.
System is an HP Pavilion 3 ghz, 8 gb RAM - ONE WEEK OLD.
I have a retail version of Win 7 Ultimate x64 that I'm using. Like I said, I've done clean installs over and over, reformatting the drive each time, and even with the basic, fresh install, I get BSOD.
Please help.

These crashes were caused by memory corruption (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!!!


1-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



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[romavictor]

thank you so much for your response, especially around the holidays.
here's the situation:
i ran the memory test from a USB two nights ago - 4 full passes and ZERO errors.
ran it today and got TONS of errors after 59 minutes.
i had driver verifier running for 24 hours straight, through this morning when i started the memory test, and everything worked fine.
then i installed my graphics card driver and it went BSOD almost right away, with driver verifier enabled. the graphics driver is the most updated version, downloaded directly from ATI and built for 64-bit Win 7. could this link back to the memtest errors?

here are my questions: with the errors in memtest, this means that there is faulty hardware. i have no problem sending it back and letting HP figure it out.
my second question is in regards to the OS. could the faulty memory have lead to all the BSOD's? i've been getting the 'memory management' BSOD, but others as well: pool_header, IRQL not less or equal, etc. could these be chalked up to memory/hardware problems?

now i throw in the win7 CD and i can't even get it to boot from the disk. says that an error occured while attempting to read the boot configuration data.
my hope is that this is all hardware based and that a simple motherboard and/or RAM fix will do the trick but i suspect there may be driver issues with the 64-bit OS.

thanks again for your help-

 

[zigzag3143]

You have two choices. To sweat it out yourself, or to rma it to hp. If I were you I would rma it as who knows if this portends the future.

 

[romavictor]

oh yes the RMA is in the works. gonna get sent back.
my main question that you might be able to answer is whether all BSOD's can be caused by faulty memory hardware.
the one's i've seen are: IRQL not less or equal, memory management, bad pool header, etc.
i guess i'm just wondering if i have to fight the driver-64bit-incompatibility battle once the compy comes back or this all could be due to RAM.

thanks again-

 

[zigzag3143]

oh yes the RMA is in the works. gonna get sent back.
my main question that you might be able to answer is whether all BSOD's can be caused by faulty memory hardware.
the one's i've seen are: IRQL not less or equal, memory management, bad pool header, etc.
i guess i'm just wondering if i have to fight the driver-64bit-incompatibility battle once the compy comes back or this all could be due to RAM.

thanks again-

Not all BSOD's can be caused by faulty ram. Some can be caused by software, some by configurations, etc. Could all be due to RAM, but only time will tell.