Solved BSOD even after fresh install (Windows Update may be the cause)

[Mattster]

I've built a new system and after about a week of it operating it has decided to be a complete douche to me for some unknown reason. Everything was okay until I installed the SSD (so I was aware of anyway, the computer belongs to my sister and she never told me when the system used to crash, so it could have crashed before the SSD). Anyways, when I was made aware of the computer issue I checked the Event Viewer logs to see what was wrong and tehre was loads of Kernal Power issues. So I could only assume that maybe the old PSU was not good enough for all the cool new hardware, so I bought a new PSU; although the problem still persisted.

I've had more chance to observe the system today and determine what is going on. I've removed 2 HDDs from the system and kept the SSD in (I ran a health check of the SSD on my own system, and it reported it to be perfectly fine). Anyways, reformatted the SSD and everything was going well after installation. After give the OS a lovely 150 updates it BSOD on me. I read a log which suggested there was bad drivers, so I just assumed the ethernet drivers I had to manually install were incorrect (even though they worked fine before SSD upgrade). So I went to a wireless connection for the time being, did everything all over again and got the same result. At this point I determine Windows Update must be giving me grief. I installed security updates only at first, and everything was going fine. Then installed SP1, and after maybe the odd 3 more updates after SP1 it is now doing the entire damn thing all over again with crashing.

If I load Windows Update and either search for updates or implement Framwork 4 update it will BSOD, if I leave the system idle for 5 minutes after booting, it will BSOD. And it will do this no matter what I do. So I am completely stumped and would hopefully like to find some help from anyone before I start to blame the hardware. Also as a side note (as I love Safe Mode) it hasn't crashed at all in Safe Mode, so it's obvious to me it must be something that loads with the OS.

I've attached the logs that you need (hopefully).

 

[Arc]

Hello Mattster.

Scan the system for possible virus infection. It is needed, despite of it being a clean reinstall.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Roll back to your display driver to an earlier one.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your Intel Graphics Driver.
• Download an immediate older version form Intel Download Center and install it.

Install Service pack 1.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

Let us know the results. And, next time upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[Mattster]

Thanks for the aid, Arc.

I've ran both the Anti-root kit and Windows Defender Offline, both have reported a clean system and no issues at all; although an error would have been nice at least I could have been closer to a fix.

I'm unable to run Driver Fusion as it requires .NET Framework 4, and every time I even attempt to touch that, the system crashes or BSOD's; this even includes installing it from Windows Update and downloading the installer pack from their site. I'm even getting issues with Firefox now (still in the process of downgrading my graphics drivers as you've mentioned). Here's an msinfo32 report as you requested.

EDIT: Also if this can prove any help, even when in Safe Mode I've just tried to install Java and it just BSOD.

 

[Arc]

Can you update the Edimax nLite Wireless USB Adapter driver?

fffff880`02478000 fffff880`02570000   netr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\netr28ux.sys
[COLOR=Red]    Image name: netr28ux.sys
    Timestamp:        Fri Jul 03 15:01:38 2009[/COLOR] (4A4DCFFA)
    CheckSum:         000FE3BC
    ImageSize:        000F8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It should be the place to get the update: MediaTek - Downloads Windows.

If you fail to update it; or if the computer crashes even after the update, try a different adapter. And if the crashes still occur with a different adapter with a latest driver, we have to take some different way to troubleshoot.

 

[Kaktussoft]

Why did you do a clean install instead of migrating to SSD?
Not a solution to your question but I just want to know.

Can you still boot to old win7 on harddisk and gives it the same problems?

 

[Mattster]

Can you update the Edimax nLite Wireless USB Adapter driver?

fffff880`02478000 fffff880`02570000   netr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\netr28ux.sys
[COLOR=Red]    Image name: netr28ux.sys
    Timestamp:        Fri Jul 03 15:01:38 2009[/COLOR] (4A4DCFFA)
    CheckSum:         000FE3BC
    ImageSize:        000F8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It should be the place to get the update: MediaTek - Downloads Windows.

If you fail to update it; or if the computer crashes even after the update, try a different adapter. And if the crashes still occur with a different adapter with a latest driver, we have to take some different way to troubleshoot.

Oh yes, I moved from the ethernet port to the wireless adapter because I thought the ethernet was causing the problem. Wireless is perfectly fine. It's just when I install stuff like .NET Framework, Java, or update after Windows SP1 that the system just constantly gives BSOD. And it provides different error codes each time.

Why did you do a clean install instead of migrating to SSD?
Not a solution to your question but I just want to know.

Can you still boot to old win7 on harddisk and gives it the same problems?

It's just a habit I've developed, if I'm required to move the OS then I'd like to just have a fresh install. As for the old Windows 7 partition on the HDD, they have been removed. One of the HDD is near on dead, and the 2nd HDD I don't really trust. I have however attempted the same methods on them as I have with the SSD. Which is just like fresh install and update everything back to the latest updates and such, and I still get the same issue. So I can only assume it will be something hardware related. I'll get back running PC check and see if that kicks anything out.

 

[Arc]

Can you update the Edimax nLite Wireless USB Adapter driver?

fffff880`02478000 fffff880`02570000   netr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\netr28ux.sys
[COLOR=Red]    Image name: netr28ux.sys
    Timestamp:        Fri Jul 03 15:01:38 2009[/COLOR] (4A4DCFFA)
    CheckSum:         000FE3BC
    ImageSize:        000F8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It should be the place to get the update: MediaTek - Downloads Windows.

If you fail to update it; or if the computer crashes even after the update, try a different adapter. And if the crashes still occur with a different adapter with a latest driver, we have to take some different way to troubleshoot.

Oh yes, I moved from the ethernet port to the wireless adapter because I thought the ethernet was causing the problem. Wireless is perfectly fine. It's just when I install stuff like .NET Framework, Java, or update after Windows SP1 that the system just constantly gives BSOD. And it provides different error codes each time.

Update the driver. As far as the other things of the system is old, it is compatible with those; but if the other elements got updated, it fails to keep up.

 

[Mattster]

I've had no luck what so ever with fixing this system. I removed the SSD to see if that was causing any issues and tested it on my system, the results was nothing was wrong. So I tried an old HDD for the system that is causing me problems, and as slow as it is (due to the HDD) there's little BSOD's although they still exist; even when a fresh install. I ended up downloading an application called "Who's Crashed" as I found it in someone else's post and it seems to give me a better idea as to what could possibly be the problem. As of right now I've removed one of my memory modules from the system, and updating everything from scratch again (since the system refused to load without the 2nd RAM card in). I'll report back with any new BSOD's or errors once they've occurred.

 

[Arc]

Have you Tried a newer network adapter?

Apparently the issue is not related with SSD or HDD. And .net framework is the most difficult thing to download via windows update. You may try an external source. Download .NET Framework Version 4.5 - FileHippo.com

Which program we do use gives much closar look at a dump than wh crashed. Download and Install Debugging Tools for Windows

 

[Mattster]

Thanks for the help Arc, I've finally found the source of my problems now. One of the memory modules is faulty, even though memtest reported back my memory was perfectly fine, one of the modules is actually causing the BSOD issues. I've removed the module causing the issue and all the BSOD's are gone now.

 

[Arc]

Thanks for the help Arc, I've finally found the source of my problems now. One of the memory modules is faulty, even though memtest reported back my memory was perfectly fine, one of the modules is actually causing the BSOD issues. I've removed the module causing the issue and all the BSOD's are gone now.

Very nice and very interesting!

How did you come to know ?

 

[Mattster]

To be honest, it was just luck really. I mean, I trusted memtest to give me accurate results but it was such a liar to me. I read the reports from Who Crashed, and it was always referring to memory but was always assuring me it was a software issue, not hardware. Anyway, I was looking around the internet for similar instances of this error code and someone mentioned memory, and since Who Crashed was mentioning memory as well I though I might as well check. Removed one, crash. Removed that, and replaced with the other.. Worked fine. Then just went through the steady process of updating everything all over again (thank god I have an unlimited download package lol) then put the other memory module back in, crashed. So yeah, was just pure luck if anything.