Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen of Death (Driver IRQL not less or equal)


  • Please log in to reply
4 replies to this topic

#1 emretwolf

emretwolf

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:11 AM

Posted 06 January 2017 - 01:37 AM

This is bluescreenwiewer report. How can i fix it?

It happens when I leave the computer idle for a long time

 

 

==================================================
Crash Time        : 5.01.2017 23:24:16
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Caused By Driver  : Netwbw02.sys
Caused By Address : Netwbw02.sys+3f4d2
File Description  : Intel® Wireless WiFi Link Driver
Product Name      : Intel® Wireless WiFi Link Adapter
Company           : Intel Corporation
File Version      : 18.33.5.1
Processor         : x64
Crash Address     : ntoskrnl.exe+14a6f0
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\010617-21359-01.dmp
==================================================

==================================================
Crash Time        : 5.01.2017 12:47:35
Bug Check String  : DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug Check Code    : 0x000000c9
Caused By Driver  : kinonih.sys
Caused By Address : kinonih.sys+b174
File Description  : KinoConsole
Product Name      : KinoConsole
Company           : Kinoni
File Version      : 1.0.0.103 built by: WinDDK
Processor         : x64
Crash Address     : ntoskrnl.exe+14a6f0
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\010517-14312-01.dmp
==================================================

==================================================
Crash Time        : 2.01.2017 09:45:34
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Caused By Driver  : Netwbw02.sys
Caused By Address : Netwbw02.sys+3f4d2
File Description  : Intel® Wireless WiFi Link Driver
Product Name      : Intel® Wireless WiFi Link Adapter
Company           : Intel Corporation
File Version      : 18.33.5.1
Processor         : x64
Crash Address     : ntoskrnl.exe+14a6f0
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\010217-23734-01.dmp
==================================================
 



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:11 AM

Posted 06 January 2017 - 06:58 AM

Start by uninstalling KinoConsole and see if that helps.

 

If it doesn't, then please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.
 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 emretwolf

emretwolf
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:11 AM

Posted 06 January 2017 - 11:49 AM

Okey this is it.

Attached Files


Edited by emretwolf, 06 January 2017 - 11:58 AM.


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:11 AM

Posted 07 January 2017 - 06:01 AM

Your UEFI/BIOS (version 5.30) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

C: drive only has about 3% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

The memory dumps seem to blame your wireless networking (but the Driver Verifier memory dump doesn't confirm this)

This could be either a hardware or a software problem.

Start by updating all of your networking drivers (wireless, wired, and bluetooth) to the latest, W10 compatible versions.

If that doesn't stop the BSOD's, then I wonder if this is a hardware issue.  Please post back if this is the case, as troubleshooting hardware issues on laptops isn't easy (you may be able to remove/replace the wifi card, but each model is different).

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Thu Jan  5 15:24:16.523 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010617-21359-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 3:03:35.321
*** WARNING: Unable to verify timestamp for Netwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys
Probably caused by :Netwbw02.sys ( Netwbw02+3f4d2 )
BugCheck D1, {108, 2, 0, fffff8054e7ef4d2}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000108, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8054e7ef4d2, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_Netwbw02!unknown_function
CPUID:        "Intel® Core™ i7-5500U CPU @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
  BIOS Version                  5.30
  BIOS Release Date             03/25/2016
  Manufacturer                  TOSHIBA
  Baseboard Manufacturer        FF50
  Product Name                  SATELLITE L50-C
  Baseboard Product             06F2                            
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  5 04:47:35.354 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010517-14312-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 0:00:10.226
*** WARNING: Unable to verify timestamp for kinonih.sys
*** ERROR: Module load completed but symbols could not be loaded for kinonih.sys
Probably caused by :memory_corruption
BugCheck C9, {21f, fffff809b2d0b174, fffff102eccbcdc0, 0}
BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
Arguments:
Arg1: 000000000000021f, A driver has not filled out a dispatch routine for a required IRP major function.
Arg2: fffff809b2d0b174, The address in the driver's code where the error was detected.
Arg3: fffff102eccbcdc0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR:  0xc9_21f
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
CPUID:        "Intel® Core™ i7-5500U CPU @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
  BIOS Version                  5.30
  BIOS Release Date             03/25/2016
  Manufacturer                  TOSHIBA
  Baseboard Manufacturer        FF50
  Product Name                  SATELLITE L50-C
  Baseboard Product             06F2                            
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  2 01:45:34.282 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010217-23734-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 18:35:22.063
*** WARNING: Unable to verify timestamp for Netwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
Probably caused by :Netwbw02.sys ( Netwbw02+3f4d2 )
BugCheck D1, {108, 2, 0, fffff802ab4ef4d2}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000108, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff802ab4ef4d2, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_Netwbw02!unknown_function
CPUID:        "Intel® Core™ i7-5500U CPU @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
  BIOS Version                  5.30
  BIOS Release Date             03/25/2016
  Manufacturer                  TOSHIBA
  Baseboard Manufacturer        FF50
  Product Name                  SATELLITE L50-C
  Baseboard Product             06F2                            
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Thu Jan  5 15:24:16.523 2017 (UTC - 5:00)**************************
npf.sys                     Thu Feb 28 20:31:24 2013 (513004EC)
ScpVBus.sys                 Sun May  5 17:31:26 2013 (5186CFAE)
monblanking.sys             Wed Oct  1 07:43:38 2014 (542BE8EA)
iwdbus.sys                  Fri Oct  3 20:31:12 2014 (542F3FD0)
cpuz138_x64.sys             Thu Feb 26 02:04:34 2015 (54EEC582)
dtultrascsibus.sys          Thu Mar 26 22:06:54 2015 (5514BB3E)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
QIOMem.sys                  Tue May  5 01:40:35 2015 (554857D3)
dtultrausbbus.sys           Mon Jun  8 06:48:49 2015 (55757311)
TVALZ_O.SYS                 Wed Sep  9 11:41:43 2015 (55F05337)
tosrfec.sys                 Mon Mar  7 04:43:53 2016 (56DD4D59)
tap0901t.sys                Tue Apr 26 18:18:13 2016 (571FE925)
ETD.sys                     Thu May 19 23:19:59 2016 (573E825F)
Thotkey.sys                 Sun Jun  5 23:22:45 2016 (5754EC85)
edevmon.sys                 Thu Jun  9 06:05:37 2016 (57593F71)
kinonih.sys                 Wed Jun 22 03:13:57 2016 (576A3AB5)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
xusb22.sys                  Fri Jul 15 22:28:13 2016 (57899BBD)
CHDRT64.sys                 Fri Jul 22 04:59:34 2016 (5791E076)
RtsP2Stor.sys               Mon Aug 15 03:38:21 2016 (57B1716D)
iaStorA.sys                 Tue Aug 23 11:15:14 2016 (57BC6882)
rt640x64.sys                Fri Oct  7 05:24:19 2016 (57F769C3)
Netwbw02.sys                Sun Oct  9 12:00:54 2016 (57FA69B6)
idmwfp.sys                  Mon Oct 10 12:14:56 2016 (57FBBE80)
ibtusb.sys                  Mon Nov 14 19:31:48 2016 (582A5774)
TeeDriverW8x64.sys          Wed Nov 16 14:50:53 2016 (582CB89D)
nvvad64v.sys                Fri Nov 25 10:43:56 2016 (58385C3C)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
igdkmd64.sys                Fri Dec 16 15:48:32 2016 (58545320)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  5 04:47:35.354 2017 (UTC - 5:00)**************************
igdkmd64.sys                Mon Jun 13 13:27:48 2016 (575EED14)
TeeDriverW8x64.sys          Thu Sep 15 13:08:03 2016 (57DAD573)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  2 01:45:34.282 2017 (UTC - 5:00)**************************
NvStreamKms.sys             Mon Jan 12 12:56:42 2015 (54B40ADA)
nvlddmkm.sys                Thu Aug 25 16:31:18 2016 (57BF5596)
ibtusb.sys                  Thu Oct 13 18:46:55 2016 (58000EDF)


http://www.carrona.org/drivers/driver.php?id=npf.sys
http://www.carrona.org/drivers/driver.php?id=ScpVBus.sys
monblanking.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys
dtultrascsibus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=QIOMem.sys
dtultrausbbus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=TVALZ_O.SYS
http://www.carrona.org/drivers/driver.php?id=tosrfec.sys
http://www.carrona.org/drivers/driver.php?id=tap0901t.sys
http://www.carrona.org/drivers/driver.php?id=ETD.sys
http://www.carrona.org/drivers/driver.php?id=Thotkey.sys
http://www.carrona.org/drivers/driver.php?id=edevmon.sys
kinonih.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=CHDRT64.sys
http://www.carrona.org/drivers/driver.php?id=RtsP2Stor.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
http://www.carrona.org/drivers/driver.php?id=idmwfp.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys

.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 emretwolf

emretwolf
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:11 AM

Posted 07 January 2017 - 09:28 AM

I did what you said. I have not encountered any problems for now. Really thank you so much. If the problem repeats then I will write here


Edited by emretwolf, 07 January 2017 - 09:37 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users