Random BSOD's seeming to point to netio.sys


  1. Posts : 7
    Windows 7 64-bit
       #1

    Random BSOD's seeming to point to netio.sys


    I'm having random BSOD's on my wife's new Compaq CQ5210F with Windows 7 64-bit. Almost all dump files seem to point to netio.sys
    There seems to be no particular pattern to the crashes...5 one day, none for a week, etc., not tied to any particular activity.
    I've tested the memory overnight using recommended tools and the memory is fine. I've checked HP's site for updated networking drivers as the dumpfile seems to suggest a networking issue, but there are none newer than what it shipped with.
    Thanks for your help!
    Zipped minidump files attached.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    charlesdhartman said:
    I'm having random BSOD's on my wife's new Compaq CQ5210F with Windows 7 64-bit. Almost all dump files seem to point to netio.sys
    There seems to be no particular pattern to the crashes...5 one day, none for a week, etc., not tied to any particular activity.
    I've tested the memory overnight using recommended tools and the memory is fine. I've checked HP's site for updated networking drivers as the dumpfile seems to suggest a networking issue, but there are none newer than what it shipped with.
    Thanks for your help!
    Zipped minidump files attached.

    Hey and welcome

    Well it seems like you have two distinct types. Power State, and Kernal Mode Trap.
    Power state is usually device like a drive, or usb device. Kernal mode trap is usually a driver.

    Since you have tested the memory, and no signs of networking issues are epressed in the dmps You are going to have to start looking at them.
    Start with a chkdsk/f for the HD
    you can go here for more info. http://www.carrona.org/hddiag.html

    let us know the results

    Ken J+

    Code:
    122509-34101-01.dmp    12/25/2009 3:49:06 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`022f9060    fffff800`00b9c518    fffffa80`05d9e1d0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    122609-15116-01.dmp    12/26/2009 10:28:20 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`022f9060    fffff800`00b9c518    fffffa80`03383d30    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    123009-16489-01.dmp    12/30/2009 3:11:14 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`022f9060    fffff800`00b9c518    fffffa80`0283f0e0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    010410-16099-01.dmp    1/4/2010 8:31:16 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`022f9060    fffff800`00b9c518    fffffa80`05e59260    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    122809-15584-01.dmp    12/28/2009 7:39:48 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`034e0609    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    123109-16052-01.dmp    12/31/2009 7:37:30 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`0348a89b    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    123109-16988-01.dmp    12/31/2009 7:57:20 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`0349589b    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    123109-16598-01.dmp    12/31/2009 8:00:04 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`034813f0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    123109-15787-01.dmp    12/31/2009 8:07:40 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`02885609    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    010210-17784-01.dmp    1/2/2010 3:16:42 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`03487609    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    010510-15288-01.dmp    1/5/2010 7:32:08 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`03488609    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    011010-17019-01.dmp    1/10/2010 7:04:02 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`03494609    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    011010-15584-01.dmp    1/10/2010 7:47:18 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`034dd609    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    011010-14180-01.dmp    1/10/2010 9:55:44 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`0348289b    ntoskrnl.exe    ntoskrnl.exe+71f00                    
    011010-12994-01.dmp    1/10/2010 10:37:52 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`8005f031    00000000`000006f8    fffff800`03481609    ntoskrnl.exe    ntoskrnl.exe+71f00
    Code:
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\New folder (3)\011010-14180-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0340b000 PsLoadedModuleList = 0xfffff800`03648e50
    Debug session time: Mon Jan 11 00:53:57.394 2010 (GMT-5)
    System Uptime: 0 days 2:06:58.971
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 8005f031, 6f8, fffff8000348289b}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 000000008005f031
    Arg3: 00000000000006f8
    Arg4: fffff8000348289b
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000347c469 to fffff8000347cf00
    
    STACK_TEXT:  
    fffff880`009eac68 fffff800`0347c469 : 00000000`0000007f 00000000`00000008 00000000`8005f031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`009eac70 fffff800`0347a932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`009eadb0 fffff800`0348289b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0696ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepAccessCheck+0x8b
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`0347a932 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 7
    Windows 7 64-bit
    Thread Starter
       #3

    Thanks for the reply! Chkdsk found nothing. I'll run Hitachi's diagnostics and post the results back.
      My Computer


  4. Posts : 7
    Windows 7 64-bit
    Thread Starter
       #4

    Thanks again for looking at the crash files!

    I ran Hitachi's disk diagnostics (advanced scan) and everything, as expected, came back clean.

    If this is pointing to a driver problem, are there any clues from the dump files as to what driver(s) might be the culprit?
      My Computer


  5. Posts : 7
    Windows 7 64-bit
    Thread Starter
       #5

    Help! 10 more crashes in 1 day!


    Computer has been crashing incessently today. The dump files look very similar. I've checked the hard drive as Ken J+ recommended and it was clean. Where do I go from here? New dump files attached.
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    The dump files appear to point to networking (NETIO.SYS) - so I'd suspect either your networking drivers, or problems with your networking device(s). Several of the dumps point to nvmf6264.sys (dated Thu Jul 30 19:48:18 2009) - a component of your nVidia nForce networking drivers.

    The point here is to replace the drivers. That's because we suspect the currently installed drivers to be corrupted. So first you uninstall them (to hopefully remove the corruption), then install a fresh copy of the latest available drivers.

    Please download the latest version of the nVidia nForce drivers from here: NVIDIA DRIVERS 15.49 WHQL
    Then uninstall the current nForce drivers from your system.
    You'll notice that the drivers that you downloaded are Vista drivers - so please install them using this procedure:
    Compatibilty Mode Driver Installation:
    1 - Download the latest driver from the manufacturer's website.
    2 - Uninstall the current drivers using the Control Panel...Programs and features...Uninstall a program applet. Then verify that the driver/device has been removed in Device Manager
    3 - Right click on freshly downloaded driver installation file and select "Properties"
    4 - Select the Compatibility tab - and do the following:
    - Click on the "Change settings for all users" button
    - Click on the box to select "Run this program in compatibility mode for" and then select Windows Vista Service Pack 1
    - Click on the box to select "Run as administrator"
    - Click on OK to exit all the dialogs
    5 - Right click on the driver installation file and select "Run as administrator"
    6 - Let it install and see if that stops the BSOD's.
    Also, please update this driver: USBAVCap.sys Thu May 10 03:33:49 2007
    It's a component of your AVerMedia USB Video Capture Driver (http://www.avermedia.com/avertv/Support/Download.aspx?Type=Software)

    Here's a summary of the BSOD's:
    Code:
    BugCheck 9F, {3, fffffa80022f9060, fffff80000b9c518, fffffa8005e59260}
    Probably caused by : nvmf6264.sys
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff80003488609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff80003494609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff800034dd609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff8000348289b}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff80003481609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff8000348a609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 9F, {3, fffffa80022faa20, fffff800047ea518, fffffa8004adaca0}
    Probably caused by : nvmf6264.sys
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff8000348a609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff800034d6609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff800034da89b}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff800034df609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff80003483609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff8000348a89b}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff8000348a609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 7F, {8, 8005f031, 6f8, fffff800034dd609}
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
      My Computer


  7. Posts : 7
    Windows 7 64-bit
    Thread Starter
       #7

    USASMA, thanks so much for analyzing my BSoD problem!

    I've uninstalled and replaced the nvidia drivers as well as updated the Avermedia drivers as you recommended. So far, so good, (no BSoD's yet), but with the randomness of the crashes, it will be several days before I can say for sure that the problem is solved.

    I will post back here in several days if everything is stable. Thanks again!
      My Computer


  8. Posts : 7
    Windows 7 64-bit
    Thread Starter
       #8

    Problem fixed!


    Replacing the nVidia drivers seemed to do the trick. Updating the Avermedia drivers caused additional problems. Going back to the older Avermedia drivers resolved the new problems.

    I even ran verifier for 3 days on the new drivers and was not able to cause any crashes.

    Thanks again for diagnosing the problem. You guys are great!
      My Computer


  9. Posts : 1
    Windows 7
       #9

    I have been having this problem since i upgraded my dell studio 1737 from vista. I downloaded the Windows debugger pack & followed the techrepublic.com dojo videos instructions of how to use it & all of my bsod's pointed to the netio.sys file. I went out on a limb & searched the hard disk for the file & moved to recycle bin in frustration & so far so good. I've went to the microsoft site & looked for hot fixes w/ no avail the did windows update. Fingers crossed...I'll report if the symptoms reoccur.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    cblambert said:
    I have been having this problem since i upgraded my dell studio 1737 from vista. I downloaded the Windows debugger pack & followed the techrepublic.com dojo videos instructions of how to use it & all of my bsod's pointed to the netio.sys file. I went out on a limb & searched the hard disk for the file & moved to recycle bin in frustration & so far so good. I've went to the microsoft site & looked for hot fixes w/ no avail the did windows update. Fingers crossed...I'll report if the symptoms reoccur.
    Clambert

    You need to start your own thread, and we need the actual DMP file created during the crash. use these to find it. https://www.sevenforums.com/crash-loc...d-problem.html

    thanks

    Ken
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:46.
Find Us