BSOD after Win7 Updates - Pls Help

Hey guys. So I finally got the Win7 Ultimate that is supposed to come with my R3 and installed it without a problem. I also completed installing all drivers.

Last night, I found a notification for Windows Update in the taskbar and went for it. Its about 14 updates of KB##### series.

After completing the download and installation, it asked for a reboot so I did. Before entering the Windows screen from a reboot, I suddenly got BSOD.

When it was trying to restart, it says Windows cant start and needs to be repaired. So I followed and clicked automatic repair, waited long and finally windows cant be repaired automatically and shut down.

I tried to restart again and windows started properly but it all went back to the original setup (big screen icons, default log-on screen, default log-on pics). Basically the config after a fresh install but all drivers I installed previously are OK. So I just reconfigured again to what I wanted except for changing the logon screen. I was thinking maybe its creating the problem.

So from this point and because of what happened, I tried to create a disc image but after completion, I cant find the image in the 2nd drive. I tried again and result it the same. I was originally planning to create a system image after update but I'm getting BSOD.

I'm not updating now because I dont want to get another BSOD. What do you think is the problem guys. BSOD said failure to load windows due to hardware change but I didn't change anything. TIA everyone.

 

Download whocrashed and post the log.

 

I had a similar problem, one of my ram sticks was defective. Took it out and no more BSOD.

Thats what worked for me, but take a BSOD Dump and the gurus (not me) here will check it out.

 

I was trying to open the dump file so I can show it here but I dont have a program to open it . Ok, I will download whocrashed and post it here when I get home from work. Thanks guys.

 

Zip and upload your dump files from C:\Windows\Minidump and I'll analyze them for you.

 

Was tied up last night and wasn't able to check this. I'll do this tonight and upload the zip file here.
Thanks.

Edit:
Here is my dumpfile folder. I only have 1 file inside though.

Edit2:
I DL'ed whocrashed and here's the report:


Thanks in advance for those who can help me understand this and solve the problem.

 

The dump file you uploaded points to ntkrnlmp.exe as the faulting module. This makes it a little hard to troubleshoot. ntkrnlmp stands for NT KeRNeL, Multi-Processor version. It's pretty much the central file for the OS. Most of the time a BSOD blamed on ntkrnlmp is a result of the file processing bad data. As such, it's difficult to diagnose with just one dump file.
Please run a system file checker by following option 2 here: SFC /SCANNOW Command - System File Checker.

If you get errors, keep running the scan until no errors pop up. If no errors pop up or you continue to get BSOD despite the errors being fixed by the scan, please enable Driver Verifier by following instructions here: [url='http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html"]Using Driver Verifier to identify issues with Drivers[/url]. With Driver Verifier enabled, continue to use your system normally. If/when the verifier detects a faulty driver, it will trigger a BSOD and the resulting dump will list all your drivers including the faulty driver. Please then upload that dump file. It should give us more insight into the issue.
Please also read this regarding Driver Verifier: DRIVER VERIFIER . It is important that you create a system restore point.

 

Thanks a lot. I'll follow this process and will update this thread for any development.

 

My pleasure
Do keep us updated.

 

I got 3 BSODs again today. Actually I did a fresh install again about 2 days ago just to be sure that system will be clean of anything. I noticed I am getting BSOD when I'm running on battery supply.

After this 3 BSODs, I run the sfc scannow command and it says "Windows Resource Protection did not find any integrity violation."

I attached the zip file of the minidump again. I hope you can look at it if you have time.

Thanks.

 

The dump from May 6th points to RtsPStor.sys which is your Realtek card reader driver. Please try reinstalling them.

The other 2 BSOD's were a 0xA and a 0x1E both pointing to ntkrnlmp.exe as the faulting driver. I'm starting to suspect a hardware problem please start with a RAM test with memtest. Instructions here: RAM - Test with Memtest86+. Please run at least 7 passes (overnight is best).

 

Thanks again. I'll do the above tonight and will update this thread.

Edit:
When I turn on the laptop today, I got another BSOD and then it went to windows but there is a message "no supported hardware" something like that for GPU. When I checked device manager, my 580M is not detected so I reboot again.
From reboot, it asked for repair and everything went fine again.
Its always like this since I installed W7 Ultimate from Dell. It will prompt the it wasn't shutdown properly even if it did then BSOD then ask for repair and then it will function properly like nothing happened.

BTW - im just about to uninstall the media card reader, I found a newer one in realtek website. What do you think about the GPU non-detection? I've seen this a couple of times since I got this GPU. (Dell initially gave me 560M instead of 580M so they replaced it. Same as W7 Home Premium instead of Ultimate then they sent me the new DVD for Ultimate)

 

*bump*

Please let me know if its not allowed to bump. Sorry if it isn't. I just want to get some response about the occasional non-detection of my GPU as stated above.
If somebody have experienced it and how they resolve it.
Thanks.

Edit:
BTW, aznpos531, I run memtest overnight and completed the test without errors. I haven't have any BSOD since I updated the memory card driver also.

 

I'm not 100% sure about the the GPU not being detected. It could be anything from it not being seated properly to a software/driver problem or the card maybe on its way out. Which version of the nVidia drivers are you running right now?

If you can, please upload the dump file from your latest BSOD. Also, make sure you disable Driver Verifier if you haven't already.

 

I'm running the latest, 296.1. There is a story behind my GPU. I got the laptop in April 16 with a 560M instead of my order with 580M, Dell sent me a new 580M on April 19 and technician installed it. Its a brandnew GPU, its still sealed in the box and the case.

I guess if I get another detection error, I'll probably try to re-seat and repaste it. I dont have any problem with temp though, my all time max is just 67C.

I'll post the dumpfile when I get home. Thanks again.

 

Glad to hear that the BSOD's seem to have subsided for now. Keep me updated on any new BSOD's and upload the dumps as they come.

Yea, I guess try reseating the card with a repaste if the issue comes up again.
And I'll analyze your latest dump when you upload it.

 

Here it is.
Thanks.

 

Just analyzed your latest dump and it's a 0xA IRQL_NOT_LESS_OR_EQUAL stop caused by Ak27x64.sys which is your Bigfoot Killer Wireless adapter driver. I've seen several instances where this driver caused problems. See if there's a newer version and try reinstalling with the new driver. If a newer version isn't available, try reinstalling with the current version.

 

Thanks. I'll check it tonight. Also, since I've done a fresh install, I haven't updated W7 from windows update. Because the last time I did update, that's the 1st time I got BSOD. That's the last reason why I did a fresh install again.

I checked and I have a lot of pending updates. Should I run it or just leave it as is?

 

I generally find that keeping up to date with the Windows update is a good thing and in some cases solves some BSOD's. One such update for Windows 7 is SP1.
In your case I would keep updating until there are no more updates and see if the BSOD's pop up again.

 

Hey bro. I haven't tried reinstalling the Killer driver since I haven't had any BSOD again since the last I sent you. That's why I am also hesitant to run Windows Update because my system is running great again. I'm afraid W7 update will just screw it up again

 

If you're happy with your system the way it is and it's stable, by all means run it as is without the updates. If a problem does arise, you still have the option to update then.

 

That's exactly what I'm thinking now. I'm just happy that it looks like we got rid of the BSOD. I hope its really gone.

Thanks a lot! You've been a big help!
+rep once I'm allowed again

 

I got a new one lol! I think its the same as before. Is it still related to the Killer driver?

 

Boo...guess they came back
It's a 0x9F POWER_DRIVER_STATE_FAILURE and it's blaming pci.sys with involvement of the nVidia drivers this time around. Thing to try would be another SFC System File Check, Repair install and clean install of nVidia drivers.

edit:I just read in another thread that you're OC'ing your 580M. That could be the cause of your new BSOD's. Was your GPU OC'ed at the time of this latest crash?

 

It was on stock settings at the time of the crash. But this is what happened.
My screen froze during my last OC so I have to force reboot. Then I noticed some artifacts when I tried playing Tera so I restarted again.

Just before it show the windows login screen, I got that BSOD.
After that it restarted normally and I got to play Tera last night and Diablo this morning without any signs of artifacts.

So do I have to reinstall the GPU driver? I am currently using 296.10, would you recommend the 301.24 beta?

 

It may have been a one time thing as a byproduct of the failed OC (just a guess). I would continue to use it as normal and see if you get any more BSOD's.
The 301.24 beta drivers gave me TDR errors so I reverted to 296.10.

 

I'm following your advice and so far its really working great. I am quite certain about one thing though, my R3 will surely get BSOD when I boot on battery power.

When I'm on battery, everything seems laggy, clicking icons, start button, tray icons or anything in the screen, is that supposed to be normal? After a while on battery, maybe within 5 minutes from log-in, I'll get a BSOD.

Even if I try to plug it in after booting on battery, I will surely get BSOD after a few minutes.

I cant remember getting BSOD anymore when running plugged in.

Is there also a way to assign only the program that can run on startup when running on battery? I want to disable auto start of apps like MSI AfterB, MSI AB OSD, and other program utilities for my 580M as they seem like looking for the GPU even when its on battery power. I have a feeling this contributes to the error causing BSOD.

I'm not sure about this but I'm guessing the mobo doesn't supply any power to the GPU when its on battery so it looks like, the "programs" I'm running for my 580M are looking for a non-existent GPU? Or am I wrong

Reason for that is because one time when running on battery, MSI AB and Nvidia driver prompted an error that "there is no hardware detected" or something.

 

Try doing a power drain. Unplug your laptop, remove the battery, open up the bottom and remove the CMOS battery. Press the power button for a minute and leave the batteries out for another minute. Put the batteries back in and boot up your system. Go into the BIOS and reset any changes you made from the default (SATA Operation to AHCI etc.).

 

Ok so after doing the power drain, I should boot on battery to check if I still get the error right? Sorry for the silly question as I dont really know about power drain

I think it should be obvious since there's no point of trying this if I will boot plugged anywy

Ok, I'll do this and will update. Thanks again.

 

haha yea, see if the error's still there.

 

Hi. Its been a long time since I last updated this thread but I've been getting some random BSOD again recently. It happen during non critical time mostly during standby or just minutes after doing my stuff.
I'm getting the Driver Power State Failure first and I read that most of the time, updating Windows solves this. I originally started this thread because I started getting BSOD after win update so I didnt run any update since I last fresh installed the OS.
Few days ago, I installed Nvidia's latest driver 301.42. After maybe a day or two, I got another BSOD but its still the Driver Power State Failure so I thought maybe a Win update will help so I decided to finally run windows update again.
I got one more DPSF after that but today, I got 2 BSODs again but now its Nvidia related, Video TDR Error.
When I updated Nvidia Driver, I uninstalled the 296.10 drivers properly, restarted on safe mode and run driver sweeper, rebooted and installed new drivers.
I have no idea about the error

Btw, another reason why I updated the gpu driver is I started getting some small fps stutter recently while playing D3 so I thought an update may solve it. I am still having some but now I'm not sure if its a lag spike or something else. My latency is always below 50ms (mostly10-20) everytime I test if this means anything.

I attached the minidump compressed folder again. Thanks in advance.

 

The first 3 BSODs you uploaded dated June 1st, 4th and 7th were all 0x09F DRIVER_POWER_STATE_FAILURE stop errors caused by pci.sys with involvement of win32k.sys and nvlddmkm. Here's the dump from the 7th:

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800eb8ea20, fffff80000b9c4d8, fffffa800d30d850}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : pci.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800eb8ea20, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa800d30d850, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f74000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c488 fffff800`03735e53 : 00000000`0000009f 00000000`00000003 fffffa80`0eb8ea20 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`036d40e6 : fffff800`00b9c5d8 fffff800`00b9c5d8 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x28e30
fffff800`00b9c530 fffff800`036d3396 : fffff800`03877700 00000000`00040f04 00000000`00000000 00000000`00000001 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`036d400e : 00000009`a943043a fffff800`00b9cc18 00000000`00040f04 fffff800`03844308 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`036d3707 : 00000002`29d34dc2 00000002`00040f04 00000002`29d34d11 00000000`00000004 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`036d077a : fffff800`03841e80 fffff800`0384fc40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

Followup: MachineOwner
---------

The dump from today (the 8th) was indeed a 0x116 TDR error. Those are always hard to troubleshoot since there are so many possible causes including hardware issues. I remember that Rev posted saying that the 3xx.xx drivers are geared more for the 600 series cards and may have issues with the 460M. Maybe it's having issues with 580M cards as well.

For now, I would reinstall 296.10 after completely removing 301.42. It may be worth a try to run SFC /SCANNOW Command - System File Checker again. Perhaps also try to install the all the Windows updates again to see if that eliminates the issues.