BSODs Persisting - Kernel-Power Errors

PhothreeniX

Canada161 Posts

December 17 2011 19:43 GMT

I have been having problems with this since the beginning of November.
It has on average been 1 BSOD per day, give or take. The total according to the Event Log, there have been 21 Kernel Power Critical errors since November 6th until today (Dec. 17)

I have searched and researched and done as much as I can to diagnose the problem. As much as I know how to do at least.
Stress tests using Prime95, Updated my SSD drivers and all other drivers. I've tried reseating memory and triple-checking all connections. I have done chkdsk scans as well as both the built in Windows Memory checker and memtest86. I have scoured multiple tech forums and the internet in general for more information. But I still have come up with no solution.

The main issue holding me back I believe is that it is completely random as far as I can see. Tasks like editing documents, playing minecraft, watching youtube videos, playing skyrim maxed out, standard virus scans all the way to letting it sit idle while taking a shower has resulted in the same BSOD. I should note all virus scans have completed with no threats.

I'll spoiler this out since I want to give as much information as possible so I'll spoiler the section and then a individual spoiler for each ss.
Starting from the earliest event log to the most recent here are the details.

+ Show Spoiler +

I'll include the system details in the first log only since they are all identical except the timestamp code.
+ Show Spoiler +

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2011-11-06T10:40:30.334410200Z

EventRecordID 444

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Pho3niX-PC

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

Logged on 5 occasions

+ Show Spoiler +

- EventData

BugcheckCode 122
BugcheckParameter1 0x20
BugcheckParameter2 0xffffffffc000009d
BugcheckParameter3 0xfffffa800df877c8
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

- EventData

BugcheckCode 122
BugcheckParameter1 0x20
BugcheckParameter2 0xffffffffc000009d
BugcheckParameter3 0xfffffa800ef3e7c8
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

- EventData

BugcheckCode 122
BugcheckParameter1 0x20
BugcheckParameter2 0xffffffffc000009d
BugcheckParameter3 0xfffffa800e0ab078
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800f94e060
BugcheckParameter3 0xfffffa800f94e340
BugcheckParameter4 0xfffff8000337e240
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800d1b8060
BugcheckParameter3 0xfffffa800d1b8340
BugcheckParameter4 0xfffff800033e38b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800e3ae060
BugcheckParameter3 0xfffffa800e3ae340
BugcheckParameter4 0xfffff800033968b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 3221226010
BugcheckParameter1 0xfffff8a0084c3d80
BugcheckParameter2 0xffffffffc0000006
BugcheckParameter3 0x774d523b
BugcheckParameter4 0x7ee780
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800e47cb30
BugcheckParameter3 0xfffffa800e47ce10
BugcheckParameter4 0xfffff800033e88b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800e4b4b30
BugcheckParameter3 0xfffffa800e4b4e10
BugcheckParameter4 0xfffff800033888b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800e2a78f0
BugcheckParameter3 0xfffffa800e2a7bd0
BugcheckParameter4 0xfffff800033ca8b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800d861b30
BugcheckParameter3 0xfffffa800d861e10
BugcheckParameter4 0xfffff800033d48b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800e235b30
BugcheckParameter3 0xfffffa800e235e10
BugcheckParameter4 0xfffff800033ce8b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800e27fb30
BugcheckParameter3 0xfffffa800e27fe10
BugcheckParameter4 0xfffff800033e28b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800f1ceb30
BugcheckParameter3 0xfffffa800f1cee10
BugcheckParameter4 0xfffff800033cd8b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800f11c730
BugcheckParameter3 0xfffffa800f11ca10
BugcheckParameter4 0xfffff800033e58b0
SleepInProgress false
PowerButtonTimestamp 0

+ Show Spoiler +

EventData

BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800ed88b30
BugcheckParameter3 0xfffffa800ed88e10
BugcheckParameter4 0xfffff800033d48b0
SleepInProgress false
PowerButtonTimestamp 0

Now I have noticed as I sure you have that the PowerButtonTimestamp is always equal to 0. From what I have read that means that the power was interrupted before a full error report could be logged.

Despite the obvious connection between power interrupted and "get a new PSU dood" I am hesitant take that as an answer. Mainly because I have pushed my computer very hard with games and stress tests and 9 times out of 10 I have no issues. Decent temperatures, no crashes, no problem at all. Its the one time that is the issue.

My system specs:
Intel Core i5 2500K
OCZ Vertex 3 120GB
ASUS P8Z68-V Pro
Mushkin Enhanced Silverline Stiletto 8GB 2X4GB PC3-10666 DDR3 (x2 for 16GB)
Gigabyte GeForce GTX 570 Fermi Windforce
Corsair Professional Series Gold AX750

Temperatures hover around 20C - 30C (68F- 86F). Under load it doesn't rise above 50C (122F).

I'm not sure what more information I can give to help you help me find some answers so I'll end this novel here.

Thanks in advance ♥

Emon_

3925 Posts

December 17 2011 19:50 GMT

First off - congrats on having a sexy system. The frustration that comes with a faulty system is a pain I know too well and I hope your problem gets resolved fast.

Perhaps your error is software related? Maybe something is installed that shouldn't be there. Though I'm guessing you've booted Memtest86 before any OS? I'd like to say wipe everything and do a clean install, but with todays computers that isn't too feasable. You can run Ubuntu from a CD / USB stick and see if it crashes.

Other than that - have you done any hardware troubleshooting? (taken parts from another computer, swaped them for parts in yours to see if you get the error)

PhothreeniX

Canada161 Posts

December 17 2011 20:19 GMT

Thanks, it is awful sexy and quite fun too (benchmarking Minecraft on minimum settings at 3.6k FPS hehe). I was used to my old furnace...err computer....it would heat my room in the winter time. Anyways.....

I haven't done any hardware troubleshooting as I don't have any additional hardware that is compatible (that would actually cause a problem). My old PSU was failing, GFX last legs, RAM was DDR2, etc.
I have done all diagnostics prior to booting my OS (such as memtest86 and chkdsk).
I have had no trouble booting from USB to Linux, which I had to do in order to update my SSD firmware since my Windows install is on my SSD. However that should make reinstallation of Windows not to much of a hassle.

And now that I think of it I recall seeing something in the Event log about corrupt. That word just seems familiar. .......

Actually I just found something interesting.....it seems foolishly I was only focusing on errors that were categorized as Critical. I just found other logs in the Event Log that seem to be related to my most recent BSOD. Since I'm lazy I'm just going to take a screen cap of all 4 of them. Hopefully I don't break the page with the large picture D:
+ Show Spoiler +

I am going to keep searching the event logs for that corruption event I remember seeing. In the meantime hopefully those additional logs can help pinpoint my issue (which does require a tissue)

l00l

179 Posts

December 17 2011 20:42 GMT

it could be your ssd causing it, i had that same error when my SSD caused bsods and it stopped once i got a stable firmware.
next time you bsod get the error code, if its 0x0000f4 it is probably the SSD

PhothreeniX

Canada161 Posts

December 17 2011 21:01 GMT

That is what I have been thinking however I have upgraded to the most recent firmware for my Vertex 3 SSD, 2.15. Apparently 2.13 was supposed to implement a fix to random BSODs. There have been no new topics on their forums regarding BSOD problems with the Vertex 3 and there have been no additional firmware updates or information about future firmware updates since mid-November.

[image loading]

jaj22

United Kingdom1376 Posts

December 17 2011 21:56 GMT

From your earlier bugchecks: 0x122 is a Windows Hardware Error Architecture internal error, but 0x20 param 1 is so far undocumented. Param 2 looks like an NTSTATUS code of STATUS_DEVICE_NOT_CONNECTED though. Bugcheck code 0x244 is also undocumented.

Suggests that a critical device has gone silent. The SSD is as good a bet there as anything. I suppose you could try disabling the sleep mode for it.

PhothreeniX

Canada161 Posts

December 18 2011 19:42 GMT

I assume I would disable sleep mode via Power Options in Control Panel? Well, if so, so far so good. I'll keep this thread updated if I (or someone else) do find a definitive solution in case someone else has a similar problem in the future.

chris89

United States1 Post

May 20 2013 08:08 GMT

I know this is old but I have been doing some testing with the same error. I know the solution at least I believe I do.

My system is totally stable running my GTX 280 on my 750W power supply and Phenom 2 X6.

I bought a GTX 460 for $39 on ebay since he said it was bad, would boot into safe mode but not Windows.

Okay so originally I thought it was bad since after repasting and cleaning it and flashing a low speed bios on it, it still presisted the Nvlddmkm.dll BSOD upon booting into windows.

So I was toying around with the bios on the 280 and I managed to get the same error when I had the voltage too low for the 2d/ boot up clocks or the clock it self was too low to 2d compared to the voltage. Anyway I re-flashed with ideal settings and it's all back to normal.

Anyway so I was like wow this makes me think about the GTX 460 issue. So I did a lot of research on how to flash and change bios settings for fermi gpu's since it's way different than the GTX 280.

I popped out the GTX 280 and popped the GTX 460 in. I see a tiny amount of imperfection artifacts on boot in the Gigabyte splash screen and then the rest is fine even safe mode looks fine. I was running 320.00 beta drivers in windows 7 x64.

So I adjusted all the voltages to a 0.975v minimum or the 460bios.rom while in windows with the 280. Shut down popped out the GTX 280 and popped the GTX 460 in and immediately flashed my new modded voltages bios.rom and I was able to boot into windows! Then I was able to game it up for like 45 minutes at 675Mhz and so I was like why not try out 800Mhz and it was working beautifully at 800Mhz. Then it BSOD'ed to the same NVLDDMKM.sys and according to the event viewer it's always Kernel-Power.

Since then I have been flashing over and over and over again to get it to work but it won't boot into windows, will only work in safe mode. I need to figure out what clock Safe Mode is using so I can mimic what safe mode likes in windows... Otherwise I could pop the 280 in and boot into windows but the system does shut down ocassionally when the GPU is under full load in game. Since the 280 is a power hungry monster.

So it's clear it's some kind of clock/ voltage power state issue as well as possibly my power supply. I mean I'm not seeing the 12v rail go below 12v but this could and most likely is incorrect according to AIDA64 my 5v rail is sitting at 4.170v which is way too low.

I suspect it is in fact the power supply so pick up a KINGWIN 850W for like $50 on ebay shipped and be golden. KINGWIN is the best performance and value power supply company I have ever witnessed. I have a Kingwin 1000W and it's just epic how efficient the rails are and how stable it is.

Anyway I would analyze your rail voltages in the bios first and write down the numbers and post them.

Then go into windows, find a good app like AIDA64 that can monitor the powersupply and go in game and set to NONE Fullscreen Windowed mode so you can see your voltages while under gaming load and write those numbers down. Since if I remember correctly, the rule of thumb is it not okay for any of the 12v, 3.3v, or 5v rail to droop under load below I think it was 20%.

THANKS

Please or register to reply.

BSODs Persisting - Kernel-Power Errors

Completed

Ongoing

Upcoming