BSOD occurs at random times right after logging on

[ConeSniper]

Hello, I would really appreciate some help with these random BSODs' I keep getting the system I just upgraded from originally using Vista home premium 32 bit to Windows 7 Home premium 64 bit, Yes I did wipe the hard drive and I have reinstalled the OS multiple times to try and navigate around this problem.


Specsrocessor: Intel Core I5-2500 3.3 GHZ
MOBO: ASUS P8H67-V
Ram: 4-gb Crucial (2x 2gb)
PSU: Antec 650 watt earthenwatts
HD:ST3360320AS ATA device 326 GB
OS: Windows 7 Home premium 64 bit, Brand new disk just got yesterday

Again any help would really be appreciated, The only reason I am able to post this is because my computer is currently in safe mode and even then it will eventually randomly BSOD on me...
Will post Dump files soon

 

[JMH]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[ConeSniper]

System info is in minidumps.zip file

 

[zigzag3143]

The most common reason for your crashes is pool corruption. In order to find which driver is mis-behaving please run driver verifier.


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

* If you have a Raid update its Driver.



Driver Verifer

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.

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

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JGriff2 & Usasma.

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


Using Driver Verifier (Windows Drivers)

 

[JMH]

FYI > It would be wise to update your system to SP1 as soon as possible.

Please run the System Update Readiness Tool (SURT) and then update to SP-1

32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details


Now update to SP-1

http://windows.microsoft.com/install Windows7 SP1

 

[ConeSniper]

I have tried updating to SP1 and such but the computer has bluescreened, everytime I try to install a windows update or something. In my latest attempt the only outside driver I installed was the ASUS motherboard Network Driver and it still bluescreened after about 10 minutes even in safe mode, For right now I have given up and reverted back to my Windows vista 32 bit home premium