Fresh Install...NTOSKRNL.exe?

[bodhisattva]

Windows 7 Pro x64 SP1, fresh install

Hardware Build:
x58a-ud3r
i7-970

Less than 24hrs into the installation, after updated chipset drivers, I've had three BSODs (all of which are included in the attached dump.zip

It is my belief that it could be a bad ram module but a second opinion would be terrific in light of this new data.

Thanks, in advance,
Bodhi

 

[zigzag3143]

Windows 7 Pro x64 SP1, fresh install

Hardware Build:
x58a-ud3r
i7-970

Less than 24hrs into the installation, after updated chipset drivers, I've had three BSODs (all of which are included in the attached dump.zip

It is my belief that it could be a bad ram module but a second opinion would be terrific in light of this new data.

Thanks, in advance,
Bodhi

Memory management caused by your video driver. re-install like this

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

When it is removed then download and install the fresh copy.

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\042411-12682-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`0325fe90
Debug session time: Sun Apr 24 15:48:36.823 2011 (GMT-4)
System Uptime: 0 days 2:50:51.697
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8004195ad0, ffff, 0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8004195ad0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003107fd0 to fffff8000309a640

STACK_TEXT:  
fffff880`09ae7f08 fffff800`03107fd0 : 00000000`0000001a 00000000`00041790 fffffa80`04195ad0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09ae7f10 fffff800`03087aef : fffffa80`00000000 00000000`0837ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09ae80d0 fffff800`030998d3 : ffffffff`ffffffff fffff8a0`14b4b2b0 fffff8a0`14b4b2b8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`09ae81d0 fffff800`03095e70 : fffff880`055661cf fffff8a0`0c3d69e0 fffff8a0`14b4b290 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09ae8368 fffff880`055661cf : fffff8a0`0c3d69e0 fffff8a0`14b4b290 00000000`00000000 fffffa80`08de56d0 : nt!KiServiceLinkage
fffff880`09ae8370 fffff880`0556563c : fffff8a0`07897b80 fffff8a0`07897b80 00000000`00000000 fffff8a0`0c3e94e0 : dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+0x53
fffff880`09ae83a0 fffff880`0556554a : fffffa80`00000000 fffffa80`08aed060 fffffa80`08de56d0 fffff880`09ae8478 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0xdc
fffff880`09ae83d0 fffff880`05550b5a : fffff880`09ae83f8 fffff8a0`07317e70 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`09ae8400 fffff880`0554b523 : fffffa80`091d6f70 00000000`00000000 fffff8a0`0c3d69e0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`09ae84b0 fffff880`05531ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`09ae8580 fffff880`04aecccc : 00000000`00000000 fffff8a0`0e73a000 fffff8a0`0e73a000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`09ae85b0 fffff880`04aff784 : fffffa80`066dc000 00000000`00000000 00000000`00000000 fffff8a0`0e73a068 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`09ae86a0 fffff880`04ae4815 : 00000000`fffffeda fffff8a0`0df220d0 fffff8a0`0e73a000 fffffa80`066dc000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`09ae8710 fffff880`04b22e4a : 00000000`00000000 fffffa80`066dc000 fffff8a0`0df220d0 fffff8a0`0df22150 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`09ae8740 fffff880`04b227e0 : fffff900`c1c6ece0 00000000`00000000 00000000`00000001 fffff900`c1c6ece0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`09ae87f0 fffff960`000d50f4 : 00000000`00001284 fffff900`c1c6ece0 00000000`00000000 fffff900`c1c6ece0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`09ae8880 00000000`00001284 : fffff900`c1c6ece0 00000000`00000000 fffff900`c1c6ece0 fffffa80`08aed060 : win32k+0xc50f4
fffff880`09ae8888 fffff900`c1c6ece0 : 00000000`00000000 fffff900`c1c6ece0 fffffa80`08aed060 fffff960`000d4758 : 0x1284
fffff880`09ae8890 00000000`00000000 : fffff900`c1c6ece0 fffffa80`08aed060 fffff960`000d4758 fffff900`c1c6ece0 : 0xfffff900`c1c6ece0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53
fffff880`055661cf 488b0f          mov     rcx,qword ptr [rdi]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53

BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53

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

 

[bodhisattva]

Thank you, for your help. I did what you had asked of me and things seem to be running well.

Windows still won't verify the AMD drivers on startup though. I suppose thats none of my concern so long as things continue to operate.

I will report back if necessary.

Thanks, again,
Bodhi