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: BSOD issues


11 Nov 2010   #1

Windows 7 Home Edition 64bit
 
 
BSOD issues

I run Windows 7 64bit Home edition and haven't had any issues what so ever until last month. I was using Avast! as my anti-virus protection when it let me know that an upgrade to the program was ready to install. I installed the new Avast! program and that's when my problems started. I checked Event Viewer and noticed that my first blue screens had to deal with a software issue with Avast. I uninstalled Avast and installed AVG instead and had no problems for a month. I was having issues with AVG causing my games to stop working mid game so I decided to uninstall it and go with Microsoft Security Essentials. My BSOD woes came back shortly after. Problem is I uninstalled it and it persisted. I did a System Restore back to when I uninstalled AVG and before I installed MSE and still no luck. I've gotten IRQL BSODs and a MEMORY_MANAGEMENT BSOD. I've got two dump files that I'm attaching for anyone who can debug it.


My System SpecsSystem Spec
.

11 Nov 2010   #2

Windows 7 Ultimate x64 SP1
 
 

Hi,
Your 2 dumps have 0xA bugcheck code (MEMORY_MANAGEMENT), usual caused by drivers or RAM.
So I would recommend you to perform memory test for at least 7 passes. (better run it overnight)
RAM - Test with Memtest86+

Then you have a lot of drivers that need to be update (especially for Creative device)
Code:
List Creative Drivers in your machine:
ha20x2k.sys  Mon Dec 29 06:01:12 2008 
CT20XUT  CT20XUT.SYS  Mon Dec 29 06:03:00 2008
ctac32k.sys  Wed Jul 02 01:38:22 2008
ctac32k.sys  Wed Jul 02 01:38:22 2008
ctaud2k.sys  Mon Dec 29 06:01:47 2008
CTEXFIFX.SYS Mon Dec 29 06:02:55 2008
CTHWIUT.SYS  Mon Dec 29 06:03:03 2008
ctoss2k.sys  Mon Dec 29 05:59:50 2008
ctprxy2k.sys Mon Dec 29 06:01:50 2008
ctsfm2k.sys  Mon Dec 29 05:59:37 2008
emupia2k.sys Mon Dec 29 05:59:30 2008

Nvidia Video & Chipset drivers :
nvBridge.kmd Fri Nov 20 19:09:47 2009
nvlddmkm.sys Fri Nov 20 19:40:46 2009
Log
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003d06c50
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchFilterHo

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002afa058 to fffff80002a86740

STACK_TEXT:  
fffff880`06762068 fffff800`02afa058 : 00000000`0000001a 00000000`00041790 fffffa80`03d06c50 00000000`0000ffff : nt!KeBugCheckEx
fffff880`06762070 fffff800`02a5968a : fffffa80`0724c060 fffffa80`00000a98 fffff880`000006da fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x339c8
fffff880`06762920 fffff800`02d6bdcf : fffff8a0`0a9019a0 fffff880`06762c20 00000000`00000000 fffffa80`06ea16a0 : nt!MmCleanProcessAddressSpace+0x96
fffff880`06762970 fffff800`02d44635 : 00000000`c0000005 00000000`c0000001 000007ff`fffa8000 fffffa80`0b750b60 : nt!PspExitThread+0x92f
fffff880`06762a30 fffff800`02a631db : 00000000`00000100 fffffa80`06ea1760 00000000`00000001 fffff800`02a8db9d : nt!PsExitSpecialApc+0x1d
fffff880`06762a60 fffff800`02a63620 : 00000000`00000001 fffff880`06762ae0 fffff800`02d4474c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`06762ae0 fffff800`02a85a37 : fffffa80`06ea16a0 00000000`00007530 fffff880`06762bf8 fffffa80`0714b7a0 : nt!KiInitiateUserApc+0x70
fffff880`06762c20 00000000`76ebfd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`01eafe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ebfd9a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339c8
fffff800`02afa058 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339c8

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339c8

Followup: MachineOwner
---------
My System SpecsSystem Spec
12 Nov 2010   #3
Microsoft MVP

 
 

Just a bit from the Stack Text...

This line:
Code:
fffff880`06762920 fffff800`02d6bdcf : fffff8a0`0a9019a0 fffff880`06762c20 00000000`00000000 fffffa80`06ea16a0 : nt!MmCleanProcessAddressSpace+0x96
Mm = Windows Memory Manager - and it's attempting to clean up the address space for the Process

And this line:
Code:
00000000`01eafe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ebfd9a
It's from an address that's probably not in the kernel address space. In most cases this is from the user address space and is caused by a program improperly trying to access the kernel space.

After you've finished wish's directions, if you're still having BSOD's, then please run Driver Verifier according to these instructions:
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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
.


Reply

 BSOD issues




Thread Tools



Similar help and support threads for2: BSOD issues
Thread Forum
BSOD issues BSOD Help and Support
BSOD Issues BSOD Help and Support
Need help with BSOD issues BSOD Help and Support
BSOD Issues BSOD Help and Support
BSOD issues BSOD Help and Support
Been having BSOD issues, like many on here. BSOD Help and Support
Freezing issues and BSoD issues. Help please! 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 08:31 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