Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Seemingly random BSOD Event ID: 41 Task Category: 63

22 Sep 2014   #1
3000

Windows 7 Pro 64
 
 
Seemingly random BSOD Event ID: 41 Task Category: 63

Hi this is my post so I hope I hope I get this all right, sorry if I do something wrong. I'll try and give as much info as I can.

I'm on a custom built PC I built around this time 2 years ago. Not long after owning it I started getting the BSOD errors. They are quite sporadic, sometimes happening a couple of times a day, sometimes not for several days. They also seem to happen when I'm doing a variety of things, sometimes after hours of use doing multiple tasks or playing games, sometimes when I'm just watching a movie or have not long booted the PC.

Because of unrelated issues I replaced the wireless card not long after I got it which didn't fix it. The PSU got really noisy and hot so I got a replacement of the same model (I'm not sure if this temporarily fixed the issue or not, I can't remember).

I ran stress tests on the CPU, GPU and memory (over-night tests if I remember correctly) and it didn't crash during them or show any errors as far as I'm aware.

I then got a new hard drive so I could do a fresh install. I re-installed the OS but it still happened. On this hard drive the errors seem to be less regular but because it never fixed the issue I haven't been on this hard drive for long while so it may just be luck that it isn't crashing as much as the other hard drive and installation.

Here is what it says in the details pop up in the event viewer...

- <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="2014-09-22T14:15:24.543221000Z" />
<EventRecordID>13379</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Sam-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">80</Data>
<Data Name="BugcheckParameter1">0xffffffffffffff7f</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0xfffff80001a86166</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Attachment 334222

Also... it just happened again whilst writing this (I'm uploading this on another PC), is it worth using the dm log collector again and uploading another file?

Thanks in advance for any help


My System SpecsSystem Spec
.
22 Sep 2014   #2
HarriePateman

Windows 7 Ultimate 64-bit
 
 

Welcome to 7F,

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80001aa717c}

Probably caused by : ntkrnlmp.exe ( nt!KeTerminateThread+314 )

Followup: MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff7f, 0, fffff80001a86166, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!zzzWakeInputIdle+c7 )

Followup: MachineOwner
---------
Here are the 2 DMP files from the 2 BSOD's you have had.


The first one BugCheck A The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

The Second One Bugcheck 0x50 Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).


As Both of these can be caused by Drivers i would like you to try this before we try anything else:

information   Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier - Enable and Disable


information   Information
Your Anti-Virus is known for causing Blue screen of death issues on Windows 7.
I recommend you change your Anti-Virus and see if the problem still persists.
Here is a list of trusted Anti-Virus's:

AVAST 2014 | Download Free Antivirus Software for Virus Protection

Avira Free Antivirus - Download the best free antivirus software

Free Antivirus Software - Download Bitdefender UK Free Edition
My System SpecsSystem Spec
22 Sep 2014   #3
3000

Windows 7 Pro 64
 
 

Thank you so much for helping. I'll replace AVG with a different AV and leave windows running with the driver verifier on and then report back after the next BSOD.

One of the first things I did when I installed windows on the second HD was install AVG actually, so that's something that's always been consistent on both instances so could be a potential culprit.

Really appreciate you help
My System SpecsSystem Spec
.

22 Sep 2014   #4
HarriePateman

Windows 7 Ultimate 64-bit
 
 

Quote   Quote: Originally Posted by 3000 View Post
Thank you so much for helping. I'll replace AVG with a different AV and leave windows running with the driver verifier on and then report back after the next BSOD.

One of the first things I did when I installed windows on the second HD was install AVG actually, so that's something that's always been consistent on both instances so could be a potential culprit.

Really appreciate you help
No worries, glad i could help
My System SpecsSystem Spec
23 Sep 2014   #5
3000

Windows 7 Pro 64
 
 

information   Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.
Attachment 334344

Hello again!

Ok, I got my next crash and I've attached the files. I've not been able to change the anti-virus yet because I'm on a bad connection for a few days, so I can't download a new anti-virus.
My System SpecsSystem Spec
23 Sep 2014   #6
HarriePateman

Windows 7 Ultimate 64-bit
 
 

Hello,

Just checking did you follow the instruction within the tutorial word for word?

Code:
Unable to read TrackIrqlQueue at fffff80001fb7120
IRQL tracking is not enabled. You have to enable Driver Verifier
for at least one driver to activate IRQL tracking.
Driver Verifier - Enable and Disable

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff7f, 0, fffff80001adf166, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!zzzWakeInputIdle+c7 )

Followup: MachineOwner
---------
It is possible that its your hardware causing the issue, after this we will do some hardware tests.
My System SpecsSystem Spec
23 Sep 2014   #7
3000

Windows 7 Pro 64
 
 

I believe I did, is there a way to check whether it's currently enabled then? Or would I have go through the disabling process then try the enabling process again, and wait for another BSOD? Or should I try some hardware issues now?
My System SpecsSystem Spec
23 Sep 2014   #8
HarriePateman

Windows 7 Ultimate 64-bit
 
 

Ideally it would be best if you could double check the DV and run it again until a BSOD.

However we can try some hardware Tests, but these will take along time.
My System SpecsSystem Spec
23 Sep 2014   #9
3000

Windows 7 Pro 64
 
 

Ok, I'll try the DV again if that's best.

I'm going to re-install my graphics drivers anyway as the sound and picture are jumping when I play videos and then replace AVG, so I'll do all that first while I wait for another BSOD

Thanks again
My System SpecsSystem Spec
23 Sep 2014   #10
HarriePateman

Windows 7 Ultimate 64-bit
 
 

Brilliant see you soon
My System SpecsSystem Spec
Reply

 Seemingly random BSOD Event ID: 41 Task Category: 63




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD event ID 41 task category 63 dmp included
hi all, first post, long time lurker here and so far have found a fix to most of my problems just googling and ending up here in many cases but I need some very specific help so I just joined up today so, I got a bsod out of nowhere twice these past 2 weeks, and not while gaming or anything...
BSOD Help and Support
Multiple BSOD Event ID - 41 Task Category (63) Source - Kernel Power
Hey guys I keep getting the BSOD. 28 times in the last week and is bugging me. Just wondering if you can help me fix this. Would be very much appreciated. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power"...
BSOD Help and Support
BSOD playing Guild Wars 2, kernel event id 41 task category(63)
Hiya My computer has started blue screening randomly. It happens occasionally while playing league of legends and will always crash within about the first few min of playing guild wars 2. I think it might be a faulty motherboard. Almost a year ago my computer was blue screening and i sent the...
BSOD Help and Support
Kernel-Power: Event ID 41 - Task Category (63) BSOD's
I've been having this problem from some time now. My computer randomly locks up, it's not shutting down or going to blue screen. It just locks up and stays there until I hard reset the entire computer. My computer specs. Intel Quad-Core i7-920 L3 Cache 8MB 2.67Hz 2.79Ghz 2793 Mhz. Nvidia...
BSOD Help and Support
Seemingly Random BSODs: EVENT ID 41 TASK CATEGORY 63 BugcheckCode 26
Desktop system Specs: CPU: Intel Core i7-2600K Sandy Bridge 3.4GHz (3.8GHz Turbo Boost) LGA 1155 95W Quad MOBO: ASUS P8Z68-V PRO LGA 1155 Intel Z68 w/UEFI BIOS Storage1: Mushkin Enhanced Chronos Deluxe MKNSSDCR120GB-DX 2.5" 120GB SSD (SATA III) Storage2: Western Digital Caviar Black...
BSOD Help and Support
[New Windows 7 Laptop] BSOD Kernel-Power Event ID 41 Task Category 63
Howdy. I've had my laptop since Christmas Day and it has BSOD 3 times: today, on the 28th and the 29th. The Event Viewer tells me that the critical errors were Kernel-Power Event ID 41 Task Category (63). Here are the details of the critical errors: - System - Provider ...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App