Sign in with
Sign up | Sign in
Your question

Randomly reboots due to kernel power errors in eventvwr

Last response: in Windows 7
Share
May 5, 2012 10:01:12 PM

Hello all. Hope everyone is doing well today

I dont particularly stick to support forums, but since this issue is really unique to me, I am hoping someone can fill me in with some help

As of recently, I just upgraded my system to the following configuration:

Intel i5 2500K 1155 socket CPU
Gigabyte Z68A-D3H-B3 revision 1.3 mobo
8GB Corsair Vengeance DDR3 1600 RAM
(2) 60GB OCZ Solid 3 SSDs (One for each partition that I'm running on my system)
2TB Western Digital SATA HDD
nVidia GeForce GT430 2GB DDR3 graphics card
Rosewill RD 500-2SB 500 Watt PSU
Rosewill Challenger Mid-Size ATX case

Prior to installing the software, I had tested the memory, CPU, HDDs, everything. All checked out OK.

My system hosts two SSDs to run two partitions: One is Windows 7 Ultimate 64-bit, the other being Windows XP Professional 32-bit. The additional 2TB HDD is basically to store the tons of data that I have on, and I use the Windows 7 My Documents folders to have everything map to the HDD to acquire my data, download to it, etc.

The issue that I seem to be running into, is that every time I load up the Windows 7 partition, no matter how long I leave everything running, if per say I was to leave it running overnight, when I wake up in the morning, it will show that the PC has rebooted. Upon checking the event viewer, I am seeing multiple entries specifying that the error was caused by a kernel-power error, listed as event 41. Reviewing this info, I later noticed that it was causing a bugcheckcode of 265 everytime the issue occurs.

Ideally, I would like to think that it was hardware related, or driver related, as it mostly occurs when I play movies or videos, but when I boot the Windows XP partition, I never come across any of these issues whatsoever. Granted, the XP partition is used primarily for work when I do remote stuff from home, but granted I want to watch a movie on it I can also. Also, when loading the eventvwr on the XP partition, no kernel-power entries are listed.

So clearly, this is occuring on the Windows 7 partition, and not the Windows XP partition. Since I dont really think this is due to hardware issues, I am requesting for some advice on what I can do, or what I can upload here, to have reviewed and followed up with a suggestion. Thank you!

May 5, 2012 11:13:14 PM



Interesting.... the only thing I haven't checked was the PSU, I will give that a whirl and follow up on my findings. I will also upload the bugcheckcode entry I'm receiving when I finish working tonight so that perhaps if something else is going awry, maybe the answer is in there

Currently running Speedfan, the only thing giving me some concern are my 4 cores running around 45 degrees C. Everything else is running between 30-35 degrees C. So I also have a couple things to check on. I am using a stock cooler that came with the CPU. Which would you prefer me try upgrading first, the cooler or the PSU?
Related resources
May 6, 2012 5:35:24 AM

Here's an entry on my eventvwr regarding this:


- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-05-05T12:55:01.088006300Z" />
<EventRecordID>7909</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>PETERSON3</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">265</Data>
<Data Name="BugcheckParameter1">0xa3a039d89a675789</Data>
<Data Name="BugcheckParameter2">0xb3b7465eece5270b</Data>
<Data Name="BugcheckParameter3">0xfffff8000381137c</Data>
<Data Name="BugcheckParameter4">0x1</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>


Any suggestions? My temps are running low enough to where this should not be a concern. I also had this issue on my older PC and both PSU's cause this issue to occur. Only thing in my new machine that was taken from my old machine, is the 2TB HDD which after testing with a Western Digital DLG tool, reported no errors.

I tried updating drivers on my system, as they were outdated. I feel convinced, sad to say, that this could possibly be a SP1 issue that should be addressed, as numerous people also are experiencing this issue with no solid fix yet. Just a hunch though.
May 6, 2012 5:59:30 AM

Also am receiving some bugcheck messages as well:


Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 5/5/2012 8:55:07 AM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PETERSON3
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a039d89a675789, 0xb3b7465eece5270b, 0xfffff8000381137c, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050512-8814-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-05-05T12:55:07.000000000Z" />
<EventRecordID>7929</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>PETERSON3</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000109 (0xa3a039d89a675789, 0xb3b7465eece5270b, 0xfffff8000381137c, 0x0000000000000001)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">050512-8814-01</Data>
</EventData>
</Event>


Any input would be appreciated. Thanks!
May 6, 2012 10:06:17 AM

Only times I ran into 0x00000109 was with driver problems in win7 64 bit, as only drivers should be able to interfere with kernel to that degree that it starts bitching around, at least in win7x64. I would try with drivers. Just personal experience here.
May 6, 2012 2:03:00 PM

Rattengesicht said:
Only times I ran into 0x00000109 was with driver problems in win7 64 bit, as only drivers should be able to interfere with kernel to that degree that it starts bitching around, at least in win7x64. I would try with drivers. Just personal experience here.



Hey there Rattengesicht. Thanks for your input!

Yeah that seems to be the general consensus regarding this issue.... either hardware problems or drivers. My only concern hardware wise would have to be the 2TB HDD since it was moved over from the previous PC I had, and also ran into these issues running Windows 7 64-bit with SP1. But I ran a scan with the western digital tool yesterday and reported no issues with it.

I have since posting this thread, updated the drivers and let the system run overnight. No reboots occured. I feel as though that the issue might be related to SP1, and need to be fixed in another SP release. Guess we will find out.
May 8, 2012 3:39:03 AM

Rattengesicht,

Hey I just wanted to give you an update. I went about updating the drivers Saturday night per your recommendation to check there after testing my hardware. Appears that I had a few that were outdated from last year. I've been running the box for the last 2 days and so far so good no reboots as of yet.

I'm not sure of turning off the hard drive feature that shuts down the drive during hibernation was a good idea, but in a sense I want to replicate how my settings are on my XP partition as best as possible, so I disabled HDD shutdowns during inactive periods as well. Either or, I've come home to my OS still loaded from how I last left it.

If this all plays out and I continue to truck through this without a reboot after weeks end, I will consider this to be resolved, and will personally thank you for your swell suggestion. Wouldn't of even thought of it since I just bought the mobo too. Oh well.... thanks a lot :-)
May 9, 2012 5:57:22 PM

Just an update....

I have not had any reboots since updating the drivers over the weekend. Appears to be in the clear. Thanks everyone for your input. This thread can be closed
May 19, 2012 1:53:48 AM

Hey guys quick update....

I ran a debugging tool cause I received a kernel power error yesterday. Wondering if anyone can analyze this and give me another suggestion on how to approach this:


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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatchi...
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89af9051b, Reserved
Arg2: b3b7465eed772e11, Reserved
Arg3: fffff88000d38ed8, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

OVERLAPPED_MODULE: Address regions for 'OEM03Afx' and 'OEM03Vfx.sys' overlap

FAULTING_IP:
CLFS!CClfsBaseFilePersisted::CreateImage+0
fffff880`00d38ed8 488bc4 mov rax,rsp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x109

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031a1498 00000000`00000000 : 00000000`00000109 a3a039d8`9af9051b b3b7465e`ed772e11 fffff880`00d38ed8 : nt!KeBugCheckEx


STACK_COMMAND: kb

FOLLOWUP_IP:
CLFS!CClfsBaseFilePersisted::CreateImage+0
fffff880`00d38ed8 488bc4 mov rax,rsp

SYMBOL_NAME: CLFS!CClfsBaseFilePersisted::CreateImage+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLFS

IMAGE_NAME: CLFS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d

FAILURE_BUCKET_ID: X64_0x109_1_CLFS!CClfsBaseFilePersisted::CreateImage+0

BUCKET_ID: X64_0x109_1_CLFS!CClfsBaseFilePersisted::CreateImage+0

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

2: kd> lmvm CLFS
start end module name
fffff880`00d18000 fffff880`00d76000 CLFS (pdb symbols) c:\symbols\clfs.pdb\BC47A0828BC441C0AE1580A06361F0AF2\clfs.pdb
Loaded symbol image file: CLFS.SYS
Mapped memory image file: c:\symbols\CLFS.SYS\4A5BC11D5e000\CLFS.SYS
Image path: \SystemRoot\system32\CLFS.SYS
Image name: CLFS.SYS
Timestamp: Mon Jul 13 19:19:57 2009 (4A5BC11D)
CheckSum: 00065C46
ImageSize: 0005E000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0000.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: clfs.sys
OriginalFilename: Clfs.Sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: Common Log File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
!