Kernel-PowerEvent ID: 41 Task Category (63)

Hi

I think this is the 'Last chance saloon' for me and gaming. Cutting to the chase whilst gaming the game crashes and takes out Windows too

Consequently Event Viewer reports a very unhelpful error message:: Kernel-PowerEvent ID: 41 Task Category (63)

Below is a list of fixes provided by the game distributors and other well meaning Techy Guru's  that have not succeeded and/or raised grounds for concern:

1. Re-installed game
2. Install game on a second/slave HD instead
3. Run the game as Administrator
4. Verify the Integrity of the Game Cache
5. Check your Antivirus Settings
6. Run Steam as Administrator
7. Choose to run the game in Compatibility Mode for Windows XP (Service Pack 3) (not available only Vista & Windows server 2008)
8. Update Windows
9. Monitor PC for any over heating issues

The above topic error message is the only critical error message that appears in Event Viewer when I am gaming, The game normally crashes 10 -15 mins in to it,

but Windows 7 seems to work perfectly fine until I begin gaming. My PC has been upgraded recently and more than exceeds the minimum spec for the game I am 'Trying' to play

I installed Windows Kits with the Debugging tool feature hoping this may help ID the problem

I have uploaded the mini dump file and also DxDiag.txt file too hoping someone can make sense of it.

So far I have obviously run 'Debugging Tools for Windows' in the background before I begin gaming, when the game crashes normally after about 10 to 15 minutes of play it takes out Windows too, so I am not sure that the dump file uploaded is of any help in identifying the cause(s) but I hope someone can let me know.

Link to my PC system & most recent dump file and other files etc---------->      https://onedrive.live.com/?id=86B405B97366D741%21105&cid=86B405B97366D741

Appreciate any help from anyone who wants to lend a hand.

Edited by Harry_Palmer, 06 July 2017 - 01:26 PM.

Hi. . .

Please run the BSOD Posting Instructions app - https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

You can skip step #3 (PERFMON).

Regards. . .

jcgriff2

Event ID 41 is Windows saying that it doesn't know why it shut down.

If the Event ID 41 error is caused by the game crashing and taking Windows down with it - then it's likely a hardware problem.

If the Event ID 41 error is caused by forcing the system to shut down (by holding the power button down), then it may/may not be hardware.

On occasion it can be because a BSOD occurred and it forced the system to restart unexpectedly.
More info on the Event ID 41 error:  http://support.microsoft.com/kb/2028504

Please start with these free hardware diagnostics (after uploading the reports that jcgriff2 asked for):  http://www.carrona.org/hwdiag.html

Please run ALL of the reports and let us know the results.  We can move on after all that is done.
 

Edited by usasma, 06 July 2017 - 04:01 PM.

 

Hi. . .
 
Please run the BSOD Posting Instructions app - https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
 
You can skip step #3 (PERFMON).
 
Regards. . .
 
jcgriff2

Have uploaded to specified BSOD zipped folder as instructed to this link: https://onedrive.live.com/?id=86B405B97366D741%21105&cid=86B405B97366D741

Edited by Harry_Palmer, 06 July 2017 - 06:55 PM.

Event ID 41 is Windows saying that it doesn't know why it shut down.

If the Event ID 41 error is caused by the game crashing and taking Windows down with it - then it's likely a hardware problem.

If the Event ID 41 error is caused by forcing the system to shut down (by holding the power button down), then it may/may not be hardware.

On occasion it can be because a BSOD occurred and it forced the system to restart unexpectedly.
More info on the Event ID 41 error:  http://support.microsoft.com/kb/2028504

Please start with these free hardware diagnostics (after uploading the reports that jcgriff2 asked for):  http://www.carrona.org/hwdiag.html

Please run ALL of the reports and let us know the results.  We can move on after all that is done.
 

Thanks for the swift reply usasma, waiting for first poster JCGRIFF2 to analyze my BSOD upload he requested.

Edited by Harry_Palmer, 06 July 2017 - 06:55 PM.

Hi. . .

There were no dump files in the Sysnative zip file.

Please check \windows\minidump for dump files

If there are dump files, copy the  \windows\minidump folder to Documents; zip up the entire folder and ATTACH it to your next post.

Regards. . .

jcgriff2

EDIT: There was a processed dump file on your onedrive listing the probable cause as an IBM driver -

RapportCerberus64_1804047.sys

Please go to \windows\system32\drivers - locate that driver and obtain any detailed info from it (like who/what it belongs to). Google says it is part of "Rapport", but I can't find software with that name. If you know of it. Either update the program installation or remove the program installation from your system.

Edited by jcgriff2, 08 July 2017 - 02:45 PM.

Hi

I have no mini dumps files to present to you, the folder is clean, the only one is the

one i uploaded to my OneDrive.

I tried to create one by installing and running 'Debugging Tools for Windows' whilst in game

but when the game constantly crashes it takes out Windows too so I guess as a result no dump file can be created..

As for your observation regarding 'RapportCerberus64_1804047.sys' (IBM driver) its an App that my bank

advised me to install for added security, I have now uninstalled it as you suggested, so let's see what happens.

Thank you for continued help.

Hi. . .

My pleasure to try and help here.

That driver was named in the processed dump on your One Drive as the probable cause of the crash. It appeared on the stack and is the only 3rd party driver on the stack, so there is little doubt that it is involved.

If you scroll to the right, you'll see RapportCerberus64_1804047 on a few lines -

STACK_TEXT: 
fffff880`0e0f5240 fffff880`08dd7104 : fffff8a0`112585f0 fffffa80`11e5fbe0 fffff880`0e0f5420 fffff880`0e0f5420 : nt!ExAcquireResourceSharedLite+0x4e
fffff880`0e0f52b0 fffff880`08dc7e36 : 00000000`00000208 fffffa80`12e30f80 fffffa80`13710010 fffff800`03c81a95 : udfs!UdfAcquireResource+0x50
fffff880`0e0f52e0 fffff880`08da2f42 : fffffa80`11e5fbe0 fffffa80`14b0d010 fffff880`00000208 fffffa80`14b0d248 : udfs!UdfCommonQueryInfo+0xa2
fffff880`0e0f5360 fffff880`01045bcf : fffffa80`14b0d248 fffffa80`14b0d010 fffffa80`13710010 00000000`00000000 : udfs!UdfFsdDispatch+0x21a
fffff880`0e0f53d0 fffff880`010446df : fffffa80`14736320 fffffa80`14925710 fffffa80`14736300 fffffa80`14b0d010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0e0f5460 fffff880`01045bcf : fffffa80`14b0d290 00000000`00000001 fffff880`0e0f56a0 fffff880`03e5a78d : fltmgr!FltpDispatch+0xcf
fffff880`0e0f54c0 fffff880`01048aea : 00000000`00000000 00000000`00000000 fffffa80`13632100 fffffa80`14925710 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0e0f5550 fffff880`0107e4f2 : fffffa80`11bbf108 00000000`00000001 fffffa80`11bbf010 fffffa80`149257c0 : fltmgr!FltPerformSynchronousIo+0x2ca
fffff880`0e0f55f0 fffff880`03f00e22 : 00000000`00000001 fffffa80`1423cab0 fffffa80`32707063 fffff880`03f498c0 : fltmgr!FltQueryInformationFile+0x52
fffff880`0e0f5630 00000000`00000001 : fffffa80`1423cab0 fffffa80`32707063 fffff880`03f498c0 fffff8a0`00000009 : RapportCerberus64_1804047+0xcee22
fffff880`0e0f5638 fffffa80`1423cab0 : fffffa80`32707063 fffff880`03f498c0 fffff8a0`00000009 fffff880`0e0f5700 : 0x1
fffff880`0e0f5640 fffffa80`32707063 : fffff880`03f498c0 fffff8a0`00000009 fffff880`0e0f5700 00000000`00000001 : 0xfffffa80`1423cab0
fffff880`0e0f5648 fffff880`03f498c0 : fffff8a0`00000009 fffff880`0e0f5700 00000000`00000001 fffff880`03e598f6 : 0xfffffa80`32707063
fffff880`0e0f5650 fffff8a0`00000009 : fffff880`0e0f5700 00000000`00000001 fffff880`03e598f6 00000000`0000001e : RapportCerberus64_1804047+0x1178c0
fffff880`0e0f5658 fffff880`0e0f5700 : 00000000`00000001 fffff880`03e598f6 00000000`0000001e fffff8a0`00000001 : 0xfffff8a0`00000009
fffff880`0e0f5660 00000000`00000001 : fffff880`03e598f6 00000000`0000001e fffff8a0`00000001 fffff8a0`1c9ac250 : 0xfffff880`0e0f5700
fffff880`0e0f5668 fffff880`03e598f6 : 00000000`0000001e fffff8a0`00000001 fffff8a0`1c9ac250 00000000`00000040 : 0x1
fffff880`0e0f5670 00000000`0000001e : fffff8a0`00000001 fffff8a0`1c9ac250 00000000`00000040 fffff880`03e458d0 : RapportCerberus64_1804047+0x278f6
fffff880`0e0f5678 fffff8a0`00000001 : fffff8a0`1c9ac250 00000000`00000040 fffff880`03e458d0 fffff8a0`1f565340 : 0x1e
fffff880`0e0f5680 fffff8a0`1c9ac250 : 00000000`00000040 fffff880`03e458d0 fffff8a0`1f565340 fffff880`03e458d0 : 0xfffff8a0`00000001
fffff880`0e0f5688 00000000`00000040 : fffff880`03e458d0 fffff8a0`1f565340 fffff880`03e458d0 fffff8a0`1f565340 : 0xfffff8a0`1c9ac250
fffff880`0e0f5690 fffff880`03e458d0 : fffff8a0`1f565340 fffff880`03e458d0 fffff8a0`1f565340 fffff8a0`1f2c8e90 : 0x40
fffff880`0e0f5698 fffff8a0`1f565340 : fffff880`03e458d0 fffff8a0`1f565340 fffff8a0`1f2c8e90 fffff880`03e458d0 : RapportCerberus64_1804047+0x138d0
fffff880`0e0f56a0 fffff880`03e458d0 : fffff8a0`1f565340 fffff8a0`1f2c8e90 fffff880`03e458d0 00000000`00000000 : 0xfffff8a0`1f565340
fffff880`0e0f56a8 fffff8a0`1f565340 : fffff8a0`1f2c8e90 fffff880`03e458d0 00000000`00000000 fffffa80`1423cab0 : RapportCerberus64_1804047+0x138d0
fffff880`0e0f56b0 fffff8a0`1f2c8e90 : fffff880`03e458d0 00000000`00000000 fffffa80`1423cab0 fffff8a0`1f2c8e90 : 0xfffff8a0`1f565340
fffff880`0e0f56b8 fffff880`03e458d0 : 00000000`00000000 fffffa80`1423cab0 fffff8a0`1f2c8e90 fffff880`03e62748 : 0xfffff8a0`1f2c8e90
fffff880`0e0f56c0 00000000`00000000 : fffffa80`1423cab0 fffff8a0`1f2c8e90 fffff880`03e62748 fffff880`0e0f5770 : RapportCerberus64_1804047+0x138d0
 

So what happened to the minidumps?  Did you delete them by using CCleaner or are you saying there never were any?  I would have expected to find at least the one on your One Drive that you processed with Windbg (nice job, by the way).

In the future, try out these commands:

!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!sysinfo cpuinfo;!sysinfo 
machineid; !sysinfo cpuspeed; !sysinfo smbios

They all should be on one line. It will give you driver info + system info.

See how things go now that the offending driver is gone.

Regards. . .

jcgriff2

Hi jcgriff2

Removed the App 'RapportCerberus64_1804047' as you suggested but it appears to have made

no difference, game to continues to crash, but Windows generated a dump file which i have uploaded

to my Onedrive entitled 'WER6346.tmp'  https://onedrive.live.com/?id=86B405B97366D741%21105&cid=86B405B97366D741

You commented:

'In the future, try out these commands:

!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!sysinfo cpuinfo;!sysinfo
machineid; !sysinfo cpuspeed; !sysinfo smbios'

To be frank I don't know how to execute the above, can you help?

Also I am running WinDbg in kernal mode, having read the help tutorial that came with it but I am not really sure

it is set up correctly, I ran it before the last game & windows crash and no mini dump files were

created. I am a heating engineer for a living and part of my job is to diagnose and repair all types of

boilers when a problem develops but by comparison this issue with my PC is so difficult to resolve

or even finding the right tools for the job, having said that when I think I have the right tools then this

in its self creates another problem by knowing how to use them in the correct manner.

How you guys are able to problem solve complex PC issues and analyze data/logs (to me anyway) is quite astounding.

Edited by Harry_Palmer, 10 July 2017 - 05:20 PM.

The commands that I gave you - !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!sysinfo cpuinfo;!sysinfo  just get pasted into the kd> line at the bottom of Windbg.

I don't know what the file 'WER6346.tmp'  is - I need a dump file from \windows\minidiump -- copy the latest dump out to Documents, then zip it up.

Please ATTACH the file to your post instead of using One Drive. Thank you.

Regards. . .

jcgriff2

Edited by jcgriff2, 11 July 2017 - 02:13 PM.