BSOD on shutdown after long sessions

[d10kn]

View attachment 303821

Greetings everyone

I recently updated my GPU and PSU, I used to have a Radeon HD 7450 and upgraded to a HD6670, and a new 550W PSU.

A few days back I noticed that after trying to shutdown my PC, some minutes would go on and it would be still on (I usually turn off my screen when I click 'shutdown' ) , so I noticed it had a BSOD, it had been the first time EVER for me to get one, so I shrugged it off and proceeded to shut it down anyway.

It has happened two more times after that, the second time thinking it had to do with the new GPU I installed, I uninstalled the drivers and reinstalled them again, then rebooted the pc. No BSOD happened at that time.

Then a BSOD happened yet again, and I thought it had to do with the memory somehow, seeing as it only happened when I had my PC on for long times.

I'd really appreciate any help you guys could give me.

 

[Arc]

Hi d10kn.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Also, uninstall the display driver in full. Then clean up any possible leftovers. Then install 13.9 WHQL of the display driver.

Let us know the results.
_________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, 800000000000000, 0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmCloseAllocation+5d )

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: 0000000000000022, 
Arg2: 0800000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x19_22

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370b0e0
GetUlongFromAddress: unable to read from fffff8000370b198
 0800000000000000 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  FirefallInstal

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000352c330 to fffff800034d4f00

STACK_TEXT:  
fffff880`0916d808 fffff800`0352c330 : 00000000`00000019 00000000`00000022 08000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0916d810 fffff800`03608518 : 00000000`00000000 fffff880`0916d960 fffff880`0916d8d0 fffff880`00000001 : nt! ?? ::FNODOBFM::`string'+0x7338
fffff880`0916d8a0 fffff880`06c01ee5 : 00000000`00000000 fffffa80`00000000 00000000`6d4d6956 00000000`00000000 : nt!ExFreePoolWithTag+0x468
fffff880`0916d950 fffff880`06d1cc10 : 00000000`00000000 fffff8a0`0197a000 fffff8a0`0197a000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x5d
fffff880`0916d980 fffff880`06d1c54b : fffff8a0`0197a000 fffff8a0`0197b300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0916da70 fffff880`06d2218f : 00000000`00000799 00000000`00000001 fffff880`0916dca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0916dac0 fffff960`0021b1d6 : 00000000`065ae7a0 00000000`c0002080 00000000`00000000 fffff800`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b
fffff880`0916dbf0 fffff800`034d4153 : 00000000`00000000 00000000`00000501 fffffa80`04836a80 fffffa80`0902b460 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0916dc20 00000000`7380119a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`065ae758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7380119a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmCloseAllocation+5d
fffff880`06c01ee5 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidMmCloseAllocation+5d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

IMAGE_VERSION:  6.1.7600.16385

FAILURE_BUCKET_ID:  X64_0x19_22_dxgmms1!VidMmCloseAllocation+5d

BUCKET_ID:  X64_0x19_22_dxgmms1!VidMmCloseAllocation+5d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x19_22_dxgmms1!vidmmcloseallocation+5d

FAILURE_ID_HASH:  {f4b33a7f-8267-b0e5-cae5-b9a4891273b9}

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

 

[d10kn]

Thanks for the reply,

So far so good, though between reboots I haven't been able to get in a long session, I'll test it out for a few more days and come back to you.

 

[Arc]

Its ok, let us know how the computer is running.