New
#1
BSOD even after fresh install (Windows Update may be the cause)
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).