Solved BSOD from previous months

[vietdragon2009]

I've had several BSOD after a clean install of windows 7 home 32 full in attempt to fix a previous BSOD (must have been for a different reason). It can't be a hardware issued because I'm dual-booting xp home 32 oem with no problem, which I didn't do either till after the clean install of 7. I've also ran DLG Diagnostic (Western Digital) and Windows Memory Diagnostic. I've done a selective start-up, updated drivers (which was hard because the motherboard only has drivers up to vista), scanned for viruses in safe mode. The computer (custom) belongs to my church, which is [atleast] 3 years old with no problems till about 6 months ago. The event viewer led to MSE, so I changed it to AVG , now it says something about shadow copies aborted and sxstrace (it didn't produce a minidump for this BSOD so I'll be sure to post it next time).

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[vietdragon2009]

Drivers
ASUSTeK Computer Inc.-Forum- windows 7 not compatable?

NVIDIA DRIVERS 296.10 WHQL

ViewCast | Streaming Media Solutions (240e)

 

[zigzag3143]

Drivers
ASUSTeK Computer Inc.-Forum- windows 7 not compatable?

NVIDIA DRIVERS 296.10 WHQL

ViewCast | Streaming Media Solutions (240e)

Again we need the actual DMPS not text files of their results., Follow the instructions to find and upload them.

 

[vietdragon2009]

sorry

 

[writhziden]

Security Software:

avgcsrvx.exe	c:\program files\avg\avg2012\avgcsrvx.exe	336	8	200	1380	3/18/2012 9:21 AM	12.0.0.1786	329.84 KB (337,760 bytes)	8/15/2011 7:21 AM
avgemcx.exe	c:\program files\avg\avg2012\avgemcx.exe	2348	8	200	1380	3/18/2012 9:22 AM	12.0.0.1854	950.84 KB (973,664 bytes)	10/10/2011 7:23 AM
avgidsagent.exe	c:\program files\avg\avg2012\avgidsagent.exe	2176	8	200	1380	3/18/2012 9:22 AM	12.0.0.1855	4.23 MB (4,433,248 bytes)	10/12/2011 7:25 AM
avgnsx.exe	c:\program files\avg\avg2012\avgnsx.exe	2240	8	200	1380	3/18/2012 9:22 AM	12.0.0.1883	1.17 MB (1,229,664 bytes)	11/28/2011 1:19 AM
avgtray.exe	c:\program files\avg\avg2012\avgtray.exe	2636	8	200	1380	3/18/2012 9:22 AM	12.0.0.1912	2.30 MB (2,416,480 bytes)	1/24/2012 5:24 PM
avgwdsvc.exe	c:\program files\avg\avg2012\avgwdsvc.exe	1824	8	200	1380	3/18/2012 9:21 AM	12.0.0.1773	188.26 KB (192,776 bytes)	8/2/2011 7:09 AM

Possible out of date drivers:

windrvr9	8da00000	8da2d8e0	Sun Jun 17 04:26:25 2007 (46750c51)	0003c174		windrvr9.sys
mcdbus	8ee5c000	8ee78800	Tue Feb 24 03:42:13 2009 (49a3cf05)	0001e53c		mcdbus.sys
ADIHdAud	8ef76000	8efd8000	Thu May 21 02:22:07 2009 (4a150f2f)	0006a671		ADIHdAud.sys

windrvr9.sys appears to be part of TalkSwitch; a telephone driver...
mcdbus.sys
ADIHdAud.sys


Make sure the HD Audio driver (the last driver listed) is updated.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\vietdragon2009\Windows_NT6_BSOD_jcgriff2\031412-67735-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82a48000 PsLoadedModuleList = 0x82b914d0
Debug session time: Wed Mar 14 16:10:07.835 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:30.019
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 848342b8, the pool entry being checked.
Arg3: 00000000, the read back flink freelist value (should be the same as 2).
Arg4: 848342b8, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82c929a7 to 82b6868c

STACK_TEXT:  
a0083b58 82c929a7 00000001 00000034 61564d43 nt!ExAllocatePoolWithTag+0x682
a0083b80 82c9414c 9edd2d84 a0083c2c 0000002c nt!CmpGetValueKeyFromCache+0x9e
a0083bec 82c932ae a0083c7c a0083c2c a0083c28 nt!CmpFindValueByNameFromCache+0xa2
a0083c60 82c937d6 a153c4f8 00000002 03b2f97c nt!CmQueryValueKey+0x350
a0083d14 82a8621a 0000081c 03b2fa40 00000002 nt!NtQueryValueKey+0x312
a0083d14 77417094 0000081c 03b2fa40 00000002 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
03b2fa10 00000000 00000000 00000000 00000000 0x77417094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+682
82b6868c cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+682

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea76eb4

FAILURE_BUCKET_ID:  0x19_3_nt!ExAllocatePoolWithTag+682

BUCKET_ID:  0x19_3_nt!ExAllocatePoolWithTag+682

Followup: MachineOwner
---------

Possible causes are Drivers...


Check for driver conflicts:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 203912
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[vietdragon2009]

Thanks guys I'll update you if I get another one.

 

[vietdragon2009]

new

 

[writhziden]

Problematic Software:

Start Menu\Programs\Advanced SystemCare 5	Public:Start Menu\Programs\Advanced SystemCare 5	Public

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.


Your crash appears to be due to a corrupted installation of AVG. Uninstall AVG through Start Menu -> Control Panel -> Uninstall a program. Then Download and install the latest version from AVG Windows 7 Users | Internet Security | Save 20%

It could also mean your network drivers need to be re-installed. You can find the network drivers at Drivers - Download NVIDIA Drivers and in device manager, they are under Network Adapters.

To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding the appropriate set of devices
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

 

[vietdragon2009]

Thank you I'll try that out.

Hadn't had time to do anything yet. This is just another 1 I got.

 

[vietdragon2009]

This one happened in xp which never happened before.

 

[writhziden]

The crashes themselves are relatively inconclusive. The bugcheck codes would indicate a hardware issue, though. The most likely hardware is your memory.

Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[vietdragon2009]

Tests show hardware is fine, I'll try a few more rounds. However, I'm getting a bsod on win 7 that gets stuck at "Initializing Data for crash dump" and no minidump. driver_irql_not_less_or equal stop: 0x000000D1 (0x00002008, 0x00000002, 0x00000000, 0x84DF64BB) nvstor.sys-address 84DF6xbb base at 84de8000, date stump 45357aad

 

[writhziden]

Your Chipset drivers are out of date or corrupted. Update from NVIDIA DRIVERS 15.57WHQL

 

[vietdragon2009]

It's been two months without a problem. Hopefully it's fixed, thank you all your help.

 

[vietdragon2009]

stop:0x0000008e (0xc0000005, 0xb9ece457, 0xba56abb4, 0x000000000) scsiport.sys-address b9ece457 base at b9ece000 datestamp 4802539d I had another 1 I thought was a bios issue and no minidump. My motherboard doesn't have a win7 bios update. I used asus bio update with a xp update. It's not recognizing my win 7 disc. I'm trying to do a repair with xp cd, but its stuck on "installing windows" "setup will complete in approximately 39 minutes.