Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD Before and After Clean Win7 Install

29 Jan 2013   #11

Windows 7 Home Premium 64bit
 
 

Okay, thanks. Disk check also reported no problems.

My System SpecsSystem Spec
29 Jan 2013   #12

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Till we wait for a reply there's something more we can do:

Upload a screenshot of your hard disk using CrystalDiskInfo and Summary tab using Speccy:Use verifier for 36 hours. Then send us the BSOD reports

Driver Verifier
Quote:
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/Windows 7 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 [/B][B]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.
Driver Verifier - Enable and Disable

Using Driver Verifier to identify issues with Windows drivers for advanced users
Driver Verifier - BSOD related
Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
30 Jan 2013   #13

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

In addition to the instructions given by Koolkat for Driver Verifier, you also do not want to select 'Force Pending I/O Requests' and 'IRP Logging' checks. The former often causes false positives and is only designed to be operated by the driver developer, and the latter is worthless.

Once it is setup, restart the system and let the system crash some and then send us the crashdumps. It may cause a boot loop like what Koolkat hinted too, which you'll want to enter Safe Mode to turn off Driver Verifier from there then enter normal Windows and upload us the new crashdumps.
My System SpecsSystem Spec
.


13 Feb 2013   #14

Windows 7 Home Premium 64bit
 
 

Sorry, I know it's been a while. A family emergency came up and I barely even thought about or used my laptop. I'm going to attach the CrystalDiskInfo and Speccy screenshots you asked for, as well as three crash dumps that I got since I've started using my laptop again. I'll get started on the Driver Verifier stuff.
My System SpecsSystem Spec
14 Feb 2013   #15

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

If I'm reading the values correctly - and these are unusually screwy numbers I'm looking at - there's some items that are particularly disconcerting, such as CRC errors, all for your SSD drive. Again, these may just be vendor-established values that I am not interpreting correctly, but it does appear there to be some issues. The thing I would check for is your power and data cables hooked to your SSD and confirm that both ends of each are fastened correctly, since CRC errors especially represent an issue with cabling. If you have a spare data cable try that as well.

I'll await till you provide us crashdumps from Driver Verifier to continue investigating this, but there's a possibility the SSD may not be doing so hot, either by a problem internally, a cabling issue or a motherboard problem. Samsungs are currently top dog in terms of reliability (aside from their Sandforce controller drives, like all Sandforce drives) but there's still always the possibility of getting a dud. We'll want to continue looking into this further to verify this as the issue. However this does coincide with the fact that I/O during crashdump generation is suddenly halted due to some unforseen error or hangup.
My System SpecsSystem Spec
16 Feb 2013   #16

Windows 7 Home Premium 64bit
 
 

So I ran Driver Verifier for about two days. I had two crashes, but both times it never got to the BSOD and didn't create a dump. It would hang at a scrambled screen for like 10 min and then I would just hard shut down. I disabled Driver Verifier and got two more crashes that created dumps, so I'll attach those. Should I try Driver Verifier again?
My System SpecsSystem Spec
18 Feb 2013   #17

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Try it once more to make sure it wasn't coincidental. Otherwise, it's not going to make things easy for us without DV. However, I honestly don't think it'll help much anyways, since all your symptoms - including the scrambled hangs when DV is on - points finger at hardware issues.

I would recommend considering evaluation of your Samsung drive. Have you tried removing the drive entirely and running the system on a Windows installation on the other drive?
My System SpecsSystem Spec
18 Feb 2013   #18

Windows 7 Home Premium 64bit
 
 

Okay. Is there a way to determine what hardware is causing the problem? I've been monitoring the Samsung drive and the CRC error count has not gone up since I took that screenshot. Also, the Samsung drive is much newer than the WD drive and the WD drive is the original Windows installation drive that started having BSODs.
My System SpecsSystem Spec
19 Feb 2013   #19

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Well if that's the case then there shouldn't be anything to worry about the SSD drive. The CRC errors may just be something that's internally resolved. Still wouldn't hurt to refit the cables n stuff for it though just in case.

Aside from hardware diagnostic software and swapping hardware, there isn't really any sure measure of finding hardware problems. If the problem eludes the software diagnostics, then you have to end up swapping hardware through process of elimination to find the culprit.

The usual hardware testing I have people run through are mentioned below in the copypaste:


RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Blend; overnight (9+ hours) followed by Large FFTs 9+ hour run.
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

All of these are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the latest version of UBCD due to a bug. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get the system to crash during high load logging, that's even better. Last, make sure that when running Prime95 that you check temps during first 30 minutes or so to see if temps are stable. Prime95 runs very hot so be sure your cooling can handle it before letting it run extensively.
My System SpecsSystem Spec
23 Feb 2013   #20

Windows 7 Home Premium 64bit
 
 

So for the past 4 days I haven't gotten any BSOD, which was weird because I was getting 1-2 a day. Then today I got like 6. Also I reseated the cables for my SSD and HDD. I don't have any extra SATA cables to replace and see if that helps though. I ran memtest for many passes before, when I first posted here. Probably like 20+ passes of each stick in each slot without any errors. And I ran Seatools on my SSD and HDD and they passed without problems. I'll test with Prime95 and the HWInfo and get back to you. Also, let me know if you want the crash dumps I've gotten since last posting them.
My System SpecsSystem Spec
Reply

 BSOD Before and After Clean Win7 Install





Thread Tools



Similar help and support threads for2: BSOD Before and After Clean Win7 Install
Thread Forum
BSOD even after clean Win7 re-install BSOD Help and Support
Solved random BSOD clean win7 64bit install, need your help guys BSOD Help and Support
BSOD when trying to do clean install a Win7 ultimate 64bit BSOD Help and Support
Solved BSOD after completing clean install win7 64 BSOD Help and Support
Solved BSOD when attempting to clean install Win7 64bit Professional BSOD Help and Support
Win7 64bit BSOD - clean install BSOD Help and Support
Win7 7100 Clean Install - BSOD BAD_POOL_HEADER Installation & Setup

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:50 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33