Kernal-Power errors that are getting more frequent.

[Kernal]

Hi everyone, so I recently built a gaming rig and have been running it for a couple weeks, everything was fine at first, I did get about 3 different reboots in the first week that were all to do with Kernal-Power 41 errors, these would happen randomly, once it did it when I plugged in my headphones to the front of the case.

Well this is strictly a gaming machine, and its started to have these constant freezes/BSOD/crashes more and more often, I thought it may be due to the overclocking I did to the CPU and GPU (did not overclock FSB or memory) but have since put them back to stock and now it can happen shortly after booting into windows, there is not much else on this computer apart from games and tools for overclocking/monitoring, don't have heat issues, I'm running the stock drivers for everything, my ATI drivers are 10.7, was trying to update to the recent 10.8 but the pc will not stay on long enough now, my guess is either memory or PSU, will hopefully be running a memtest later tonight, but am attaching the minidump files here for you guys to hopefully shed some light on.

https://www.yousendit.com/dl?phi_ac..._download%26batch_id%3DaHlTcXlnYTI4Q1R2Wmc9PQ

 

[Kernal]

Just a heads up I think I found the problem, was able to boot into Safe Mode without issues each time, then setup the driver verifier, now I get a BSOD upon bootup and it seems to be an IO issue with the driver HIDCLASS.SYS, so looking into a fix right now.

 

[zigzag3143]

Hi everyone, so I recently built a gaming rig and have been running it for a couple weeks, everything was fine at first, I did get about 3 different reboots in the first week that were all to do with Kernal-Power 41 errors, these would happen randomly, once it did it when I plugged in my headphones to the front of the case.

Well this is strictly a gaming machine, and its started to have these constant freezes/BSOD/crashes more and more often, I thought it may be due to the overclocking I did to the CPU and GPU (did not overclock FSB or memory) but have since put them back to stock and now it can happen shortly after booting into windows, there is not much else on this computer apart from games and tools for overclocking/monitoring, don't have heat issues, I'm running the stock drivers for everything, my ATI drivers are 10.7, was trying to update to the recent 10.8 but the pc will not stay on long enough now, my guess is either memory or PSU, will hopefully be running a memtest later tonight, but am attaching the minidump files here for you guys to hopefully shed some light on.

https://www.yousendit.com/dl?phi_action=app/orchestrateDownload&rurl=https%253A%252F%252Fwww.yousendit.com%252Ftransfer.php%253Faction%253Dbatch_download%2526batch_id%253DaHlTcXlnYTI4Q1R2Wmc9PQ

Most of these were from memory. the others from your video driver. I would test the memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

And download and install a new video driver

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidump\081910-25412-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`0309de50
Debug session time: Thu Aug 19 03:38:19.580 2010 (GMT-4)
System Uptime: 0 days 0:00:19.188
Loading Kernel Symbols
...............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 280055b8e80, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 00000280055b8e80
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ede13a to fffff88003c297f2

STACK_TEXT:  
fffff800`043b6c98 fffff800`02ede13a : 00000000`003853dc fffffa80`051440a8 fffff800`03058c40 00000000`00000001 : 0xfffff880`03c297f2
fffff800`043b6ca0 fffff800`02ed8dcc : fffff800`0304ae80 fffff800`00000000 00000000`00000000 fffff800`02ff0ce0 : nt!PoIdle+0x53a
fffff800`043b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PoIdle+53a
fffff800`02ede13a 0fba25061518000f bt      dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`0305f648)],0Fh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PoIdle+53a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!PoIdle+53a

BUCKET_ID:  X64_0x1a_41287_nt!PoIdle+53a

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 00000280055b8e80
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ede13a to fffff88003c297f2

STACK_TEXT:  
fffff800`043b6c98 fffff800`02ede13a : 00000000`003853dc fffffa80`051440a8 fffff800`03058c40 00000000`00000001 : 0xfffff880`03c297f2
fffff800`043b6ca0 fffff800`02ed8dcc : fffff800`0304ae80 fffff800`00000000 00000000`00000000 fffff800`02ff0ce0 : nt!PoIdle+0x53a
fffff800`043b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PoIdle+53a
fffff800`02ede13a 0fba25061518000f bt      dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`0305f648)],0Fh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PoIdle+53a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!PoIdle+53a

BUCKET_ID:  X64_0x1a_41287_nt!PoIdle+53a

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

 

[Kernal]

Thanks Zigzag, I got memtest running atm, I tried to update the HIDCLASS.SYS file with DriverEasy, but will not allow install inside Safe Mode, so turned off the driver verifier and used Driver Sweeper to remove the ATI drivers, rebooted and shortly after getting into windows I got a BSOD saying something about REGISTRY_ERROR, was unable to take note of what else was on there as it was only up for a few seconds, will see what the memtest shows then.

 

[Kernal]

So I have finished the memtest, but before I actually let it run last night, I was able to fix the HIDCLASS.SYS issue by uninstalling some drivers last night to do with a gamepad I got and a keyboard that I no longer use and it was able to boot up and could even run Bad Company 2 for an hour just fine, so as I went to bed I ran the memtest for the night, and as I just got up, its showing about 23 million errors and counting, so yup, seems to be bad memory, so will be changing it today and later tonight I'll run another and see how that goes.

Thanks again.