Windows 10: BSOD ntkrnlmp.exe ( nt!KiSystemServiceExitPico+1f2 )

Hi!

I've been having BSOD's for quite some time now. While messing around with Drive Verifier I solved some issues with KillerNetworking drivers, but now I seem to be stuck on Kernel errors and can't go any further on investigating.

I already suspected of hardware fault and sent the laptop to the store claiming hardware fault. On their end, they said they ran every possible test and benchmark (Witcher 3 and other abusive games, as well as other tests), without any errors, so it leaves me to think it's drivers.

The errors appear to be more frequent when gaming, although sometimes happen during lighter usage (writing reports, browsing, etc).

I'm attaching the latest dmp's I generated in case someone finds something.

Thanks in advance! Best redumps.zipgards

:)

 

BSOD

BugCheck 4A, {53c921cc, 1, 0, ffffcc0045c31b80}

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExitPico+194 )

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_audiostudio100.exe_nt!KiSystemServiceExitPico

audiostudio100.exe associated with Sound Forge Audio Studio software.

if you have anything of that you need to remove it.

 

APC Index Mismatch

Hi Siri,

Here is some information from the dump files (the error is consistent across all dump files):

BugCheck 1, {7ffc85425ca4, 0, fffe, ffffc381af0b5b80}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExitPico+194
)

BUCKET_ID: 0x1_SysCallNum_7_nt!KiSystemServiceExitPico

STACK_TEXT:

ffff8a00`b5fef948 fffff801`f51e9929 : 00000000`00000001 00007ffb`3f155ca4 00000000`00000000 00000000`0000fffe : nt!KeBugCheckEx

ffff8a00`b5fef950 fffff801`f51e982b : ffffb18c`70c14080 00000065`994fdcf8 ffff8a00`b5fefaa8 00000000`00000018 : nt!KiBugCheckDispatch+0x69

ffff8a00`b5fefa90 00007ffb`3f155ca4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x194

00000065`994fdca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`3f155ca4

This appears to be the same as the error reported in the following link:

Enable filenames with colon (:) on drvfs · Issue #1514 · Microsoft/WSL

Apparently, according to a post in the link, this is an
IOCTL locking issue and there should be a fix in the next Windows Insider build.

@Claudio Casonato - the error you are experiencing is also the same.

 

One of the dumps shows a problem with WmBEnum.sys which is a Logitech wingman driver:

WmBEnum.sys Tue Apr 27 13:10:19 2010

As this is rather old I would try and find an updated driver.

Please provide a full set of logs so that we can help further.

 

Thanks for the fast reply. Already attached the logs, sorry for missing that.

That Logitech driver is most likely my G27 Driving Wheel software. This OS was freshly installed just a week ago, I installed the latest there was on their website. I'll try and look again. Maybe it is worth mentioning that the latest errors I uninstalled SoundBlasterX software as it appeared in "PROCESS NAME" in one of the dumps, just for testing.

 

Just did a fresh install, and in an hour 3 Orange Screens (?), all related to a system file, within an hour of trying to run the Benchamark mode of DiRT Rally. Not to mention various times it just closed the game like it crashed.

Should I just let Windows install all the drivers and? I'm completely lost here...

 

Yes, Windows 10 will usually find 90% of the drivers but look in device manager for any devices that still have a yellow exclamation mark - these drivers will need to be obtained directly from the manufacturers website. Do not use an automatic driver update program - these can sometimes load incorrect drivers or install unwanted items in parallel.

I'm not sure what an orange screen is - unless this was a graphics problem?

 

I never used automatic driver updates. There are no exclamation marks, I downloaded every driver from the provider, and tried to look for updated versions of them.

It mostly happens when gaming, yes, although it happened in other occasions before. An orange screen is just a BSOD with an orange background, as simple as that. Even the errors and bugchecks are the same. The logs I attached before were from these Orange Screens.

 

The logs are in a foreign language and cannot be scanned or read.
Please change the default language to English and re-post the zip for troubleshooting:
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials
log collector v2-beta06.zip

 

Changed the language, fresh install, new couple errors. Sry for the delayDESKTOP-KIOD9PF-18_01_2018_175851_28.zip

 

There were 3 BSOD mini dump files debugged.
Windows driver verifier is tool that is used to find misbehaving drivers.
It will stimulate drivers producing repetitive BSOD until all misbehaving drivers are fixed or until the tool is turned off.
When using the tool you will need to know how to turn the tool off after each BSOD.
There are 3 methods using the Windows advanced troubleshooting menu:
1) startup options > restart > select #6 safe mode with command prompt:
type: verifier /reset
2) command prompt > Administrator: X:\widnows\system32\cmd.exe > X:\Sources>
type: verifier /bootmode resetonbootfail
3) system restore
The methods to turn of the tool should be used in sequence only if the prior command fails.
Using system restore often leads to loss of the BSOD mini dump file and little progress is made in the troubleshooting.
Before using the tool backup files, make a backup image and make a brand new restore point.
Macrium Software | Your Image is Everything (free edition)
Use this link for the test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Use this link for the method to turn off the tool:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
After each BSOD please post a new zip for troubleshooting:
log collector v2-beta08.zip