Windows 7 Frequent Blue screen problem, Please help!

dao764

New Member
Joined
Feb 20, 2013
Messages
4
Hello, everyone.
My screen frequently breaks horizontally and turns into blue screen. In attempt to fix this problem, I changed my graphic card as well as my hard disk to SSD, and re-installed windows. But I'm still getting BSD now and then.
I attached my DMP file and event logs, could anyone analyze and find a solution for me? It's been giving me a headache for a long time now.

Thanks in advance!
Link Removed
David Oh
 


Attachments

Last edited:
Solution
Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

Only 3 Windows Updates installed. Most systems have 140 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

You have an ASUS USB-N13 300Mbps 11n Wireless USB dongle:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An...
Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

Only 3 Windows Updates installed. Most systems have 140 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

You have an ASUS USB-N13 300Mbps 11n Wireless USB dongle:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

The memory dump blames rtwlanu.sys - a driver component of your wireless USB network adapter:
rtwlanu.sys Tue Sep 6 02:38:48 2011 (4E65BFF8)
Realtek RTLxxxxx Wireless USB 2.0 Adapter
Link Removed
Please remove the device from your system and un-install it's software to test. Either use a long cable or a wireless card that plugs into your motherboard for internet access while testing.

If that proves to be the problem you can also try:
- download a fresh copy of the software for this device
- un-install the current software
- install the freshly downloaded software
- monitor for further BSOD's

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

L1E62x64.sys Thu Jun 11 02:45:22 2009 (4A30A802)
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20)
Link Removed

AiCharger.sys Wed May 5 04:37:36 2010 (4BE12E50)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed

Should the BSOD's continue, please run Driver Verifier according to these instructions: Link Removed


Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Wed Feb 20 12:05:25.306 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022013-13556-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:13:54.007[/B]
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for rtwlanu.sys
*** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys
Probably caused by :[B]rtwlanu.sys ( rtwlanu+1f84d )[/B]
BugCheck [B]D1, {fffffac007ebe898, 2, 0, fffff88000c16807}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffac007ebe898, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000c16807, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_rtwlanu+1f84d[/B]
  BIOS Version                  3503   
  BIOS Release Date             04/13/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Wed Feb 20 12:05:25.306 2013 (UTC - 5:00)**************************
[COLOR=RED][B]L1E62x64.sys                Thu Jun 11 02:45:22 2009 (4A30A802)[/B][/COLOR]
[COLOR=RED][B]ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)[/B][/COLOR]
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
[COLOR=RED][B]AiCharger.sys               Wed May  5 04:37:36 2010 (4BE12E50)[/B][/COLOR]
rtwlanu.sys                 Tue Sep  6 02:38:48 2011 (4E65BFF8)
[COLOR=RED][B]AODDriver2.sys              Tue Mar  6 04:55:00 2012 (4F55DEF4)[/B][/COLOR]
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
atikmpag.sys                Fri Jul 27 21:14:47 2012 (50133D07)
atikmdag.sys                Fri Jul 27 21:48:09 2012 (501344D9)
EstRtw.sys                  Thu Dec 27 03:52:57 2012 (50DC0C69)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 


Solution
Back
Top