Windows 10: Bsod 0xD1

Hi i Get a BSOD windows 10 enterprise edition 64bit
HP Elitebook 8460p

crash dump file: C:\Windows\Minidump\041316-22640-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80128D8036C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF80128D8036C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

:)

 

Require technical help with BSOD problems.

Every so often while playing a game i'll get the BSOD, Driver_NOT_LESS_OR_EQUAL 0xD1 ( dmp file 100116-8234-02 included in post).

I'm 'ok' with computers but finding out the cause is giving me some trouble so i'd appreciate any help.

I've ran memory diagnostics and that came back with zero faults, i ran verifier.exe to test my drivers and kept getting BSOD soon after startup, DRIVER_VERIFIER_IOMANAGER_VIOLATION OxC9 (dmp file 100116-11656-01).

Here's my dmp files and system info:

OneDrive

If anyone can take a look at whats causing this, that would be great.

Regards

John

 

Need help with BSOD - driver validation

Hi,

We need more information about the issue.

• When exactly do you get the BSOD error?
• What is the complete BSOD error?
• What is the make and model of the computer?
• Did you make any changes prior to this issue?

Refer the link below for more information.

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL

Hope this helps in resolving the issue. If the issue persists, do get back to us. We will be happy to assist you.

Thank you.

 

*Arrow Blue Screen of Death (BSOD) Posting Instructions

 

the issue is not resolve ...

 

*Arrow Blue Screen of Death (BSOD) Posting Instructions

 

i attach zip file with all info DESKTOP-39KAPRC-Wed_04_13_2016_203501_83.zip

 

How much data it may contain in 22 bytes?

You need to redo the process.

 

i do the processs again and this not allocate info in the zip fille i do same the step in the post ...

 

@almogc, try the batch file version of the MD Log Collector.

Run this as admin. Post the log in your reply post. Attachment 75489

 

Hi almogc

Welcome to the 10forums *Smile

Although there are some problems with the log files, we'll need a few to get some info about your system to get a better idea of what is going on. Please follow below instructions for gathering a few files manually.

Please run "winver" (without quotes) in a search and press enter, this will show a pop-up of the exact Windows version that is installed. Please make a screenshot of it and post it so I know what Windows version we're working with.

Please search for "msinfo32" (without quotes) and open the msinfo32 app,

• save it as msinfo32.nfo,
• in explorer go to the directory where it is saved,
• right click the msinfo32.nfo file,
• choose 'send to' or 'copy to',
• choose 'compressed (zipped) folder'

Attachment 75548

Please run following commands in an admin command prompt, it creates a file called 'systeminfo.txt', it is created with the DM Log Collector and shows some information about your system too but we'll have to do it manually now.
Code: systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp"findstr /v "Owner." "%USERPROFILE%\Desktop\systeminfo.tmp" > "%USERPROFILE%\Desktop\systeminfo.txt" del "%USERPROFILE%\Desktop\systeminfo.tmp"[/quote] Please search "dxdiag" (without quotes), you'll see a pop-up within a few moments.
In this popup you see the DirectX Diagnostic Tool, click on 'Save All Information' and save it as 'dxdiag.txt'
Attachment 75549

Please go in Windows Explorer to following location for the gathering of the minidumps: %systemroot%\minidump
Select all dumps from the last week, right click 1 of them and choose > send to > compressed (zipped) folder naming it as minidumps.

Now that we have a few files, please upload them all, you may put them all together in 1 zip file if you'd like *Smile
You can put them in a zip file by moving them in the same place, select the files > right click 1 of them and choose > send to > compressed (zipped) folder.

To sum up there are a few files gathered
1. msinfo file
2. systeminfo.txt file
3. dxdiag file
4. minidumps

 

hi i attach all logs
thank you

 

Please run in an admin command prompt following command
Code: slmgr /dlv[/quote] a pop-up will show within a few moments, please make a screenshot of it and post it.

Please don't forget to run below commands in an admin command prompt, simply copy/paste it
Code: systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp" findstr /v "Owner." "%USERPROFILE%\Desktop\systeminfo.tmp" > "%USERPROFILE%\Desktop\systeminfo.txt" del "%USERPROFILE%\Desktop\systeminfo.tmp"[/quote] Upload the text file that it outputs.

 

I've asked an activation expert on this matter for a second thought about it and we both agree that the activation is counterfeit.

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Forum rules

 

Absolutely correct - but just to elaborate a bit more regarding the connection between netio.sys (which I assume is a network driver) and the counterfeit app in use - the latter uses a loopback IP to emulate a KMS server response on the local machine - so it's almost certainly the cause for the driver failing.