BSODs introduced with Clean Install of Win 7 Ultimate x64

[Holiday7]

Hello there!

I'm getting BSOD's on a freshly installed Win 7 Ultimate (x64), via disc. My system wasn't BSOD'ing before the clean install. I decided to do a clean re-install of Windows to avoid sorting through and manually clearing out junk on my HDD as it was near full.

I'm using the correct most up-to date drivers for my Chipset (nForce 780i), Graphics Card (GTX 570), Sound Card (Auzentech X-Fi Home Theater HD) and Wireless Network Card (Edimax EW-7728In). BIOS is up-to date also.

When I run 'sfc /scannow' it finds errors but cannot repair them. I've run it 10's of times now to no avail of repairing the corrupt files. I've also ran a chkdsk to Automatically Attempt to Fix Errors and Recover Bad Sectors and the report came back as having 0kb in Bad sectors so I believe it's safe to presume my HDD is fine and isn't the cause here.

Before I installed via disc, I tried installing my copy of Windows 7 via the USB Tool which I have used previously and I was also getting BSOD and this caused me to go ahead and try install via disc.

The last BSOD's I received were after the forced restart of installing my Audio drivers and then again right after using 'sfc /scannow' in the Command Prompt as an Administrator.

Attached are the necessary files?


Thanks for any help in advance!

 

[richc46]

You have given us only one BSOD report. Since these reports, at best, give little clues, I cannot guarantee that the hint given in your report is valid. In any case, it indicates memory corruption.
Take memtest
Guide to using Memtest86+ - Geeks to Go Forums
Scan each ram stick for 8 passes, using the same slot
Then
run all sticks for 8 passes.

 

[Holiday7]

Thanks for the reply, is there any way I can give you more information/dumps that might help?

I'll get onto running Memtest soon.

 

[richc46]

If it were me, I would take memtest, as that might work. If not, wait until you get a half dozen or so BSODs, then send the report. It should show all the BSODs. While accumulating the reports do not use anything like Ccleaner as that removes the error reports.

 

[Holiday7]

Okay will do, I'll report back with my findings.

I believe the last time I was on these forums was due to a previous faulty EVGA 780i FTW motherboard spitting out freezes and BSOD's. I think the ram slots (or how the board interacted with the memory) were faulty.

The RAM was fine as the sticks passed memtest in certain slots but not when others were populated - that and my issues completely disappeared with my second (yes second - EVGA are that rubbish) replacement.

I wouldn't be surprised if I'm facing the exact same issue as I do tend to have rubbish luck!

 

[richc46]

Probably is the same cause, test all slots

 

[Holiday7]

I've tested each RAM module in slot 0 on the board for at least 8 passes with 0 errors.

A test with all the slots populated for at least 8 passes also reveals 0 errors.

One minor thing to mention is that whilst testing each RAM module separately, one of the sticks caused my system not to post with an LED post code of 'C1' on my EVGA 780i FTW board. My manual noted this code with a name of 'Memory Presence' and a description of 'Base memory detect'. Once I re-seated it, my system operated nominally and it passed the memory test as mentioned above.

What now? Shall I keep trying to force some more blue screen reports? Is the invalidation of my OS files via the 'sfc /scannow' command nothing of any worry?

 

[richc46]

SFC Scan. When the scan finds errors that cannot be repaired the usual method to correct the problem is to make a repair install, if the problems are causing trouble with the computer. Can you give us a screen shot of your SFC report?
BSOD. Assuming that you did the test correctly the problem is not with memory. Try using the computer in safe mode for a while. Do you still get BSOD's. Do not rush this portion, your answer will determine the best route to take in an attempt to solve the problem.

 

[Holiday7]

I've attached a screenshot of the command results and the actual sfc log to this post.

There's no doubt I ran memtest86+ correctly, I've used it plenty of times before. I'll play about in safe mode although I'm limited in what I can actually do in that mode. Anything you recommend I can do that will put some load on my system to potentially induce BSODs in safe mode?

 

[richc46]

I checked your SFC report. The only way to resolve those problems is clean install or to try a repair install.
If you want information on how this is done just post. You will need an install DVD, however for either.
Regarding safe mode. Yes, you will be rather limited and probably bored while in safe mode. Lets go this way. Try a clean boot, run it in clean boot mode. Do what you normally do to cause the BSODs. If you get BSODS, try and get a few and send the report. If you do not get BSOD, slowly reactivate the software disabled by the clean boot, after reactivating each one, take your time, use the machine, if no BSODS, activate another software, till we find the cause.
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[Holiday7]

Thanks for your assistance so far Richard.

I mentioned in my first post I originally re-installed my OS via the USB Tool. When I was getting sfc errors and blue screens on that installation I correctly followed a repair install under the sevenforums guide. However this didn't fix my errors. I might try yet another clean install as the repair took just as long, if not longer than a clean install does. After the install I'll follow your clean boot advice and let you know how I get on.

I know my OS installation image from Microsoft/Digital River which I burned to disc/used with the USB Tool is fine as my friend had a replacement HDD sent from Western Digital and asked me to reinstall Windows for him (he isn't comfortable with this computer stuff). He also uses Win 7 Ultimate (x64), I used the same disc to install Windows onto his new drive with his license and it works like a charm and validates perfectly when the System File Checker is ran.

 

[richc46]

Ill be honest, the test indicated a RAM problem, which you tested and found the RAM to be OK. I am leaning toward a hardware problem. If the computer does not work well with the clean boot, we have to start testing the hardware components.