BSOD upon waking up from hibernation - Windows 8.1 x64

Levont

Levont

Member
Joined
Jul 16, 2014
Posts
7
This issue started coming up to me on 7-15-14 and I would like some expert advice on how to remedy this problem. Thanks in advance.

· OS - Windows 8.1
· x86 (32-bit) or x64 ? (x64)
· What was original installed OS on system? Windows 8
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? It came pre-installed.
· Age of system (hardware) (2 years)
· Age of OS installation - have you re-installed the OS? (Age of OS: 2 years with no re-install)

· CPU: AMD FX(tm)- 4130 Quad Core Processor 3.80 GHz
· Video card: GeForce GT 630
· MotherBoard Asus M5A97 R2.0
· Power Supply - brand & wattage (if laptop, skip this one) (Brand: Allied Wattage: 300W)

· System Manufacturer: Ibuypower
· None. (Custom made computer)
· Desktop

Perfnom/report step didn't work for me. (Stated that it refused), so I don't have a prefnom in the zip

View attachment 8622
 
Hi,

All of the attached DMP files are of the PAGE_FAULT_IN_NONPAGED_AREA (50) bug check.

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Code: 
0: kd> k
Child-SP          RetAddr           Call Site
ffffd000`21c245a8 fffff801`01f9624a [COLOR=#006400]nt!KeBugCheckEx[/COLOR]
ffffd000`21c245b0 fffff801`01e789c9 nt! ?? ::FNODOBFM::`string'+0x20d9a
ffffd000`21c24650 fffff801`01f6f22f [COLOR=#000080]nt!MmAccessFault+0x7a9[/COLOR]
ffffd000`21c24790 fffff801`f1d256c8 [COLOR=#4b0082]nt!KiPageFault+0x12f[/COLOR]
ffffd000`21c24920 00000000`00008401 [COLOR=#ff0000]rtwlanu+0xd56c8[/COLOR]
ffffd000`21c24928 00000000`00000000 0x8401

rtwlanu.sys (Realtek RTLxxxxx Wireless USB 2.0 Adapter driver) referenced invalid system memory, therefore the box bug checked as this cannot occur in kernel-mode.

The driver itself is likely not the cause whatsoever, however something 3rd party working with the network invoked the process of pointing to bad/freed memory.


Remove and replace Norton with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing conflicts:

 Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

Regards,

Patrick
 
Norton is still listed and loaded in the latest crash dump. Please remove it as I advised.

Regards,

Patrick
 
Thanks, however the latest crash dump in that .zip is the same as the one prior. The specific timestamp is Wed Jul 16 15:32:53.248 2014 (UTC - 4:00).

If you really have removed Norton and the system has crashed again after its removal + a full system restart, please attach the newest crash dump by itself as opposed to running the collection app again. You can do this by simply navigating to C:\Windows\Minidump and zipping up the latest crash dump.

Regards,

PAtrick
 
Much appreciated.

Right, so in this dump, Norton is fully removed yet the cause of the crash remains the same - Realtek RTLxxxxx Wireless USB 2.0 Adapter driver. With this said, it's apparent that the driver itself is indeed the problem as opposed to Norton (please don't reinstall Norton now, but after we've solved your BSOD's).

Code: 
0: kd> lmvm rtwlanu
start             end                 module name
fffff800`eaa90000 fffff800`eac88000   rtwlanu  T (no symbols)           
    Loaded symbol image file: rtwlanu.sys
    Image path: \SystemRoot\system32\DRIVERS\rtwlanu.sys
    Image name: rtwlanu.sys
    Timestamp:        Wed Jul 10 10:48:31 [COLOR=#ff0000]2013[/COLOR]

We can see the driver itself is dated from 2013, not too old. However, it still may be incompatible with Windows 8.1 despite its date.

Your next step is to either check for an update from - Realtek or uninstall the software/driver and remove the adapter entirely for troubleshooting purposes. If crashes stop, the adapter's device drivers are unfortunately incompatible, and you'll need to find an alternative.

If however you continue to crash, there's two things I want to take care of:

1.

Code: 
0: kd> lmvm UsbFltr
start             end                 module name
fffff800`e9a32000 fffff800`e9a35000   UsbFltr    (deferred)             
    Image path: \SystemRoot\System32\Drivers\UsbFltr.sys
    Image name: UsbFltr.sys
    Timestamp:        Mon Apr 09 06:09:44 [COLOR=#ff0000]2007[/COLOR]

Your Waytek keyboard drivers are nearly 7 years old, no good. Either remove the keyboard and its software from the picture entirely, or uninstall the software, shut down (not restart), unplug the keyboard, allow Windows to boot, and when you come to the login screen, plug the keyboard in. Hopefully Windows Update won't attempt to download seven year old drivers, and instead the generic Windows keyboard drivers will install. If it does however install old drivers again, do the following:


  • Click Start, right-click Computer, and then click Properties.
  • In the Tasks list, click Advanced System Settings.
  • On the System Properties dialog box, click the Hardware tab, and then click Windows Update Driver Settings.
  • Select Never check for drivers when I connect a device.
  • Click OK twice, and then close the System dialog box.


and then repeat the uninstall, shut down, etc method.

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Regards,

Patrick
 
I'm not sure how this happened. But I did step one of your suggestion by uninstalling the driver and put it to hibernate for five minutes. When I pulled the computer out of hibernate, the adapter reinstalled itself and the BSOD disappeared with it. I tried to bring the BSOD by putting the computer into Hibernate for 30 minutes and pulled it out and I didn't get the BSOD. Did something happened?
 
Levont said:
I'm not sure how this happened. But I did step one of your suggestion by uninstalling the driver and put it to hibernate for five minutes. When I pulled the computer out of hibernate, the adapter reinstalled itself and the BSOD disappeared with it. I tried to bring the BSOD by putting the computer into Hibernate for 30 minutes and pulled it out and I didn't get the BSOD. Did something happened?
Click to expand...

It's very possible that somehow you got a bad driver, and the uninstall/reinstall process fixed it. Keep us updated regarding whether or not it comes back.

Regards,

Patrick
 
I never BSOD during the verifier.

The adapter that reinstalled was the Realtek RTL8723A Wireless LAN 802.11n USB 2.0 Network Adapter.

It's not listed in the Driver Verifier.

@Patrick

I'll inform you if I BSOD again with the adapter problem. I'll most likely update this thread.

So, would this be considered solved-ish and that I can reinstall norton antivirus?
 
Until proven otherwise by a crash, yes. Disable verifier if you don't crash within 24/48 hours.

If you don't crash for several days, please let us know and we'll consider it solved.

Regards,

Patrick
 
One last question on that part.

How do you disable verifier?

Also any good 'free' antivirus suggestions?
 
Levont said:
The adapter that reinstalled was the Realtek RTL8723A Wireless LAN 802.11n USB 2.0 Network Adapter.

It's not listed in the Driver Verifier.
Click to expand...

If it's not listed in Driver Verifier, it's not loaded into RAM and can't cause a BSOD.

Interesting that Windows reinstalled the driver if the device was not connected.

Levont said:
So, would this be considered solved-ish and that I can reinstall norton antivirus?
Click to expand...

No - please do not reinstall NIS until Driver Verifier is finished.

Levont said:
One last question on that part.

How do you disable verifier?

Also any good 'free' antivirus suggestions?
Click to expand...

To disable Driver Verifier, bring up a CMD prompt and enter:
Code: 
verifier /reset

Then re-boot your system.

Good, free a/v - MSE - http://windows.microsoft.com/en-us/windows/security-essentials-download

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top