crash, freeze, lock up

right, well side pannel has been off for 2 days now, the card is relativly cold to the touch, i will just try another display only driver and wait for a crash and or bsod... you dont think an update from microsoft could be causing this? or a failing / dieing hdd?

 

It could be an update clashing with an installed driver, a buggy driver or failing hardware, as noted by the BSOD analysis in #41.

 

i just think its odd... nothing changed in my hardware or software around the first time of this happening appart from some windows updates... i think im just gonna keep juggling drivers to see if anything changes, keep searching the internet to see if anything similar has happened (which could be linked to updates) but then im gonna buy a new HDD to put windows on, appart from anything else, this one i have now is really old 6 years + and has been formatted that many times...

 

was on bad company for 4 hours the other night, no problem, went on it for a good 2 hours last night, no problem, went on GTA IV this morning, came off it, bsod, restarted computer, nothing but black screen, restarted it again, froze on start up screen, restart again, something was wrong with bios and it reset itself to default =/ managed to get back on my comp, here are the 3 .dmp files that i got within 4 mins of each other

 

Try working through this list that looks like they may be similar to the 0xD1 from 050411-31044-01.dmp.

 

had another one yesterday but it didnt produce a .dmp file, just said hardware failure... would be nice if it said what had failed lol anyway got a new 1tb hdd on the way, will do a fresh instalation of windows onto it, and see how it goes then, im putting money on hdd or motherboard at this moment in time, but sods law will mean that now ive bought a hdd, it will be the motherboard lol

 

this one is an interesting one, pool corruption? and also something to do with discache.sys... when reading up on tht i see a lot of mention of malware / spyware / virus

 

Judging by the date, discache.sys was installed as part of Windows and is part of the indexer/caching system. 0x19 is usually a bad driver.

Code:

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


Loading Dump File [C:\Windows\Minidump\050711-41886-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Sat May  7 18:39:24.985 2011 (UTC + 1:00)
System Uptime: 0 days 0:47:38.006
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff80002e4c9d0, fffff80002e4c9d0, e56c69460215000c}

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

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

3: 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: fffff80002e4c9d0, the pool entry being checked.
Arg3: fffff80002e4c9d0, the read back flink freelist value (should be the same as 2).
Arg4: e56c69460215000c, 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:  WinSAT.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002df0d6f to fffff80002cbd740

STACK_TEXT:  
fffff880`0ac0f208 fffff800`02df0d6f : 00000000`00000019 00000000`00000003 fffff800`02e4c9d0 fffff800`02e4c9d0 : nt!KeBugCheckEx
fffff880`0ac0f210 fffff880`041a5e98 : fffff880`00000000 00000000`00000000 fffffa80`06ced000 00000000`00000000 : nt!ExDeferredFreePool+0xa56
fffff880`0ac0f300 fffff880`0418caa7 : fffff8a0`0b7b1900 fffff8a0`0cb9c170 fffff880`0ac0f470 00000000`00000000 : [B]dxgmms1!VIDMM_GLOBAL:[/B]:OpenOneAllocation+0x1c8
fffff880`0ac0f3e0 fffff880`040d8469 : 00000000`00000000 fffff880`0ac0f8b0 00000000`00000000 fffff8a0`0cdce360 : [B]dxgmms1!VidMmOpenAllocation[/B]+0xeb
fffff880`0ac0f430 fffff880`040d1610 : fffff880`0ac0f698 fffff8a0`0430ca30 fffff880`0ac0f870 fffff880`0ac0f870 : [B]dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>[/B]+0x291
fffff880`0ac0f4c0 fffff880`040d426b : fffff8a0`037d4000 fffff880`0ac0fb30 fffff880`0ac0fc01 00000000`00000000 : [B]dxgkrnl!DXGDEVICE::CreateAllocation[/B]+0xca8
fffff880`0ac0fac0 fffff960`0019db1e : 00000000`053fc450 00000000`c0000240 00000000`045a67d8 fffff800`000007d3 : [B]dxgkrnl!DxgkCreateAllocation[/B]+0x42b
fffff880`0ac0fbf0 fffff800`02cbc993 : 00000000`15fb56f8 fffff880`0ac0fca0 00000000`045a68a4 00000000`00000001 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0ac0fc20 000007fe`fe10460a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`053fc368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe10460a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a56
fffff800`02df0d6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a56

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

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56

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

Looking at the STACK_TEXT information, I'd have to say it looks like graphics card or drivers.

If you suspect that you might have a malware problem, start here. Read it carefully.

 

right new hard drive, new installation of windows.... crash =/ i know there is something failing on the computer, its told me theres a hardware failure that many times now, but without throwing more money at the problem (money i dont have) what could be causing this? ive done a memory test, the cpu and ram are find, ive tested a different card, still got crashes, so how do i test the motherboard and / or psu ?

 

Has the BIOS been set to defaults? Windows fully updated? The latest hardware drivers installed?

Do you have a new dump to upload from the latest crash?

 

the crash was just a freeze crash, the bios reset its self to default again... for some reason, all drivers tht i need to put on at this moment in time have been put on, and windows is just updating it self as normal =/ im slightly worried that something could be set wrong in the bios, but i have had no experience with anythign in the bios so i wouldnt know what to touch, i guess when you buy a motherboard everhting is set to default then?

 

here ya go, 3 fresh ones. ive not had chance to look at them as it keeps crashing every time i try to put the tools on, will try later

 

Revisit #41 again and install the Realtek network card driver please, I see you still have one installed that's 2+ years old, don't entrust device driver updates to Device Manager, it only checks those listed on the MSFT Update site.

2 of the dumps are 0x3b:

We've already ruled out memory, I think; this leaves us with System service, Device driver, graphics driver. The 3rd dump is a 0xD1:

I see ASACPI.sys listed in the dump here, it's from March 2005:

Uninstall whatever software is loading this or update it from the above ASUS link. Check for other updated software specific to your motherboard while you're there.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000094, fffff80002ba89c3, fffff880072f0770, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+8d3 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000094, Exception code that caused the bugcheck
Arg2: fffff80002ba89c3, Address of the instruction which caused the bugcheck
Arg3: fffff880072f0770, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
nt!CmpKcbCacheLookup+8d3
fffff800`02ba89c3 f7b718060000    div     eax,dword ptr [rdi+618h]

CONTEXT:  fffff880072f0770 -- (.cxr 0xfffff880072f0770)
rax=000000001e637e73 rbx=0000000000000000 rcx=000000001e637e73
rdx=0000000000000000 rsi=0000000000000011 rdi=fffff8a000770010
rip=fffff80002ba89c3 rsp=fffff880072f1140 rbp=fffff8a00075ade3
 r8=0000000000000000  r9=000000000000fffe r10=0000000000000000
r11=fffff880072f12d8 r12=fffff8a00741e380 r13=0000000000000001
r14=fffff8a0007676f8 r15=fffff8a0007676f8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!CmpKcbCacheLookup+0x8d3:
fffff800`02ba89c3 f7b718060000    div     eax,dword ptr [rdi+618h] ds:002b:fffff8a0`00770628=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ba89c3

STACK_TEXT:  
fffff880`072f1140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x8d3


FOLLOWUP_IP: 
nt!CmpKcbCacheLookup+8d3
fffff800`02ba89c3 f7b718060000    div     eax,dword ptr [rdi+618h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpKcbCacheLookup+8d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

STACK_COMMAND:  .cxr 0xfffff880072f0770 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+8d3

BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+8d3

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000ea39e, fffff88007df1f20, 0}

Probably caused by : win32k.sys ( win32k!ThreadUnlock1+3e )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000ea39e, Address of the instruction which caused the bugcheck
Arg3: fffff88007df1f20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!ThreadUnlock1+3e
fffff960`000ea39e 0fb64111        movzx   eax,byte ptr [rcx+11h]

CONTEXT:  fffff88007df1f20 -- (.cxr 0xfffff88007df1f20)
rax=0000000000135480 rbx=fffff900c1cc6508 rcx=fffff900c0535480
rdx=fffff900c080ce10 rsi=0000000000000001 rdi=fffff900c1cc63f0
rip=fffff960000ea39e rsp=fffff88007df28f0 rbp=fffff88007df29b0
 r8=fffff80002817000  r9=0000000000000000 r10=fffff900c1c695f0
r11=fffff88007df28a0 r12=fffff960000c5f10 r13=0000000000000001
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!ThreadUnlock1+0x3e:
fffff960`000ea39e 0fb64111        movzx   eax,byte ptr [rcx+11h] ds:002b:fffff900`c0535491=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MOM.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960000ea39e

STACK_TEXT:  
fffff880`07df28f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!ThreadUnlock1+0x3e


FOLLOWUP_IP: 
win32k!ThreadUnlock1+3e
fffff960`000ea39e 0fb64111        movzx   eax,byte ptr [rcx+11h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!ThreadUnlock1+3e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d6f11c9

STACK_COMMAND:  .cxr 0xfffff88007df1f20 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!ThreadUnlock1+3e

BUCKET_ID:  X64_0x3B_win32k!ThreadUnlock1+3e

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

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af50e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+3231333437363436
00000000`00000000 ??              ???

PROCESS_NAME:  dwm.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff8800770e730 -- (.trap 0xfffff8800770e730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffffd6000 rbx=0000000000000000 rcx=00000000c0000102
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8800770e8c0 rbp=fffffa8008968000
 r8=fffffa80091abbb8  r9=0000000000000000 r10=fffffffffffffffd
r11=00000000002f8900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028bcc69 to fffff800028bd700

FAILED_INSTRUCTION_ADDRESS: 
+3231333437363436
00000000`00000000 ??              ???

STACK_TEXT:  
fffff880`0770e8c0 fffff880`00000001 : fffff880`0770e9b0 fffff880`0770e900 fffff800`028d9c11 fffffa80`08a2a000 : 0x0
fffff880`0770e8c8 fffff880`0770e9b0 : fffff880`0770e900 fffff800`028d9c11 fffffa80`08a2a000 00000000`00000001 : 0xfffff880`00000001
fffff880`0770e8d0 fffff880`0770e900 : fffff800`028d9c11 fffffa80`08a2a000 00000000`00000001 fffff880`0770e9b0 : 0xfffff880`0770e9b0
fffff880`0770e8d8 fffff800`028d9c11 : fffffa80`08a2a000 00000000`00000001 fffff880`0770e9b0 fffff880`04807f76 : 0xfffff880`0770e900
fffff880`0770e8e0 fffff800`02af7840 : fffff880`0491a0d0 fffffa80`00000000 00000000`00000000 00000000`000002b2 : nt!MiDispatchFault+0x831
fffff880`0770e9f0 fffff880`0491a0d0 : fffffa80`00000000 00000000`00000000 00000000`000002b2 00000000`00000028 : nt!MmFreePageListHead
fffff880`0770e9f8 fffffa80`00000000 : 00000000`00000000 00000000`000002b2 00000000`00000028 fffff880`0491b93c : atikmdag+0x490d0
fffff880`0770ea00 00000000`00000000 : 00000000`000002b2 00000000`00000028 fffff880`0491b93c fffffa80`051f4000 : 0xfffffa80`00000000


STACK_COMMAND:  .trap 0xfffff8800770e730 ; kb

FOLLOWUP_IP: 
atikmdag+490d0
fffff880`0491a0d0 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmdag+490d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d23dc14

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_atikmdag+490d0

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_atikmdag+490d0

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

 

i cant find what ever is loading that, or useing it, i never installed anything called Asus PCProbe and AISuite Utilities... but ive updated the Asus ATK0110 from the asus website. Ive updated the realtek network driver too

 

nope just got another bsod but it froze on the bsod so i didnt get a .dmp file, then it froze on the logon screen

 

A description of what you were doing prior to the hang might help, as would an indication of the programs that were running.

Try uninstalling the Asus ATK0110 now.

 

was just browsing the internet (about the most i can do at the moment, got no games installed, nor have i begun to put any programs back on)

just had another freeze when sorting my backup harddrive out, on the loading screen (black screen white writing) sorry dunno what the propper name for it is, it had the read out of my system etc then at the bottom it said "overclocking failed! overvoltage failed! " press f1 to enter bios press f2 to load default values and continue " so i pressed f2.... the bios has been reset a few times to default now so why is it saying that? the only thing that is overclocked is the card but that is what asus do, its automatically overclocked out of the box, ive not done ANYTHING to the card

 

That's a great way to lose your backup data. Disconnect anything that isn't a vital part of troubleshooting the problem.

Ok, so you were on the Internet but you don't know, or aren't going to tell me, what programs were running, fine.

 

Right back up hard drive disconnected. Sorry all I had running was steam to talk to my mates that's it

 

2 new ones.... first one happened when i was browsing the internet www.gametrailers.com , again only steam was running

second one happened when i was updateing a game ive just put on (medal of honor) again only steam was running

 

Ok, let's get this rig down to basic hardware - uninstall and remove the old Soundblaster card; while you're inside the case, clean out the fans and heatsinks carefully, check and reseat the gfx card and RAM, check and reseat all power connectors.

Reset the BIOS to defaults, reboot.

Download Avast! and download the AVG removal tool. Uninstall AVG, reboot then use the AVG removal tool to ensure it's all gone. Reboot again, install Avast! and update it.

Download, install and run OCCT to stress the machine, set it so you can see the graph of temps and voltages.

Please don't install anything else, let's try to get to the root of the problem and fix it before adding anything into the mix.

 

right okay, will start doing tht tonight when i finish work, is avast! better then avg then? ive been hearing mixed feelings in regards to avg recently but ive been using it for years

 

Avast! is a little more controllable than AVG, which has become a little overblown in recent years.

 

Sorry ive not been on sooner, i took my computer to someone at my place of work to look at for me, it was really getting me down... the motherboard was faulty. I really want to thank you satrow, youve been such a great help and thank you for putting up with my stupidity at times :-o

 

Hardware errors trump everything; I'm pleased you got to the root of it