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 from a clean install - re-installed 3+ times... still BSOD

23 Oct 2013   #1

Windows 7 Ultimate x64
BSOD from a clean install - re-installed 3+ times... still BSOD

Hi - I would really appreciate it if someone can shed some light on my BSOD, it is driving me completely nuts.

I decided to re-install my Windows 7 because I have started getting some random BSOD (not too often). When I did it the first time, I forgot to install the drivers from Asrock for HDD, and ended up corrupting my 4TB drive (because it was really only seeing 1.7TB, so all the data ended up getting messed up). Before my second re-install, I realized that my HDD got corrupted and thought that was causing the issues for the BSOD.

I reformatted the data drive, but still kept on getting the BSOD. I also swapped out the rams with a bunch of Corsair XMS3's which I had on the side. I ran both of these (GSkills and XMS3s) through 12+ hours of memtest and no issues.

On the 3rd re-format, I installed all the drivers and thought all the problems were fixed when I ran Prime 95 for 12 hours straight and had no issues. However, when I started copying data back to my 4TB from my NAS, I started getting BSOD. I swapped out my 4TB with an old 3TB data drive, and I am still getting BSOD. I have also tried bumping my voltage up from 1.5 to 1.535v for the memory, but that doesn't seem to help.

If anyone can take a look at my BSOD dumps and shed some light, I would really appreciate it! Many thanks!

My System SpecsSystem Spec
24 Oct 2013   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Also, is it a must to RAID a 500 GB HDD?
My System SpecsSystem Spec
24 Oct 2013   #3

Windows 7 Ultimate x64

Arc - thank you for the response. I did run each of the memory sticks through 12+ hours of memtest. To be completely honest, when I first ran Memtest on GSkill, within 5 minutes, I got tons of errors and reds, so I pulled out the 4 sticks and replaced them with the Corsair XMS3s and went through the following steps:

1) Ran Memtest on Corsair XMS3 for 12+ hours overnight, no errors.
2) Reinstalled W7 x64 Ultimate on Raid 0 Samsung (240x2 = 480GB)
3) Reinstalled all the drivers and rand Windows update until there is no further updates
4) Format 4TB (long format) - got BSOD

Initially that led me to believe that the 4TB was the culprit, but I took it out and replace it with another 3TB data drive (the old one that 4TB replaced) and still got BSOD.

Could it be the memory controller on the 3570k CPU or the northbridge/southbridge on the Asrock Z77 going bad?? I had this build (Asrock Z77-Extreme 4, 3570K, GSkill, XFX 5850) for the past 15 months, and have ran the CPU at 4.3Ghz completely stable until the past couple of months.

I understand that theoretically, the BSOD could be a number of things, and usually I do lean towards bad ram, but if the BSOD persists after I swapped out the GSkills for the Corsairs, it leads me to believe that it is some other component (or potentially multiple components, which would really suck).

I haven't swapped out the System drive b/c I don't have spare SSDs to do a clean Windows install, but have re-build the Raid 0 drive (probably doesn't do anything if the drives are bad).

The strange thing is that last night it didn't crash for over 6 hours, and sometimes it crashes when I am copying data back to the data drive in the matter of minutes.
My System SpecsSystem Spec

24 Oct 2013   #4

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

If you disable RAID in the BIOS and perform another clean install with AHCI mode, it will be easier to narrow the situation down. RST is problematic, and asmedia driver (as far as I can remember from my last look at your data) are outdated.

If you use mixed RAM, the possibility of RAM malfunction is always there. Use only one type of RAM. Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

It is a RAM, a bad RAM.

But if you have got a result like that:

It is a motherboard issue. The particular slot is bad.
My System SpecsSystem Spec
24 Oct 2013   #5

Windows 7 Ultimate x64

Thank you. I really appreciate the insight. So I think based on what you are saying and what I think I have done so far, the error is coming either from a) RAM/memory controller or b) drivers for the storage or drivers for other items.

a) I am guessing it's not coming from the RAM because I have used two separate sets of RAM (4 sticks of Corsair, then 4 sticks of GSkills, on separate occasions). I tested these RAMs separately (4 sticks of Corsairs only, for 12+ hours, got BSOD after Memtest came out clean. Then 4 sticks of GSkills, 12+ hours of no errors, booted into Windows, then getting BSOD)

If all the dumpfile is indicating it could be the memory, I am more inclined to think it's the memory controller or the actual DIMM slot (I can test the DIMM slot by running non-dual channel, putting only 1 memory in at a time), but deep down, I am hoping it's from a driver :).

I believe this is the order that I installed the RST Driver are as follows:

1) Installed the RST driver from Asrock dated 1/29/2013
2) Updated with Intel's RST dated 8/8/2013 from Intel's website

On the Asmedia, do you think it's the SATA3 or the USB3.0 driver that is not the newest version? I installed all the "drivers" from this page, but nothing from the "utilities" section.

ASRock > Z77 Extreme4

Thanks for your help!
My System SpecsSystem Spec
24 Oct 2013   #6

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

A "memory corruption" or "memory management" BSOD must not to cause by physical RAM, but if memtest shows errors, then it is to take care of, for sure.

IRST (and specially RAID) fails, every off and on. If a kernel mode driver passes bad information to the memory, the BSOD will accept it as memory corruption, as good as physical RAM. That is why I wanted you to see the situation in without IRST installed condition; but that is not possible in RAID setup present.

As per this page (it is not any official site at all, just a collection of drivers), the Asmedia drivers are certainly not up-to-date. But asmedia sata drivers are not very fail prone.

I would like to suggest you to go for one more clean reinstall, but with IRST/RAID disabled in the BIOS, and on the AHCI mode using the system native AHCI driver msahci.sys. It will rule out the chance of a storage driver passing bad memory information. Then, if it is BSODing still, we know where we need to concentrate :)

In order to get a perfect re-install which will maximize the native performance of windows, follow Clean Reinstall - Factory OEM Windows 7. It works similarly good for retail.
My System SpecsSystem Spec
31 Oct 2013   #7

Windows 7 Ultimate x64

Arc - thank you again for all your help! I really didn't want to re-install the Windows as it is quite consuming, so here are the steps that I followed:

1) Updated the Asmedia drivers (SATA & USB)
2) Re-tested the memory for 7+ passes in memtest - no error
3) Ran prime95 with overclock for 12+ hours, no error
4) Re-formatted the 4TB hard drive unchecking quick format - no error!
5) Copied everything back to the 4TB, no BSOD or any errors!!!

Thank you for helping me find out the root causes. May I ask how you go about to read the batch dump file and to determine that the asmedia drivers are outdated?? Thanks again for all your help!
My System SpecsSystem Spec
01 Nov 2013   #8

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

To read the dump data, follow this guide ..... Debugging A BSOD - My way.

Let the dump load at first. Wait for the first break point. Then verbose load asmedia sata driver. The command will be .....
lmvm asahci64
The outcome will look like ....
start             end                 module name
fffff880`013af000 fffff880`013be000   asahci64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\asahci64.sys
    Image name: asahci64.sys
    Timestamp:        Wed Sep 21 15:12:57 2011 (4E79B1A1)
    CheckSum:         00010EE2
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
You need to see the "timestamp" line.
My System SpecsSystem Spec

 BSOD from a clean install - re-installed 3+ times... still BSOD

Thread Tools

Similar help and support threads
Thread Forum
BSOD random times, even on clean re-install
Hi, I was getting random BSODs (for ex, playing games, file transfers, watching movies on browser stream etc). I did the uninstalls of some programs, updated some drivers etc, but it did not help. I unplugged D drive (as I ran out of space and had to install some stuff in D drive, and I thought...
BSOD Help and Support
BSOD Clean install @ random Times
I just recently did a clean install on my new ssd. I have BSOD twice since the install and did not previously. Windows updates are now all up to date but where not before this BSOD. Any glaring issues is what I was wondering and If I should just wait and see if it happens again now that the system...
BSOD Help and Support
BSOD on clean install at random times
Having had various problems on my pc that gave me crashes and ending up with no sound i decided to do a clean install, everyting seemd to work ok but i have now had a couple of random BSOD. Can somebody look at my crash log and advise please. Thanks for looking
BSOD Help and Support
BSOD clean install after SSD installed
I have been reading through the forum trying to get help on my BSOD error that has been happening recently after doing a clean install of Win7 Home 64 bit. I did this bc of adding a SSD to my system and my recovery discs wouldn't work since it detected that it was a new configuration. Here are a...
BSOD Help and Support
BSOD at random times, after clean install W7 Pro 64 BCCode 1e
Hey yall, I really appreciate anyone looking at this first of all its got me stumped. So I recently did a clean install of W7 Pro 64 on my Dell XPS 1330... Everything worked out great, except the rig will crash every 30 minutes or so... I got this log from windows: Problem signature: ...
BSOD Help and Support

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 15:22.
Twitter Facebook Google+