Page 4 of 5 FirstFirst ... 2345 LastLast
  1.    02 Jul 2017 #31
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    Quote Originally Posted by Carnival View Post
    Windows isn't changing the driver that I downloaded from Asus's site, the same one is just showing up right after I reboot or if I uninstall it and try to install the one from Asus. It doesn't matter whether I'm disconnected from the internet or not, if I uninstall it, it just shows up again. I've been downloading the latest driver they have so maybe I'm at fault in some way here. I'm going to try rolling back.
    This situation tells me that you have files in your C:\Windows\INF directory that are telling the OS which drivers to install and it is happening as soon as you boot up. If you look in that directory you will see various *.inf files for many of the devices attached to your PC. There may even be a rtwlane.inf file. Try moving this file to somewhere else to stop it working.

    You could also look in the C:\Windows\System32\Drivers directory and remove the rtwlane.sys file if it is there.

    Doing this should prevent the same driver being reinstalled and enable you to load the driver you want.

    As you are playing around in the system files you should make sure you have restore points and system backups in place in case anything goes wrong. Let me know if you need directions for restore points or backups but there are plenty of tutorials that cover these areas.
      My ComputersSystem Spec
  2.    02 Jul 2017 #32
    Join Date : Jun 2017
    Posts : 23
    Windows 10
    Thread Starter

    @philc43 So I should just move the file, not delete it?

    Also, I tried downloading the latest driver for the Lan PCI-E whatever and I'm still getting BSODs.
    To test out if I'll get a BSOD or not I just let an hour long stream go on my computer while I did something else.
    It only got 39:51 in before BSOD'ing.
    I wanted to see if maybe there was a difference between downloading it directly from Asus and Realtek but the results the same for me, I guess.

    I'll try rolling back while also doing what you suggested.

    DM Log:
    https://5.lithi.io/qc6zUJ.zip
    @zbook
    Do these Event Viewer and WhoCrashed things help anything really?
    I want to hope they help or mean something at least.
    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Sun 7/2/2017 3:12:20 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\070217-31062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800BF475348)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 7/2/2017 3:12:20 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: rtwlane.sys (rtwlane+0x306C4)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800BF475348)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\WINDOWS\system32\drivers\rtwlane.sys
    product: Realtek PCIEWireless LAN PCI-E NIC
    company: Realtek Semiconductor Corporation
    description: Realtek PCIE NDIS Driver 52611 27170
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtwlane.sys (Realtek PCIE NDIS Driver 52611 27170, Realtek Semiconductor Corporation ).
    Google query: Realtek Semiconductor Corporation DPC_WATCHDOG_VIOLATION






      My ComputerSystem Spec
  3.    02 Jul 2017 #33
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    The advantage of moving it is that you can put it back again if you make a mistake.
      My ComputersSystem Spec
  4.    02 Jul 2017 #34
    Join Date : Jun 2017
    Posts : 23
    Windows 10
    Thread Starter

    I cut the rtwlane.sys file out of where it originally was and just put it in my desktop for the time being.
    So now I can just uninstall the realtek stuff with the device manager and it should work, right?
    Ideally speaking.
      My ComputerSystem Spec
  5.    02 Jul 2017 #35
    Join Date : Jun 2017
    Posts : 23
    Windows 10
    Thread Starter

    Still no good, I moved the sys file out onto my desktop yet the moment I tried installing this:

    The same drivers just came back. I'm pretty sure Qualcomm Atheros and Realtek aren't the same thing so I guess Windows can still bring back these same drivers no matter how many times I uninstall them and delete all their data.

    I tried just about all the ones here and still I get the same one.


    This same driver keeps popping up no matter what I do.
    The PCIE GB Family Controller thing comes along with it as well.

    I will be really bummed out if I have to reinstall Windows on this computer. I hate getting back all my backed up stuff. Not to mention Windows will probably just force me to update to this same broken update and put me back in the same situation. I don't want to have to speak to a support person on the phone about this because I really don't believe they'll be of any help either.
      My ComputerSystem Spec
  6.    02 Jul 2017 #36
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    I think I would have chosen the next one down on the list, your MB is not the Kabylake.
      My ComputersSystem Spec
  7.    02 Jul 2017 #37
    Join Date : Jun 2017
    Posts : 23
    Windows 10
    Thread Starter

    Well, I downloaded the "Wireless Driver for M32CD"
    And to my confusion it looks just like the one I already had....Which is what I'm assuming because absolutely nothing has changed. Either Realtek loves the name of this thing or Windows really enjoys putting me over a barrel with this constant magical reappearance of this driver after I uninstall it.
    I guess I'll just let some YouTube videos play for a bit and come back to see if it blue screens within a few hours.
    Hopefully this one rollback finally made the difference...or maybe I'm wasting my time.
      My ComputerSystem Spec
  8.    02 Jul 2017 #38
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    Hi Carnival,

    Lets hope it has made a difference. You have to dig a bit deeper in Device Manager to actually see if the driver has changed.

    Let me show you the screens for my Network driver:

    Attachment 142209

    Double-click and select the driver tab to show this:
    Attachment 142210

    Click the driver details button to show the driver details:
    Attachment 142211
      My ComputersSystem Spec
  9.    02 Jul 2017 #39
    Join Date : Jun 2017
    Posts : 23
    Windows 10
    Thread Starter

    @philc43


    Here you go, there are no obvious changes like a name change or something so I'm a bit lost on how to dig deeper into this.

    I'm not sure if this means anything but apparently what I downloaded is from 2015:

    My drivers were up to date last time I checked but hey, no reason to still not check, better safe than sorry.
      My ComputerSystem Spec
  10.    02 Jul 2017 #40
    Join Date : Jun 2017
    Posts : 23
    Windows 10
    Thread Starter

    I've been letting YouTube videos play since 5:32 PM and nothing has happened yet.
    It's way too early to say it's fixed since it likes to act up when I least expect it.
    Things have been good so far though.
      My ComputerSystem Spec

 
Page 4 of 5 FirstFirst ... 2345 LastLast


Similar Threads
Thread Forum
DPC Watchdog Violation BSOD
This weekend I had an issue with the computer and after a while traced it to the RAM being either not seated properly or too dusty. Cleaned it, reseated it. We seem to be good, but GPU was acting wonky, so redownloaded driver from Manufacturer and...
BSOD Crashes and Debugging
DPC Watchdog Violation
Hello there Now I receive a constant BSOD DPC Watchdog Violation every time I start my pc and pc seems to work fine after restarting ,I included the files in the post
BSOD Crashes and Debugging
DPC Watchdog Violation. Help!
Hi I get these random DPC watchdog violation error either at startup or from resuming from hibernation or sleep. I've attached the file Hope someone can help Ty!
BSOD Crashes and Debugging
Windows 10 RTM freezing constantly and loops/repeats sound
So the problem I've been having with Windows 10 is that it is constantly freezing on me and loops the sound over and over until it unfreezes. The computer is unresponsive and acts like it is about to bluescreen but it doesn't. After it unfreezes, it...
General Support
Solved DPC Watchdog Violation
So since installed win 8.1 i can`t shutdown my pc normaly i have to press and hold the power button , if i put him to sleep it will not come back and usually gives me this BSOD after 2-10 min. Please help!12631
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:23.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums