Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSODs, varying codes


02 Apr 2013   #1

Windows 7 Ultimate x64
 
 
BSODs, varying codes

Last week I received new mem for my computer, going from 4 (2x2) to 12 (2x2 + 2x4) GB. After installing the new memory, I started receiving BSOD's and my computer crashed frequently or just failed to boot (stuck at windows loading). Turns out the new memory was DOA (memtest confirmed this).

However, since then I have been experiencing BSOD of varying kinds, mostly with code 0x0....50.

I've tried updating graphic drivers, motherboard driver, sound driver (also on mb) and networkcard driver.

My system consists of:

i7 860
Asus P7p55d
4 GB mem
Radeon HD5850
2 HDs

I've added the 4 most recent dumps as attachments. If you need more information, please ask. Hopefully someone can help me


My System SpecsSystem Spec
.

02 Apr 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

My System SpecsSystem Spec
02 Apr 2013   #3

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Arc View Post
Was doing that while you posted this. I missed it earlier, sorry . Added the file to the starting post.
My System SpecsSystem Spec
.


02 Apr 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

VIA High Definition Audio Function Driver is the problem here.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88006ca17c8, 0, fffff8800665e52f, 0}

*** WARNING: Unable to verify timestamp for viahduaa.sys
*** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys

Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
And the driver is kinda old.
Code:
fffff880`0961d000 fffff880`097de000   viahduaa T (no symbols)           
    Loaded symbol image file: viahduaa.sys
    Image path: \SystemRoot\system32\drivers\viahduaa.sys
    Image name: viahduaa.sys
    Timestamp:        Wed Aug 04 13:21:53 2010 (4C591C19)
    CheckSum:         00153722
    ImageSize:        001C1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it from VIA Drivers Download - VIA Technologies, Inc.

And Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver, too.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffe3850fff, 2, 0, fffff880018d9970}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------
And that is also very old.
Code:
fffff880`0548e000 fffff880`05513000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri Jun 10 12:03:15 2011 (4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Get the updates from Realtek

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
  • Double click to open it.
  • Click this button only:
  • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Free up the startup. Dont worry, it will not loss any functionality. But, the startup programs often clash, and causes various issues including BSODs.

  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.


Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.


Finally, as a test, Uninstall Norton and all Symentec products using Norton Removal tool. Norton is a huge source of BSODs; though in your case I haven't found any evidence that norton is causing it.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.
My System SpecsSystem Spec
02 Apr 2013   #5

Windows 7 Ultimate x64
 
 

Thanks for the quick reaction. I have updated all the drivers (did not know you could find them on those sites, the asus site still has outdated ones) and removed the sptd driver.

I tested the RAM last week but I will test it a bit longer somewhere this week. I also have not uninstalled Norton IS, but if I keep receiving errors I will do so. If this fixes it, thank you ! if not, also thanks but I'll be back
My System SpecsSystem Spec
03 Apr 2013   #6

Windows 7 Ultimate x64
 
 

I received some new BSODs today, 0x0.....d1 tcpip.sys error.

I suspect this is because I updated the network driver. I couldn't find the right driver for my lan card (Realtek 8112L) on the realtek site so I downloaded and installed the ones you linked too. That's when I started getting the error.

But I did some searching today and I found a more recent one (I think) which specifically mentions 8112L and I installed it, it's the 768202009 version. After that I ran the diagnostic program again, results are attached to this post.
My System SpecsSystem Spec
03 Apr 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Realtek driver is properly updated .... have a look.
Code:
fffff880`05045000 fffff880`05114000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Mon Mar 04 12:55:55 2013 (51344C83)
    CheckSum:         000D1FB8
    ImageSize:        000CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
So the ndis and tcpip errors are due to something else that is blocking the access to network. Generally it is either a virus or an ambitious antivirus.

There are evidences (dump data cannot give the proof for it) of virus ...
Code:
fffff800`051d2668  fffff880`010f2830 ataport!IdePortTickHandler
fffff800`051d2680  fffff880`010f2830 ataport!IdePortTickHandler
Scan the system for possible virus infection.
Also, Norton causes that network blockage very frequently. Just a few hours ago another person got his issue fixed by removing it. Do it, at least as a test.

Well, form another crash dump of the same date, it comes out to be Norton. Positively.

Symantec Heuristics Driver
Code:
fffff880`078b5e08  fffff880`04ea3400Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_20.2.0.19\Definitions\BASHDefs\20130322.001\BHDrvx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
 BHDrvx64+0x6400
Description here: Driver Reference Table - BHDrvx64.sys

And, Norton Internet Security
Code:
fffff880`078b5f10  fffff880`0453f940Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
 SYMEVENT64x86+0x22940
Description here: Driver Reference Table - SYMEVENT64x86.SYS

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

And there are some evidences of a Memory corruption. Without taking a risk, you should test the RAM modules, too. Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

The display driver is still crashing.
Code:
fffff880`078b65d8  fffff880`05907039Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x25039
fffff880`078b65e0  fffffa80`0676f000
fffff880`078b65e8  fffffa80`067e3000
fffff880`078b65f0  00000000`00000000
fffff880`078b65f8  fffff880`04d19d1dUnable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x3bd1d
Coz, apparently it is not updated as suggested.
Code:
fffff880`04cde000 fffff880`04d6b000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Dec 20 01:02:55 2012 (50D21667)
    CheckSum:         00095A98
    ImageSize:        0008D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Also stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results after doing all the suggested changes.
My System SpecsSystem Spec
06 Apr 2013   #8

Windows 7 Ultimate x64
 
 

I have done all of the above:

- Furmark ran 2 hrs, no errors
- Memtest ran ~8 hrs, 11 complete passes, no errors.

Windows defender (boot cd) did detect a possible virus in the windows hostfile, which I deleted.
I did uninstall Norton and now use MSE + WDO.

Computer ran fine, without crashes, for two days. Today I got a 7e BSOD with dxgmm1.sys being identified as the culprit.

When I ran the diagnostic tool it alerted me that the hostfile (which I deleted ) was missing. Reinstalled it with a hotfix from microsoft, don't know if this caused the BSOD.

But it's a lot more stable than before, so we are on the right track
My System SpecsSystem Spec
06 Apr 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Something is blocking HDD access, but what is it is not very clear from the dumps. There are many a things to suspect ...... better you enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any.

The dxgmms1.sys crash is not anything very important in this moment, as the drivers are in fine condition apparently. First let us try to search the other thing.
My System SpecsSystem Spec
07 Apr 2013   #10

Windows 7 Ultimate x64
 
 

OK, I have enabled DV yesterday evening and got my first crash just now. Black screen freeze, no BSOD message.

I've ran the diagnostic tool again but don't know if that also contains the DV logs so let me know if anything else is needed.
My System SpecsSystem Spec
Reply

 BSODs, varying codes




Thread Tools



Similar help and support threads for2: BSODs, varying codes
Thread Forum
Sporadic BSOD on a new build, varying bug check codes BSOD Help and Support
Solved Several BSODs following power outage. Varying BCCodes and frequency. BSOD Help and Support
Constant BSOD over the past two week, varying error codes BSOD Help and Support
BSOD with varying stop codes daily BSOD Help and Support
very frequent BSODs with various BCC codes. Please Help. BSOD Help and Support
BSOD Randomly. Varying error codes. BSOD Help and Support
RANDOM BSODs with different codes BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 05:15 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33