Seemingly random BSOD Event ID: 41 Task Category: 63

22 Sep 2014

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

HarriePateman · 22 Sep 2014

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

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

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

22 Sep 2014

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 :)

HarriePateman · 22 Sep 2014

3000 said:

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 :)

23 Sep 2014

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.

HarriePateman · 23 Sep 2014

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.
:)

23 Sep 2014

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?

HarriePateman · 23 Sep 2014

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.

23 Sep 2014

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

HarriePateman · 23 Sep 2014

Brilliant see you soon :)