Windows 10 BSOD with bugcheck 0xc8

JupiterMoon

New Member
Joined
Jun 22, 2018
Messages
23
This gives the IRQL_UNEXPECTED_VALUE which is usually caused by a driver. But I don't know which driver.

Data from Event:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/21/2018 8:25:30 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Zekrom
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="Link Removed">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2018-06-22T00:25:30.175952600Z" />
<EventRecordID>2781</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Zekrom</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">200</Data>
<Data Name="BugcheckParameter1">0x20002</Data>
<Data Name="BugcheckParameter2">0xfffff80f47aa1010</Data>
<Data Name="BugcheckParameter3">0xfffffe8143757460</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">3</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

This event seems relevant too?

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 6/21/2018 8:25:56 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Zekrom
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c8 (0x0000000000020002, 0xfffff80f47aa1010, 0xfffffe8143757460, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3892e736-e707-4598-ab2d-e69b721606b3.
Event Xml:
<Event xmlns="Link Removed">
<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="2018-06-22T00:25:56.229714100Z" />
<EventRecordID>2829</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Zekrom</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000c8 (0x0000000000020002, 0xfffff80f47aa1010, 0xfffffe8143757460, 0x0000000000000000)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">3892e736-e707-4598-ab2d-e69b721606b3</Data>
</EventData>
</Event>

But I could not find the Dump file on my disk... For some reason both times this has happened have been while accessing paypal and on the paypal login site.
Also, my computer sometimes uses all of its 16GB of RAM when I'm just browsing the internet and I was worried I may have a memory leak in one of my drivers or something? Could that be related? Thanks
 
Solution
Also the website that had been crashing (PayPal login) allowed me to log in and do stuff now without issues so it was Intel Technology Access! Awesome, thank you for all the help!!!
Sort by date Sort by votes
Hi,
try changing your settings so that your only getting the small 256kb dump file:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

Try using the app found in the sticky to collect the data:

How to ask for help with a BSOD problem

JupiterMoon said:
Also, my computer sometimes uses all of its 16GB of RAM when I'm just browsing the internet and I was worried I may have a memory leak in one of my drivers or something? Could that be related?
Click to expand...
It may be related but without seeing the dump file it's hard to say for certain.

Try checking for malware using something like Malwarebytes

If your using a laptop then use the drivers supplied by the manufacturer otherwise bsod's can result. (the gpu being the only exception to this rule)

Please post make and model of system.
 
Upvote 0 Downvote
I changed it to do a minidump and am attaching the zip file. I also ran a threat scan with Malwarebytes and it was clean.
My specs are
CPU: Intel Core i7 6700 @ 3.40GHz
Mobo: MSI Z170A GAMING M5
GPU: NVIDIA GeForce GTX 980 (MSI)
RAM: 16GB DDR4
 

Attachments

Upvote 0 Downvote
As the above says now you've changed settings you'll need to bsod again before a dumps created.

Oh and a disabled pagefile will also stop dump file creation. Some users do this when they have an SSD running although if you never messed with it then don't worry.
 
Upvote 0 Downvote
It happened again!! Once again on the paypal login screen! All three times I've blue screened have been that site, it can't be a coincidence!! Maybe I should clear my cache and cookies for that site?
 

Attachments

Upvote 0 Downvote
According to the SystemInfo.txt file you have provided the BIOS version of your motherboard is outdated.
There is a BIOS update available for your motherboard, click the link:
Link Removed

WARNING!!!
If you don't know how to update the BIOS, then please ask somebody who knows how to do it or go to a PC repair shop.
 
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C8, {20002, fffff801e3a01010, ffffd78e10437460, 0}

*** WARNING: Unable to verify timestamp for ndisrfl.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrfl.sys
Probably caused by : ndisrfl.sys ( ndisrfl+5619 )

Followup:     MachineOwner
Hi,
try updating the above driver mentioned in the probable cause:

ndisrfl.sys: Intel Technology Access Filter Driver
Link Removed

If the blue screen continues then try updating your bios to the latest version. Bios flashing isn't as risky as it used to be but still if your unsure on how to proceed it's perhaps best left to someone that does.

Your current bios is 1.90 and it looks like there has been at least 7 updates since:
Link Removed
 
Upvote 0 Downvote
oof yeah my bios is way out of date! I thought it would auto update with MSI live update but it didn't, ugh. I'm trying that driver first but will also update my BIOS haha oops
 
Upvote 0 Downvote
alright I updated the driver ndisrfl.sys: Intel Technology Access Filter Driver and also sucessfully updated my BIOS let's try and login to PayPal
 
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C8, {20002, fffff80c9de71010, ffffd289f1ee7460, 0}

*** WARNING: Unable to verify timestamp for ndisrfl.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrfl.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
Hi Jupiter,
you have the same driver being flagged up. Tell me was it possible to remove the old driver before installing the new version?

If not, try removing the driver via the Apps page (what used to be add and remove prog's) and then installing again.

Also when you flashed the bios, did you click on 'load optimised defaults' (you'll see this setting or words to that effect in the bios itself)?

One should always do this after applying a new bios.

I had a look through your system drivers and they could do with updating particularly chipset.

Please use the drivers found on your motherboard support page, in fact I'll arrow the chipset as these are ultra and I mean ultra important:



Link Removed

Please update all drivers.

Lastly try going through your applications and removing anything which is either old or no longer used.
 
Last edited by a moderator:
Upvote 0 Downvote

It says for Intel Management Engine Driver+Microsoft hotfix the version I have is newer than the one on the site? Should I download it anyways?
 
Last edited by a moderator:
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C8, {20002, fffff80df8931010, ffff96069b90f460, 0}

*** WARNING: Unable to verify timestamp for ndisrfl.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrfl.sys
Probably caused by : ndisrfl.sys ( ndisrfl+5619 )

Followup:     MachineOwner
Hi Jupiter,
Try installing the drivers found on this page as they are later versions:
Link Removed

Also it may be the case that another driver is causing the driver thats mentioned to trip out. To try and discover if this is so it might help if you ran the driver verifier.
The verifier stresses drivers on start up which causes any dodgy drivers to bsod. The name of the driver is then caught on a dump file.

Before you try the verifier tho make sure you have a recovery disk/usb for win 10:
https://support.microsoft.com/en-gb/help/4026852windows-create-a-recovery-drive

The reason for this is because on rare occasion the verifier can cause a boot loop. If this happens you boot from the recovery disk/usb, go into safe mode and turn the verifier off. Hopefully the offending driver will have been caught on a dump.
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Any problems post back.
 
Upvote 0 Downvote
OK I did the driver verifier and I kept getting this message. It kept restarting when I said "exit and go to Windows 10" and running the verifier again, and a driver was getting flagged... And I noticed the media was all going E: and that's my flash drive, which wasn't plugged in even! And then I plugged it in and now I'm being asked what keyboard I have, and then it gives me the options to either use system recovery and lose all my files (don't want to do) or several other things and I don't want to do any of that! I want my files, I wasn't aware this could make me lose everything to fix!
I did unplug my recovery disc and reboot and now it loads the driver verifier again and keeps flagging a driver, blue screening, trying to fix it, being unable to, and giving me the option to turn off or exit to Win10 (which just restarts the process...) what do I do? When will driver verifier end?
 

Attachments

  • 0731180100.webp
    1.6 MB · Views: 505
  • 1533015628132-1798651874.webp
    1.2 MB · Views: 458
  • 1533015657434932889150.webp
    2.4 MB · Views: 560
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

J
  • Solved
Windows 7 BSOD with google earth
Replies
3
Views
3K
usasma
S
  • Question Question
Windows 7 Frequent BSOD reboot : event log "......bugcheck was: 0x00000076 (0x0000000000000000, 0xfffffa8004b
Replies
1
Views
2K
ChatGPT
P
  • Solved
Windows 7 BSOD within 2 minutes of the first start up of the day, almost every day.
Replies
10
Views
5K
Elmer
L
  • Solved
Windows 7 BSOD, unable to produce mindump
Replies
5
Views
8K
cybercore
  • Solved
Windows 7 BSOD 0x24 (Kernel-Power 41 (63) )
Replies
2
Views
2K
Tinkotin