Solved BSOD After Clean Install of Windows 7

[patfield]

Hi: I hope you can help me solve my blue screen problem. My computer is an HP Pavilion a6242n which had a OEM Windows Vista installed. It has a AMD Athlon 64 x2 processor, 3072 mb Memory, 320 g Harddrive, dvd burner, Nvidia Geforce 6150 SE graphics card. The computer is 2 years old

I did a clean install of Windows 7 Ultimate 64 bit that was a retail purchase and then used easy transfer to reinstall my data.

I am attaching the Windows_NT6_BSOD_jcgriff2 folder and the Perfmon HTML.

Hope you can help me please figure this out.

 

[wish]

Hi,
Your single dump have error code 0x19_3 = indicates pool header corruption.

Reinstall .Net Framework because mscorsvw.exe was involved on the crash.

PROCESS_NAME:  mscorsvw.exe

Upgrade your symantec antivirus to the latest version, or uninstall it.
I would recommend to use MSE for troubleshooting purpose.

These drivers need to do update:

[URL="http://www.nvidia.com/Download/index.aspx"]Nvidia chipset driver= [/URL]
nvstor   nvstor.sys   Tue May 19 23:45:37 2009
nvlddmkm nvlddmkm.sys Thu May 14 13:48:07 2009
nvm62x64.sys Fri Oct 17 14:01:06 2008

[URL="http://www.conexant.com/support/"]Conexant SoftK56 Modem Driver[/URL]=
VSTBS26  VSTBS26.SYS  Wed Oct 15 17:54:06 2008
VSTCNXT6 VSTCNXT6.SYS Wed Oct 15 17:52:22 2008
VSTDPV6  VSTDPV6.SYS  Wed Oct 15 17:57:45 2008

If the problem persist, enable driver verifier and use windows normally. Then if you get BSOD attach the new file here.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa80060fb640, 0, fffffa80060fb640}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )

Followup: Pool_corruption
---------

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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80060fb640, the pool entry being checked.
Arg3: 0000000000000000, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80060fb640, 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:  mscorsvw.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800029bb130 to fffff80002888740

STACK_TEXT:  
fffff880`06625998 fffff800`029bb130 : 00000000`00000019 00000000`00000003 fffffa80`060fb640 00000000`00000000 : nt!KeBugCheckEx
fffff880`066259a0 fffff800`029bd4c1 : ffffffff`fffffffe fffffa80`03a2ee60 00000000`00000000 fffff8a0`08d5c7b0 : nt!ExDeferredFreePool+0xca0
fffff880`06625a30 fffff800`0288d8bc : fffffa80`03a2eea0 00000000`00000000 fffffa80`52777445 fffffa80`02385350 : nt!ExFreePoolWithTag+0x411
fffff880`06625ae0 fffff800`02b9e514 : fffffa80`02a14900 00000000`00000000 fffffa80`02ed27e0 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`06625b40 fffff800`02b9e414 : 00000000`000001ac fffffa80`02a14900 fffff8a0`08d5c7b0 00000000`000001ac : nt!ObpCloseHandleTableEntry+0xc4
fffff880`06625bd0 fffff800`02887993 : fffffa80`02ed27e0 fffff880`06625ca0 00000000`00000001 00000000`00000001 : nt!ObpCloseHandle+0x94
fffff880`06625c20 00000000`76f0fe4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012f6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f0fe4a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+ca0
fffff800`029bb130 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+ca0

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+ca0

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+ca0

Followup: Pool_corruption

 

[patfield]

Still having problems with BSOD

I did all the things that were recommended but am still getting a blue screen as well as the screen freezes sometimes and I have to reboot. I am attaching another perfmon and another jcgriff2. I also downloaded all new drivers as requested.

 

[wish]

Hi again,
The driver verifier didn't mention any specific drivers that cause the crash, so you may disable it and do the suggestion bellow:

Yes I see you have updated conexant modem driver, but one of them have different timestamp (older one).
Maybe you should recheck or contact manufacture whether the modem supports win7 or not.
All conexant drivers that installed in your windows:

mdmxsdk.sys  Mon Jun 19 14:27:26 [COLOR=Red]2006[/COLOR] --> Conexant Modem Diagnostic Interface x86 Driver
CAX_CNXT.sys Fri Feb 13 13:19:32 2009 --> Conexant Modem
CAX_DP.sys   Fri Feb 13 13:18:25 2009
CAXHWBS2.sys Fri Feb 13 13:21:18 2009
XAudio64.sys Wed Apr 29 11:21:07 2009 --> Conexant Modem Audio

But the more important is your Perform report = "The average disk queue length is 1.094. The disk may be at its maximum transfer capacity due to throughput and disk seeks"
So test your hardrive with WDC Data Lifeguard Diagnostics.

If the hardrive diagnostic result good, perhaps the disk report was cause by your backup software/utility or it's related to your Storage Filter Driver(amdxata.sys) that seems outdated.

amdxata.sys  Tue May 19 10:56:59 2009 --> [URL="http://support.microsoft.com/kb/982018"]should be 2010 by windows update[/URL]
storport.sys Mon Jul 13 17:01:18 2009 --> windows update

Then let see if you still have the problem.
- wish

Log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc50014bb8, 803000002157f882, fffff6fc50014ba9}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc50014bb8
Arg3: 803000002157f882
Arg4: fffff6fc50014ba9

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  2

TRAP_FRAME:  fffff88007790960 -- (.trap 0xfffff88007790960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000c20 rbx=0000000000000000 rcx=0000000000000c20
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d82d10 rsp=fffff88007790af0 rbp=fffff88007790c00
 r8=fffffa8002369570  r9=0000000000000001 r10=0000000000000c20
r11=000000000031bdc4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ObReferenceObjectByHandleWithTag+0xb0:
fffff800`02d82d10 8b465c          mov     eax,dword ptr [rsi+5Ch] ds:8300:00000000`0000005c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a5571e to fffff80002a8e740

STACK_TEXT:  
fffff880`07790608 fffff800`02a5571e : 00000000`0000001a 00000000`00000411 fffff6fc`50014bb8 80300000`2157f882 : nt!KeBugCheckEx
fffff880`07790610 fffff800`02ac07ad : fffff8a0`0297771c fffff6fc`50014bb8 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6051
fffff880`07790660 fffff800`02aaad26 : 00000000`00000000 fffff800`02ce9b32 7ff00000`00000000 fffff800`02c1ab40 : nt!MiResolveTransitionFault+0x38d
fffff880`077906f0 fffff800`02aa8cf1 : fffff880`00000065 fffff800`00000040 80300000`2157f882 00000000`00000002 : nt!MiDispatchFault+0x946
fffff880`07790800 fffff800`02a8c82e : 00000000`00000000 fffff880`07790c38 00000000`00000000 fffff800`02b84900 : nt!MmAccessFault+0x8f1
fffff880`07790960 fffff800`02d82d10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07790af0 fffff800`02dab139 : 00000000`00000000 00000000`00000002 fffffa80`02369570 fffff880`07790c01 : nt!ObReferenceObjectByHandleWithTag+0xb0
fffff880`07790bc0 fffff800`02a8d993 : fffffa80`03f1e8c0 fffff880`07790ca0 00000000`00000000 00000000`00000000 : nt!NtSetEvent+0x75
fffff880`07790c20 00000000`773efe3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04f480f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773efe3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+6051
fffff800`02a5571e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+6051

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6051

BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6051

Followup: MachineOwner

 

[patfield]

Still blue screening

I went through the issues you suggested. I ran the disk diagnostic and everything was OK. I went to the Hot fix site and downloaded a hotfix (but I don't know what it did) and I checked with the modem supplier and they said it should work with Windows 7. I am not sure how to get an update for amdxata.sys. I ran a windows update and it says that everything is up to date. I am getting so fed up with the blue screening that I am almost ready to go back to Vista. Help me please!!

 

[wish]

Hey dont give up mate! I'll try my best to help you
I found in your System Information that your Bios date is quite old. It's 2 years before windows 7 come at 2009.
Is it possible to update the Bios?
Your Bios:

SystemProductName = GN706AA-ABA a6242n
BaseBoardProduct = ECS Nettle2
BiosVendor = Phoenix Technologies, LTD
BiosVersion = 5.18
BiosReleaseDate = 09/05/2007

Is this your motherboard? --> Motherboard Specifications, MCP61PM-HM (Nettle2) - HP Customer Care (United States - English)
I search in HP website and find an update to that BIOS:
MCP61PM-HM Motherboard BIOS Update - HP Customer Care (United States - English)

BiosVersion = 5.27
BiosReleaseDate = 2008-08-04

Since I dont know much about your PC and motherboard, you must recheck again and make sure to have the right version, because Bios update failure can be fatal.

 

[patfield]

Question on Bios update

You suggested that I try to update the bios. I did check to see that the motherboard was the one you asked I had, and that was right. When I download the bios update it states "must have Vista operation system". I was afraid to go ahead and continue with the installation because I am running Windows 7 (although not all that well). Should I still continue with the bios update?

 

[wish]

If you sure about the version, try it.
Right click the setup --> properties --> Run compatibility Windows Vista

 

[patfield]

bios update failed

when I tried to update the bios, I got the message that it failed because my system did not meet the requirements. What now? I am attaching another dump report from the last crash.

 

[wish]

So the bios version is not match with your board.

Two last dumps:

• 0x3D = INTERRUPT_EXCEPTION_NOT_HANDLED
• 0xA = IRQL_NOT_LESS_OR_EQUAL usual cause by driver or RAM.

Reinstall your Nvida driver because it was involved in the crash.
Before reinstall, better to remove the current driver with driversweeper then download and install a fresh copy.
Guru3D - Driver Sweeper
Drivers - Download NVIDIA Drivers

Then try some hardware test:
1] RAM test with memtest86 for at least 7 passes.
2] Video CArd stress with furmark.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c1d000c9, 6, 0, fffff80002aaccd3}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+21160 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000c1d000c9, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aaccd3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfa0e0
 00000000c1d000c9 

CURRENT_IRQL:  6

FAULTING_IP: 
nt!KeInsertQueueDpc+13
fffff800`02aaccd3 440fb74902      movzx   r9d,word ptr [rcx+2]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff8800755f840 -- (.trap 0xfffff8800755f840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800483c10c rbx=0000000000000000 rcx=00000000c1d000c7
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aaccd3 rsp=fffff8800755f9d0 rbp=0000000000000000
 r8=0000000000000000  r9=fffff8800483c10c r10=0000000000000001
r11=fffff8800755fb10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeInsertQueueDpc+0x13:
fffff800`02aaccd3 440fb74902      movzx   r9d,word ptr [rcx+2] ds:00000000`c1d000c9=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac1ca9 to fffff80002ac2740

STACK_TEXT:  
fffff880`0755f6f8 fffff800`02ac1ca9 : 00000000`0000000a 00000000`c1d000c9 00000000`00000006 00000000`00000000 : nt!KeBugCheckEx
fffff880`0755f700 fffff800`02ac0920 : 00000000`00000000 fffffa80`0390f000 fffffa80`0390f000 fffff880`03d3e496 : nt!KiBugCheckDispatch+0x69
fffff880`0755f840 fffff800`02aaccd3 : 00000000`00000000 00000000`00000000 fffffa80`03c9b000 fffffa80`0390f000 : nt!KiPageFault+0x260
fffff880`0755f9d0 fffff880`0483c160 : fffffa80`0390f000 00000000`00000000 00000000`00000000 fffff880`049b42c4 : nt!KeInsertQueueDpc+0x13
fffff880`0755fa60 fffffa80`0390f000 : 00000000`00000000 00000000`00000000 fffff880`049b42c4 00000000`c1d00007 : nvlddmkm+0x21160
fffff880`0755fa68 00000000`00000000 : 00000000`00000000 fffff880`049b42c4 00000000`c1d00007 00000000`00000000 : 0xfffffa80`0390f000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+21160
fffff880`0483c160 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+21160

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb9dd0e

FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+21160

BUCKET_ID:  X64_0xA_nvlddmkm+21160

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

 

[patfield]

Continuing saga of BSOD

I used the tool to completely clear the Nvidia driver and installed the new one (although when I use Driver Whiz to test the new installation it still shows up as needing a newer version, but I downloaded it right from the Nvidia site). I ran the Furmark test but there is no temperature recorded (always 0) and the fur just turns really slowly. I let it run for about 20 minutes but didn't get any results.

Even when I was running Vista and I would be playing a game (like Bejewelled) and it had to change screens, it would take forever to change to the next screen. When I run Bejewelled on my laptop, when it goes to a different level it changes right away, but on my desktop, it would take forever to go through the same process. Do you think there is something wrong with my Nvidia card?

 

[zigzag3143]

You suggested that I try to update the bios. I did check to see that the motherboard was the one you asked I had, and that was right. When I download the bios update it states "must have Vista operation system". I was afraid to go ahead and continue with the installation because I am running Windows 7 (although not all that well). Should I still continue with the bios update?

Have you checked to be sure your BIOS is win 7 compatibile?

Sometimes when installing drivers it is nec to install them in compatibility mode. I havent seen it in BIOS updates but...

To install in compat right click the installer>properties>compatibility>chose OS

 

[wish]

I used the tool to completely clear the Nvidia driver and installed the new one (although when I use Driver Whiz to test the new installation it still shows up as needing a newer version, but I downloaded it right from the Nvidia site). I ran the Furmark test but there is no temperature recorded (always 0) and the fur just turns really slowly. I let it run for about 20 minutes but didn't get any results.

Even when I was running Vista and I would be playing a game (like Bejewelled) and it had to change screens, it would take forever to change to the next screen. When I run Bejewelled on my laptop, when it goes to a different level it changes right away, but on my desktop, it would take forever to go through the same process. Do you think there is something wrong with my Nvidia card?

Yes, It has narrow down the problem to your Nvidia card.
For the furmark, you may use Speedfan to monitor the temp.

Since I have little exp with hardware stuff, I'll search help for you.

 

[Dave76]

Did you run the memtest86+ as suggested previously?

Then try some hardware test:
1] RAM test with memtest86 for at least 7 passes.

This tutorial will explain how to run the test.

How to Test and Diagnose RAM Issues with Memtest86+​

Let us know if you have any questions and what the results are.
Is that the RAM that came with your computer?
Any upgrades done?


From what you said about your integrated Nvidia graphics above, that will be something to look at.
Your integrated graphics will be using some of your RAM to run, so the RAM test should be done first.

 

[patfield]

continuing saga

Yes, I did run the memtest and after six passes there were no errors.

If the problem is with my graphics card, does that mean that I need to buy a new graphics card to run Windows 7 properly or do I need to reinstall Vista instead? I have been doing some searching on graphics cards and I am getting more and more confused about which one would be the best choice.

 

[wish]

Run Windows 7 Upgrade Advisor to see if your hardware meet the minimum requirement.
Free Download PC Upgrade Advisor Windows 7 Hardware Programs Issues

 

[patfield]

upgrade advisor

I ran the Upgrade Advisor (again) and it says my system meets the minimum requirements. I had also run it before doing the clean install of Windows 7.

You suggested that I try to do a bios upgrade using compatibility mode. I tried that and it also failed to install.

 

[wish]

From what you said before, you were confuse whether buying new graphic card or go back to vista. I think the most suitable for you is going back to vista since your motherboard is old enough so I cannot guarantee your problem will solved just by change the VGA card.
But it will be worthy if you buying all new systems for running win7.

Take a look what jcgriff2 said here:http://www.sevenforums.com/crashes-...ainbow-screen-bsod-problem-4.html#post1033591

 

[patfield]

going back to vista

Thanks to all that have responded to my problems. I think I will just do a system restore and go back to Vista. I had alot less problems when I was running it. Although my graphics were sometimes slow when running some games, at least my system didn't crash.

I appreciate all your effort in trying to get my BSOD problems resolved.

 

[wish]

You're welcome mate