BSOD problem

[Brunolechef]

Hi,
I've got lot of issues with my computer since last week, windows asked me to update some files and since a BOSD with different error appeared. I've attached a zip files. Can any one suggest anything.
Thank you in advance for looking and helping me.

Bruno.
View attachment 250984

 

[Arc]

Hello Brunolechef.

The nvidia display driver you are using is problematic.

 lmvm nvlddmkm
start             end                 module name
fffff880`1304b000 fffff880`13ae9000   nvlddmkm   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 12:17:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Roll back to an earlier known stable version.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

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

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
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, [COLOR=Red][B]and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/B][/COLOR]
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa8003c32450, the pool entry being checked.
Arg3: fffffa8003c32470, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8003c32470, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  wininit.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bf64b3 to fffff80002acbfc0

STACK_TEXT:  
fffff880`02561018 fffff800`02bf64b3 : 00000000`00000019 00000000`00000003 fffffa80`03c32450 fffffa80`03c32470 : nt!KeBugCheckEx
fffff880`02561020 fffff800`02d68ad0 : fffff880`00000000 00000000`00000000 fffff880`02561148 fffff880`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`02561110 fffff800`02dc4a11 : 00000000`00000000 fffffa80`05cee030 fffff8a0`00000004 fffff880`04000000 : nt!MiCreatePagingFileMap+0xa0
fffff880`02561180 fffff960`00120987 : fffff880`025613f0 00000000`00030000 00000000`00000000 fffff880`025613c0 : nt!MmCreateSection+0x751
fffff880`02561380 fffff960`001205ff : fffffa80`05f55090 fffffa80`0575fce0 00000000`000000e0 fffffa80`0575fce0 : win32k!CreateDesktopHeap+0x47
fffff880`025613e0 fffff960`00169acc : 00000000`00000000 fffffa80`05cee010 fffff880`025616f8 fffff880`02561998 : win32k!xxxCreateDesktopEx2+0x293
fffff880`025614f0 fffff960`00169f5a : fffff880`02561640 fffff960`00169e70 00000000`00000000 000f037f`00000000 : win32k!ParseDesktop+0x134
fffff880`02561560 fffff800`02d6c45c : fffff800`02a4d000 fffffa80`0575fcb0 fffff8a0`00e9a140 00000000`00000702 : win32k!ParseWindowStation+0xea
fffff880`025615c0 fffff800`02d7355d : fffff800`02a4d000 fffffa80`05cee1c8 fffffa80`0575fcb0 fffff800`02d734e0 : nt!ExpWin32SessionCallout+0x5c
fffff880`02561620 fffff800`02dc23d8 : fffff800`02a4d000 fffffa80`00000000 00000000`00000000 fffff700`c0000001 : nt!ExpWin32ParseProcedure+0x7d
fffff880`025616a0 fffff800`02dc35f6 : 00000000`000000ac fffffa80`05cee010 00000000`00000000 fffffa80`03ce0660 : nt!ObpLookupObjectName+0x588
fffff880`02561790 fffff960`001598ef : fffff680`003b7ff8 00000000`00000000 00000000`000bfb01 00000000`76fff3c0 : nt!ObOpenObjectByName+0x306
fffff880`02561860 fffff960`00120b7a : 00000000`00000000 00000000`0016f9c0 00000000`00000000 00000000`000002c3 : win32k!xxxCreateDesktopEx+0xdf
fffff880`02561a00 fffff800`02acb253 : fffffa80`05f9db50 00000000`0016f9a8 fffff880`02561a88 00000000`ff24d200 : win32k!NtUserCreateDesktopEx+0xe6
fffff880`02561a70 00000000`76ff42aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0016f988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ff42aa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`02bf64b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a53

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+a53

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

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

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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

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

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

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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

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.

Let us know the results.

 

[Brunolechef]

Hi mate,

Cheers for the tips we did everything last night and when we restarted the computer everything was working fine, but when we turned on the computer this morning we had chrome and skype were corrupted, windows asked us to do a CHKSDK check so we did, we also disabled the DV settings for the moment. Is there anything we should do now?

Thank you.

Bruno.

 

[Arc]

Let us know the present situation. Are Skype and Chrome still corrupt? Did disk check found anything? Is it crashing anymore?

Depending on the situation, we will decide our next step.

But, as both the networking programs did not work with DV enabled, it lead me to search for your network drivers, and I found it:

[COLOR=Red][B]TP-LINK 300Mbps Wireless N Adapter[/B][/COLOR]
Driver    c:\windows\system32\drivers\[COLOR=Red]athurx.sys[/COLOR] (2.0.0.53, 1.83 MB (1,918,976 bytes), 18/01/2013 12:49)
--------------------------------------------------------------------------------------------------------------
start             end                 module name
fffff880`0560e000 fffff880`057e9000   athurx     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
[COLOR=Red]    Image name: athurx.sys
    Timestamp:        [B]Wed Jul 28 17:31:39 2010[/B][/COLOR] (4C501C23)
    CheckSum:         001DD606
    ImageSize:        001DB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from ATHEROS drivers for Microsoft Windows (Atheros?????) or the manufacturer's website.

[COLOR=Red][B]Realtek PCIe GBE Family Controller[/B][/COLOR]
Driver    c:\windows\system32\drivers\[COLOR=Red]rt64win7.sys[/COLOR] (7.52.203.2012, 661.60 KB (677,480 bytes), 18/01/2013 16:37)
--------------------------------------------------------------------------------------------------------------
start             end                 module name
fffff880`13d43000 fffff880`13deb000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
[COLOR=Red]    Image name: Rt64win7.sys
    Timestamp:        Fri Feb 03 18:30:02 2012 [/COLOR](4F2BDA52)
    CheckSum:         000A655F
    ImageSize:        000A8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek

Let us know the results.

 

[Brunolechef]

Scrap that, we tried to install updates, one failed and we got more BSOD's, what should we do know, atm we are in safe mode because we cannot get into normal.
cheers

Bruno

 

[Arc]

Do safe mode with networking, follow the Blue Screen of Death (BSOD) Posting Instructions . Let us see the latest crash dump.

 

[Brunolechef]

View attachment 251126

there you go mate, we managed to get back onto the normal mode, so we did it on that, is it important that we do it on safe mode, if not then can you post what we need to do to prevent the BSOD

cheers

Bruno

 

[Arc]

Bruno, see it, Driver Verifier is needed there.

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

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
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, [COLOR=Red]and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/COLOR]
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a0013392b0, The pool entry we were looking for within the page.
Arg3: fffff8a0013392f0, The next pool entry.
Arg4: 0000000005040103, (reserved)

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

GetUlongFromAddress: unable to read from fffff80002c33a38

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a0013392b0 Paged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bc0cae to fffff80002a95fc0

STACK_TEXT:  
fffff880`031bd9c8 fffff800`02bc0cae : 00000000`00000019 00000000`00000020 fffff8a0`013392b0 fffff8a0`013392f0 : nt!KeBugCheckEx
fffff880`031bd9d0 fffff800`02d7712c : fffff800`02c93600 fffff8a0`06917100 fffff8a0`624e4d43 00000000`50e7b159 : nt!ExDeferredFreePool+0x12da
fffff880`031bda80 fffff800`02d771c0 : fffff8a0`0120e6f8 00000000`6a37a282 fffff8a0`00023370 00000000`00000000 : nt!CmpDereferenceNameControlBlockWithLock+0xdc
fffff880`031bdab0 fffff800`02d571ef : fffff8a0`0120e6f8 fffff800`02d75730 fffff800`02c332d8 fffff800`00000000 : nt!CmpCleanUpKcbCacheWithLock+0x34
fffff880`031bdae0 fffff800`02d75921 : fffff8a0`0120e6f8 00000000`fcd5df3d fffff8a0`00023370 00000000`00000000 : nt!CmpDereferenceKeyControlBlockWithLock+0x13f
fffff880`031bdb10 fffff800`02a9f641 : fffff800`02c332d8 fffffa80`03d94b50 00000000`00000000 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0x1f1
fffff880`031bdb70 fffff800`02d2ce5a : 00000000`00000000 fffffa80`03d94b50 00000000`00000080 fffffa80`03cbe040 : nt!ExpWorkerThread+0x111
fffff880`031bdc00 fffff800`02a86d26 : fffff880`02fd7180 fffffa80`03d94b50 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpDereferenceNameControlBlockWithLock+dc
fffff800`02d7712c 488b157dc7f1ff  mov     rdx,qword ptr [nt!CmpNameCacheTable (fffff800`02c938b0)]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!CmpDereferenceNameControlBlockWithLock+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x19_20_nt!CmpDereferenceNameControlBlockWithLock+dc

BUCKET_ID:  X64_0x19_20_nt!CmpDereferenceNameControlBlockWithLock+dc

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

So enable Verifier again, let us see a couple of verifier enabled crash dumps.

 

[Brunolechef]

what do you mean driver verifier is needed their? where?for how long? and then how do i send you the enabled crash dumps? + when it was enabled last time, we saw BSOD, is that normal?
cheers
Bruno

 

[Arc]

what do you mean driver verifier is needed their? where?for how long? and then how do i send you the enabled crash dumps? + when it was enabled last time, we saw BSOD, is that normal?
cheers
Bruno

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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

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

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

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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

AND, Driver Verifier will cause BSOD. It is employed to create BSODs. It is not only normal, but also expected.

 

[Brunolechef]

when doing the DV, do we also have to check NVidia and Realtek and leave ALL the microsoft?

cheers

bruno

 

[Brunolechef]

and do we need to leave the computer running for 24 hours?

 

[Arc]

May not for at a stage, but use the computer for at least 24 hours with DV enabled. However, if it is to crash, it will not take that long.

 

[Brunolechef]

so if there is another BSOD while running DV, then we can disable the DV and send you the crash report?

 

[Arc]

Yes. Do it.

 

[Brunolechef]

okay then, how do we know if DV is running, is there another way off telling apart from it being slow and laggy?

 

[Arc]

Apparently, no.

 

[Brunolechef]

ohh... i did it, and restarted ( but i had to restart it myself, the program didnt do it) but my comp doesnt seem any slower, should i presume its working?

 

[Arc]

Disable Driver verifier, and enable it again, following the instructions line by line.

:ar: Driver Verifier - Enable and Disable

 

[Brunolechef]

ive followed everything, so im guessing thats its enabled, there was no pop up to say that it was, it just, you must restart your comp for changes to take place, i clicked okay then i restarted the comp. so, did i do it right?