Blue screens after fresh reinstall?!

Flame Soulis

Honorable
May 11, 2013
35
0
10,540
So I was origionally having an issue where Windows decided it was a great idea to install updates during a brown out (with a UPS) and ran out of time. After that, I started to have crashes caused by ntoskrnl.exe in most crashes. I had this problem before so I figured "Okay, repair console, replace, rinse and repeat." Only this didn't work.

One backup and fresh reinstall later, I let updates go by after getting all drivers back on. All is well and my system didn't show any issues what so ever. I decided to do a reboot after the system started to slow down with I/O (explorer being slower than molasis, file operations taking longer than they should, etc), and upon doing so, I am greeted with the same issue that made me have to reinstall in the first place!

So now I'm at a loss. I'm assuming some update that Microsoft released is causing a conflict or is just plain buggy and every time I get said update, it causes mayhem on my system.

Notes:
- Yes I ran a memory check. It ran fine after 4 passes on a normal test, but the extended one froze at 21%.
- I am using Windows 7 Professional 64-bit
- Yes, I have a legit key...
- Safe mode = perfectly fine
- The crash ALWAYS seems to happen AFTER a minute from logging in

Software on system:
Trend Micro, Spybot v2, DisplayFusion, MSI Afterburner, MSI Live Update 5, Steam, Waterfox, Bitcoin-qt, IrfanView, Skype, Thunderbird, Dropbox, K-Lite Codec Pack, PDFCreator, Fences.

I'll try to upload the dmps once I get them off my PC.
 
Solution
a good thing you find out what was wrong so your answer could help someone else with the same issue ,maybe the clip was not seated all the way to the memory stick slot. time for computing now .

Flame Soulis

Honorable
May 11, 2013
35
0
10,540
Bah... no upload feature (oh well). Here's the reports instead:

==================================================
Dump File : 060113-24679-01.dmp
Crash Time : 6/1/2013 2:47:12 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`04cbb934
Parameter 3 : fffff880`033163f8
Parameter 4 : fffff880`03315c50
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+45bdaa
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : nvlddmkm.sys+453934
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060113-24679-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,504
==================================================

And...

==================================================
Dump File : 060113-22245-01.dmp
Crash Time : 6/1/2013 2:45:21 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`5090a090
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`0017657e
Parameter 4 : 00000000`00000005
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+b3b1b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060113-22245-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,584
==================================================

 

Flame Soulis

Honorable
May 11, 2013
35
0
10,540
What is strange is if I set startup to clear, things seem to start up okay. I started having the same issue, but this time with MEMORY_MANAGEMENT (1A) when I was checking stuff and KMODE_EXCEPTION_NOT_HANDLED (1E) if I let startup run its own business. Safemode seems to be running okay every time, so I'm not sure if this is a conflict or something else.

I'll try running with each stick seperately and see what happens over night.

As for the latest crashes, I've seen one crash with ataport.sys and another with tcpip.sys before I clear the start up (of course, also with ntoskrnl.exe+6d5fe). The MEMORY_MANAGEMENT one is +ed32.

These latest crashes are after Microsoft snuck an update on me even though I told it to NOT install any. Even after a system restore, it still happens...
 

Flame Soulis

Honorable
May 11, 2013
35
0
10,540
I'm embarrassed to state this, but it turns out a stick was... loose. After I reseated all 4 sticks, it ended up working fine afterwards. In fact, several problems I had before also went away (like Bitcoin-qt not syncing).

I'm not sure how any got loose but I guess it can just happen sometimes.