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

BSOD after sleep mode - netio.sys error


  • Please log in to reply
16 replies to this topic

#1 haikubot

haikubot

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 24 May 2014 - 11:10 AM

I got a BSOD today after waking the pc from sleep mode, so the most recent crash dump is probably most relevant - it highlights a problem with netios.sys.   

Does anyone have any idea what conflicts I have in my system, or what drivers might need updating?

 

Here's the data gathered from my pc:

 

Crashdump: https://www.mediafire.com/?dj5d9vmbqjjlj4o

Speccy: http://speccy.piriform.com/results/hJpwQwu4lDCEOQEAdMatT6d

Minitoolbox result: https://www.mediafire.com/?dj5d9vmbqjjlj4o

 

 

Other issues which may or may not be related:

  • no keyboards or mice that I tried are recognized during bootup, but they're fine in windows and in bios.   I can get into bios a number of ways with the motherboard, which helps.  legacy usb support during boot is enabled in bios.
  • bluetooth - my wireless keyboard and mouse work fine, but they take a little while to be recognized once the windows logon screen appears.  There might be a conflict with the onboard bluetooth support, which I disabled in bios, as it recognizes, but doesn't really support my keyboard/mouse.

Let me know if you need additional info or diagnostics.  I've run usbview and get some confusing results, but don't want to overload this post.

Thanks!


Edited by haikubot, 25 May 2014 - 11:07 AM.


BC AdBot (Login to Remove)

 


#2 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 26 May 2014 - 11:21 AM

Hi all - can anyone help?  I got another BSOD today when trying to wake from sleep mode.  

 

I've uploaded a new Crashdump zip file including today's crash: https://www.mediafire.com/?wfr11qu2s99dzoy

 

The dump file gave me this info:

 
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
 
and
 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

 

Could the issue be related to my DiNovo Media bluetooth mouse and keyboard (and bluetooth hub)?  Logitech no longer supports these, but the setPoint installation package which installs the drivers is on the Logitech site.   


Edited by haikubot, 26 May 2014 - 11:38 AM.


#3 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 12:22 PM

help!  Crashing again today when trying to resume from sleep mode - I'm uninstalling the Logitech software and boxing up the wireless mouse, keyboard and bluetooth hub to see if that makes a difference.  Too bad, as I really like the wireless keyboard.

 

In any case, I'll see if this helps - if anyone is able to advise what's happening based on the data I've uploaded, it will be much appreciated.  :-)



#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,873 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:59 PM

Posted 27 May 2014 - 02:56 PM

Let's try the following for some data.

 

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

 

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

 

Save the report as BSOD.txt.

 

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

 

Louis



#5 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 05:06 PM

Hi Louis, thanks for responding - hope the issue is something straightforward!

Here's the result of the BlueScreenView scan:

 

==================================================
Dump File         : 052714-13291-01.dmp
Crash Time        : 5/27/2014 2:12:45 AM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x0000009f
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`224c3af0
Parameter 3       : fffff800`04f383d8
Parameter 4       : fffffa80`2276d010
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052714-13291-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,544,096
Dump File Time    : 5/27/2014 8:58:55 AM
==================================================
 
==================================================
Dump File         : 052614-14040-01.dmp
Crash Time        : 5/26/2014 2:48:43 AM
Bug Check String  : DRIVER_CORRUPTED_EXPOOL
Bug Check Code    : 0x000000c5
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`033b4a9b
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052614-14040-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 294,832
Dump File Time    : 5/26/2014 8:46:04 AM
==================================================
 
==================================================
Dump File         : 052414-13291-01.dmp
Crash Time        : 5/24/2014 6:19:41 AM
Bug Check String  : DRIVER_CORRUPTED_EXPOOL
Bug Check Code    : 0x000000c5
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`033b6147
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052414-13291-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 294,840
Dump File Time    : 5/24/2014 6:28:09 AM
==================================================
 
==================================================
Dump File         : 052314-13104-01.dmp
Crash Time        : 5/23/2014 1:02:15 AM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x0000009f
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`20b6ccd0
Parameter 3       : fffff800`04b383d8
Parameter 4       : fffffa80`1c74d230
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052314-13104-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,580,520
Dump File Time    : 5/23/2014 1:57:02 AM
==================================================
 
==================================================
Dump File         : 051914-13213-01.dmp
Crash Time        : 5/19/2014 10:26:32 AM
Bug Check String  : 
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`1ccca028
Parameter 3       : 00000000`be200000
Parameter 4       : 00000000`000b110a
Caused By Driver  : hal.dll
Caused By Address : hal.dll+12a3b
File Description  : Hardware Abstraction Layer DLL
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\051914-13213-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 294,776
Dump File Time    : 5/19/2014 11:49:17 AM
==================================================
 
Again, thanks for your help troubleshooting!  


#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,873 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:59 PM

Posted 27 May 2014 - 05:41 PM

Nothing useful there...trial and error, as you were doing, may be the only way.

 

Louis



#7 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 06:03 PM

Thanks, Louis.  Any hints as to which direction I should take for trial and error?  

 

Should I be looking at motherboard hardware driver updates, for instance?  Just for fun, I've updated all the mobo-related drivers listed for this motherboard on the Asus website.  That includes probably unlikely candidates like the chipset controller.  

 

By the way, windows just popped up a "Device driver software was not successfully installed" with the unhelpful information: "unidentified device" and no driver found.   I'm not at all sure what device this could be referring to.   I even checked the wired keyboard (Logitech K120) on Logitech's support site and found that no drivers are needed for this usb keyboard.  I'm no longer using any bluetooth devices, and uninstalled the Logitech setpoint software (installs the bluetooth drivers, etc.) so I assume that's not the issue.

 

Finally, I have a very mild overclock that was handled by AI Suite 3, and again, I assume that isn't causing these problems, though I have seen posts recommending that folks only use Bios to overclock.  

 

Just so you have the full picture.  Again, much appreciated.


Edited by haikubot, 27 May 2014 - 07:12 PM.


#8 Roodo

Roodo

  • Members
  • 760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:59 AM

Posted 27 May 2014 - 08:07 PM

You should be looking for a new Power Supply.



#9 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 08:11 PM

You should be looking for a new Power Supply.

Thanks, Roodo.. it's a brand new power supply (evga super nova 1300 g2) - why do you think I should get a new one?



#10 Roodo

Roodo

  • Members
  • 760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:59 AM

Posted 27 May 2014 - 08:40 PM

What devices do you have externally installed on the computer?



#11 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 08:56 PM

What devices do you have externally installed on the computer?

Just a usb keyboard and microsoft optical mouse.

 

It was interesting that after installing the sata driver updates, and rebooting, windows acted like I'd just connected one of the internal drives (asked me would I like to open it with Lightroom or Picasa).   I also installed a driver for the monitor, which had been recognized as a standard pnp monitor rather than the Dell u2713hb.



#12 Roodo

Roodo

  • Members
  • 760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:59 AM

Posted 27 May 2014 - 09:04 PM

Did you update the bios as well?



#13 Frozwire

Frozwire

  • Members
  • 80 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:59 PM

Posted 27 May 2014 - 09:17 PM

You may try disabling the Intel C State Option in your BIOS if it is set to Auto.


"Encryption...is a powerful defensive weapon for free people. It offers a technical guarantee of privacy, regardless of who is running the government... It's hard to think of a more powerful, less dangerous tool for liberty...” - Esther Dyson


#14 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 09:21 PM

Yes, the bios is the latest, which I updated when I installed win 7.    I was hoping that would allow a keyboard to be recognized during bootup, but it didn't affect anything.   The bios is set to recognize legacy usb as well as keyboard/mouse input during boot.


You may try disabling the Intel C State Option in your BIOS if it is set to Auto.

Cool idea - thanks, Frozwire.  


Edited by haikubot, 27 May 2014 - 10:50 PM.


#15 haikubot

haikubot
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:10:59 AM

Posted 27 May 2014 - 09:53 PM

Sounds like C state in auto is useful for sleep / hibernate mode (and the power bill): http://rog.asus.com/forum/archive/index.php/t-23675.html.

I'd like to do a bit more research later today... 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users