I can't believe I'm back here again. My system has been running great for so long. But I guess this is what happens when you install and try alot of software. My BSOD's are coming from ntosknrl.exe, tcpip.sys, and dxgkrnl.sys. I've included the obligatory dumps and perfmon. Could someone please look at them and see what the problem could be? I feel so helpless when my 'puter is sick and I don't know what to do about it.
These are all blamed on your video driver. Please re-install using these instructions
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
Or Phyxion.net - Driver Sweeper
When it is removed then download and install the fresh copy.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050911-22339-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03a68000 PsLoadedModuleList = 0xfffff800`03cade90
Debug session time: Mon May 9 00:56:55.336 2011 (GMT-4)
System Uptime: 0 days 1:29:42.304
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffff8a0054da590, fffff8a0054dacd0, 5740069}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::CreateDriverAllocations<_DXGK_ALLOCATIONINFO,_DXGKARG_CREATEALLOCATION>+824 )
Followup: MachineOwner
---------
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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a0054da590, The pool entry we were looking for within the page.
Arg3: fffff8a0054dacd0, The next pool entry.
Arg4: 0000000005740069, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d190e8
fffff8a0054da590
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003c12cae to fffff80003ae8640
STACK_TEXT:
fffff880`0744abe8 fffff800`03c12cae : 00000000`00000019 00000000`00000020 fffff8a0`054da590 fffff8a0`054dacd0 : nt!KeBugCheckEx
fffff880`0744abf0 fffff880`042bcc8c : ffffffff`c000000d 00000000`00000000 fffff880`4b677844 00000000`00000000 : nt!ExDeferredFreePool+0x12da
fffff880`0744aca0 fffff880`042b6511 : fffff8a0`00000000 fffff880`ffffdade fffff880`0744af10 fffff880`0744b0f0 : dxgkrnl!DXGDEVICE::CreateDriverAllocations<_DXGK_ALLOCATIONINFO,_DXGKARG_CREATEALLOCATION>+0x824
fffff880`0744ad40 fffff880`042b926b : fffff8a0`0e011000 fffff880`0744b3b0 fffff880`0744b501 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xba9
fffff880`0744b340 fffff960`0019ddf2 : 00000000`0008c4b0 fffffa80`400004c0 00000000`0008ce50 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x42b
fffff880`0744b470 fffff800`03ae78d3 : 00000000`0023bb90 fffff880`0744b520 00000000`0138efc0 00000000`fffdb000 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0744b4a0 00000000`7375119a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008c468 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7375119a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DXGDEVICE::CreateDriverAllocations<_DXGK_ALLOCATIONINFO,_DXGKARG_CREATEALLOCATION>+824
fffff880`042bcc8c 8bc6 mov eax,esi
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!DXGDEVICE::CreateDriverAllocations<_DXGK_ALLOCATIONINFO,_DXGKARG_CREATEALLOCATION>+824
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799fa
FAILURE_BUCKET_ID: X64_0x19_20_VRF_dxgkrnl!DXGDEVICE::CreateDriverAllocations__DXGK_ALLOCATIONINFO,_DXGKARG_CREATEALLOCATION_+824
BUCKET_ID: X64_0x19_20_VRF_dxgkrnl!DXGDEVICE::CreateDriverAllocations__DXGK_ALLOCATIONINFO,_DXGKARG_CREATEALLOCATION_+824
Followup: MachineOwner
---------
Old drivers that must be updated
Code:
athrxusb.sys 7/29/2008 08:47:13 AM fffff880`02b21000 0x0010d000 0x488f1151 fffff880`02a14000
000.fcl 9/26/2008 09:11:22 AM fffff880`06a6a000 0x0002b000 0x48dcdf7a fffff880`06a3f000
purendis.sys 10/28/2008 12:31:28 AM fffff880`04911000 0x0000c000 0x490695a0 fffff880`04905000
pnarp.sys 10/28/2008 01:57:00 AM fffff880`048fa000 0x0000c000 0x4906a9ac fffff880`048ee000
pnpcap.sys 10/28/2008 09:12:25 AM fffff880`04905000 0x0000b000 0x49070fb9 fffff880`048fa000
mrdd.sys 11/12/2008 02:44:48 AM fffff880`019fb000 0x0000a000 0x491a7b60 fffff880`019f1000
mv61xx.sys 2/8/2009 10:19:46 PM fffff880`01246000 0x00046000 0x498f92c2 fffff880`01200000
TSKNF900.SYS 4/19/2009 03:31:15 AM fffff880`042f8000 0x0000a000 0x49ead343 fffff880`042ee000
ALSysIO64.sys 4/19/2009 03:41:04 PM fffff880`07a27000 0x00008000 0x49eb7e50 fffff880`07a1f000
spldr.sys 5/11/2009 12:56:27 PM fffff880`018ed000 0x00008000 0x4a0858bb fffff880`018e5000
amdxata.sys 5/19/2009 01:56:59 PM fffff880`01251000 0x0000b000 0x4a12f2eb fffff880`01246000
ADIHdAud.sys 5/21/2009 04:21:06 AM fffff880`05bf5000 0x00079000 0x4a150ef2 fffff880`05b7c000
iaStor.sys 6/4/2009 09:53:40 PM fffff880`013a0000 0x0011c000 0x4a287aa4 fffff880`01284000
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Quote