BSOD ntoskrnl.exe

Page 2 of 2 FirstFirst 12

  1. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #11

    The netr6164.sys driver is a wireless adapter driver. If there is no driver update for netr6164.sys, your wireless adapter is obsolete. Upgrade your network wireless card to one that is Win 7 compatible and uninstall the original. Wireless adapters are inexpensive.
      My Computer


  2. Posts : 43
    Windows 7 Ultimate x64 N Edition
    Thread Starter
       #12

    Hi. Could you possibly take a look at my newest JCGriff tool files. Im not entirely sure if it is netr6164.sys anymore. THanks.
    Attachment 127184
      My Computer


  3. Posts : 43
    Windows 7 Ultimate x64 N Edition
    Thread Starter
       #13

    bump
      My Computer


  4. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #14

    I can't say that it is netr6164.sys causing the problem. The dumps are error code A and that indicates a driver problem. netr6164.sys is a 2007 driver and that is way obsolete. There is nothing new in the dumps. Troubleshooting when no specific causes are give is process of elimination. It is probable that netr6164.sys is the cause; but we won't know for sure until that driver is gone. It certainly has the potential to cause crashes.
      My Computer


  5. Posts : 43
    Windows 7 Ultimate x64 N Edition
    Thread Starter
       #15

    Is it possible that the driver could suddenly just not work? The BSOD was kind of spontaneous which confuses me? Also, do you know if netr6164.sys is used for all network cards or only for ralink? I have a belkin wireless network card and I'm not sure if it uses it.
      My Computer


  6. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #16

    It is not that the driver does not work; it creates conflicts in the system. Conditions including other drivers loaded into memory, stuff being taken out of memory, other things being written to memory can set the stage for a conflict. The conflict may not happen all the time - just under certain conditions. In an extreme case, just the driver loading into memory will cause conflicts and a crash.

    netr6164.sys is a Ralink driver that also used by other manufacturers, but not by all. This is not unusual. If you renamed it and your wireless stopped working, that indicates that it is used by your Belkin adapter. Renaming will break whatever the driver is associated with. I would simply upgrade to a new wireless adapter. I had to do that when I installed Win 7.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 18:25.
Find Us