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: Consistent BSOD minutes after logging in, error code 0x0000000A


14 Feb 2012   #1

Windows 7 Ultimate x64
 
 
Consistent BSOD minutes after logging in, error code 0x0000000A

Lately I've been getting these BSOD, and it consistently occurs between immediately and a few minutes after I log into my profile to the desktop.

The desktop I use is originally a Compaq with Vista installed back in 2006 but most of the parts are since replaced; Windows 7 Ultimate x64, 4gRAM, cooling, interface, radeon 5700 card, i3 processor. Except monitor and maybe a hard disk drive from only a few years ago. The Windows 7 I got around 2-3 years ago I think


This is the BSOD collection app results and a picture of one of the BSOD codes


I can't use the system health report as I can't start the service it requires in safe mode.

Any help would be greatly appreciated, thanks in advance

My System SpecsSystem Spec
.

14 Feb 2012   #2

Win 8 Release candidate 8400
 
 

First please download malwarebytes free and run it


Please download the free version of Malwarebytes.

Update it immediately.
Do a full system scan
Let us know the results at the end.


Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!


IF the above is clean then do the following.

AVG can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

Please update the below drivers.
Code:
mdmxsdk.sys    6/19/2006 4:27:26 PM    fffff880`06000000    fffff880`06004280    0x00004280    0x449716be                            
hamachi.sys    2/19/2009 5:36:41 AM    fffff880`040af000    fffff880`040ba000    0x0000b000    0x499d3639                            
Rt64win7.sys    2/26/2009 4:04:13 AM    fffff880`03f5f000    fffff880`03f91000    0x00032000    0x49a65b0d                            
netr7364.sys    3/12/2009 10:13:08 PM    fffff880`05e24000    fffff880`05eda000    0x000b6000    0x49b9cf44                            
XAudio64.sys    4/29/2009 1:21:07 PM    fffff880`03aa6000    fffff880`03aae000    0x00008000    0x49f89a93                            
nvstor.sys    5/20/2009 1:45:37 AM    fffff880`011a7000    fffff880`011d2000    0x0002b000    0x4a13a711                            
nvstor64.sys    6/22/2009 5:23:37 PM    fffff880`012e3000    fffff880`01321000    0x0003e000    0x4a400469
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.


Use this SPTD uninstaller DuplexSecure - Downloads
DuplexSecure - FAQ

when you're done you can use this Freeware:


MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place


Using MagicISO to create ISO image files
My System SpecsSystem Spec
15 Feb 2012   #3

Windows 7 Ultimate x64
 
 

So I get back home today and logged on and so far everything hasn't blue screened so far


Here's a mini log I made while I was updating what drivers I could in safe mode. Malwarebytes detected 2 objects, removed them

Last night I was trying to log on after updating everything and after booting up, it still bluescreened with 0x0000000A and 0x0000000E and so before I slept I just left it on at the login screen throughout the night and day until I got home just now. And now it didn't blue screen this time. I'm not sure I want to test stability by restarting computer in fear of bsod.

currently not sure if it will remain stable, thank you for the help
My System SpecsSystem Spec
.


17 Feb 2012   #4

Windows 7 Ultimate x64
 
 

I spoke too soon, the next day it continued blue-screening with 0x0000000A or 0x0000000E every time I log in to desktop

Here's a new minidump rar, any drivers that still appear outdated, I couldn't determine where to locate them online, mostly the conexant ones and Ralink one. Can anyone help?
My System SpecsSystem Spec
18 Feb 2012   #5

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Recognition View Post
I spoke too soon, the next day it continued blue-screening with 0x0000000A or 0x0000000E every time I log in to desktop

Here's a new minidump rar, any drivers that still appear outdated, I couldn't determine where to locate them online, mostly the conexant ones and Ralink one. Can anyone help?
This is the only driver you need to worry about. It has known problems with win 7 and is Related to RTCore64.sys MSI Afterburner from Micro-Star Int'l Co. Ltd.

I would remove to test.


15 of 39 DMPs point directly to a memory exception several more indirectly



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.




Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
My System SpecsSystem Spec
Reply

 Consistent BSOD minutes after logging in, error code 0x0000000A




Thread Tools



Similar help and support threads for2: Consistent BSOD minutes after logging in, error code 0x0000000A
Thread Forum
Solved BSOD after logging on for around 2 minutes, error 0x0000008E BSOD Help and Support
BSOD 2-3 minutes after logging into Win 7 BSOD Help and Support
Solved BSOD 5 minutes after logging onto computer error 0x00000019 BSOD Help and Support
Solved BSOD Occurs 5 Minutes After Logging In BSOD Help and Support
BSOD within minutes of logging in BSOD Help and Support
BSOD when logging in to desktop, error 0x0000000a BSOD Help and Support
Consistent BSOD 5 minutes into Windows 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 02:29 AM.
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