Windows Vista Vista Shutting Down under 3D Apps

Well I am at my wits end.

I consider myself fairly knowledgeable when it comes to PC's and ... Vista.
But this one has me stumped for i have tried so many solutions and situational diagnostic approaches that this just is now frustrating cause I have to work from my PC.

About a week ago my PC began to reboot when running 3D apps. Everything else is fine just running 3D apps and games requiring such.

System Specs.

Vista Home Premium 32bit.

Mobo: GiGabyte S-Series GA-G33M-DS2R
Processor: Intel Core 2 Duo 2.2Gig
GPU: (Sapphire) ATI Radeon HD 4850 (larger fan release)
RAM:4gig Geil Dual Channel DDR2
HD: Seagate Barracuda 7200.20
PSU: Corsair HX620
3 x 80mm Case fans (so enough but could be more)

I have tried.

Turning off the auto reboot to get the BSOD.
Initially that worked I got a minidump file that told me that Shadow copy service had caused it and so I turned that off. it could have been an issue where it didn't have enough HD space to make or Upgrade another copy. Mind you I turned it off ages ago it just seems that it turned itself on again.

..anyway moving on. At first it was just now and then once maybe twice a day I began to thought it a heat issue with summer days getting distinctly warmer. So i opened up the case and to let the system breath a little more and on cooler nights i can get it to run for a while.

But Now it just shuts down completely as if someone had hit the off button, on any 3D app. Games let it run for a while. Secondlife will not load even the bootup screen before it just "#@!*s" and shuts down. Sometimes it will get beyond it only to shut down 5 minutes later.

I have run Prime95 and it ran stable and constant for over an hour before I ended the Torture test so it's not CPU or Ram Functionality (I have reseated the ram and many of my connections since).

When running rthdribl to benchmark the 3D performance it has no issue with it at all. Temps run rather stable and often don't peak over 62 degrees C.

I am really leaning towards heat but from where?
Observational Diagnostics prove that it runs longer in cooler Ambient Temperatures, even moreso with a desktop fan pointed directly at the GPU. But case closed under it's own cooling forget about it.

I have reinstalled with the latest GPU Drivers.

This system has been running stable for a couple of months (I recently replaced the GPU those are the couple of months, before then Since I built it. It has been stable) but has chosen only now to do this.

Currently losing Income as we speak.
Would really appreciate any Help. anything at all. Please.

 

Dump File

Ok when I rebooted just now to check the CPU temp in Bios, I got a BSOD which i hadn't had for a while. For 2 days it has just been the shut-downs under 3D apps. This isn't the cause of the shut-downs but is something else. When I was reseating connections and I restarted the system Vista for some God only knows reason decided that it wanted to reinstall all my USB drivers, and it did so successfully. But I think this is a result of it somehow. MiniDump follows. 3D apps restart still the primary Concern.

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini110508-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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x8241d000 PsLoadedModuleList = 0x82534c70
Debug session time: Wed Nov 5 21:58:52.283 2008 (GMT+10)
System Uptime: 0 days 1:03:38.181
Loading Kernel Symbols
..............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {869aed58, e7a, 0, 0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_CompleteAbortRequest+2d3 )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 869aed58, Address of the IRP
Arg2: 00000e7a
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS: 869aed58

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x44

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 824574ac to 824ea0e3

STACK_TEXT:
805ecbfc 824574ac 00000044 869aed58 00000e7a nt!KeBugCheckEx+0x1e
805ecc3c 807d13c5 824714c4 87c1ecb0 00000000 nt!IopfCompleteRequest+0x4b9
805ecc58 807bbb6f 02626163 86c43b30 33626163 USBPORT!USBPORT_Core_CompleteAbortRequest+0x2d3
805ecc9c 807bc0b1 869a5028 869a5bf8 824714c4 USBPORT!USBPORT_Core_FlushCompletedAborts+0x32e
805eccc0 807b5274 869a5028 869a5bf8 869a5002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x169
805ecce8 824d3450 869a5c04 34776478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x274
805ecd50 824d1edd 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
805ecd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_CompleteAbortRequest+2d3
807d13c5 8a4d0b mov cl,byte ptr [ebp+0Bh]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: USBPORT!USBPORT_Core_CompleteAbortRequest+2d3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 47919053

FAILURE_BUCKET_ID: 0x44_USBPORT!USBPORT_Core_CompleteAbortRequest+2d3

BUCKET_ID: 0x44_USBPORT!USBPORT_Core_CompleteAbortRequest+2d3

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

 

Cooling seems to be a problem with this card
http://www.overclockersclub.com/reviews/sapphire_hd4850/15.htm

 

Possibly Resolved? An unlikely Culprit.

Well I just had Second Life (which is a big bench tester) running for 3 hours with no shutdowns where previously I couldn't get 5 mins out of it.

It appears as though the culprit (albeit a very unlikely one) was a set of USB drivers that I installed a while back that made the Playstation 3, 6 axis controllers compatible with Vista.

(This dawned on me after reading the BSOD report again)

Vista Installs a recent update, doesn't care for it one bit and viola! you have USB driver conflict resulting in shutdown because almost all of my external perhipheral devices are USB based. How this could even appear as over heating is totally beyond me though.

By removing them it seems to have stabilized the 3D apps and removed the constant BSOD i was getting for most of the night when shutting down.
It seems that Vistas want for installing a new set of USB drivers has actually saved me a whole lot of grief, cause if it didn't install those I doubt I would have picked up on this at all.

I will let you know if I am capable of holding a full work day tomorrow, If I can I will let you know so we can sweep this under the carpet.

 

No Go

Well that wasn't it. Looks liek the 3 hour run on SL was a fluke.

Talked to my Rep at Umart today the place where I get my parts.
He suggested Memtest so i did that, at first all 4 gig passed.
However then he suggested trying just the 2 1g sticks I bought recently and when the system rebooted by itself under memtest examination he declared at least one of them faulty.

So now i am running on only 2 gig of Ram which vista totally hates...worse the problem persists. 3D apps still crashing at an indeterminate interval. Some get to thier loading screens and bail others play for maybe up to half an hour before they pack it in.

My guy suggested updating my bios which I did to no avail.
Looks like i am going to have to take it down to them and spend the 45 bucks to let them deal with it.

 

Ok but thats a pretty big file here is the core details of the CPU from cpuz.

Processors Information
------------------------------------------------------------------------------------

Processor 1 (ID = 0)
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name Intel Core 2 Duo E4500
Codename Conroe
Specification Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
Package Socket 775 LGA (platform ID = 0h)
CPUID 6.F.D
Extended CPUID 6.F
Core Stepping M0
Technology 65 nm
Core Speed 2200.2 MHz (11.0 x 200.0 MHz)
Rated Bus speed 800.1 MHz
Stock frequency 2200 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 2048 KBytes, 8-way set associative, 64-byte line size
FID/VID Control yes
FID range 6.0x - 11.0x
max VID 1.275 V
Features XD

Need other info just say the word.

But I can't wait much longer to fix this, I am probably going to take it to the shop and cough up the dough to get them to do it.

Temps looks reasonable in Bios.

 

Yeah hawk that was the old HD 4850 the new ones have a bigger fan allowing for fairly stable Temps of around 60 to 70c under full load.

 

Last time I checked in the Bios it was running at 45c. Tonight I checked again and it was running at 36c, Case was at 43c, and CPU Fan was running at 2775 rpm on average.
Does that seem a little low?

Another BSOD this time when rebooting after getting that data from bios. It would appear that my system is really just going to shite.

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini110608-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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x8241f000 PsLoadedModuleList = 0x82536c70
Debug session time: Thu Nov 6 23:00:10.465 2008 (GMT+10)
System Uptime: 0 days 0:00:12.355
Loading Kernel Symbols
................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {d668, 2, 0, 8250c15e}

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

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

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000d668, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8250c15e, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+159
8250c15e 8b10 mov edx,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: 88d5fbec -- (.trap 0xffffffff88d5fbec)
ErrCode = 00000000
eax=0000d668 ebx=00000014 ecx=000001ff edx=825217bc esi=825217bc edi=825216e0
eip=8250c15e esp=88d5fc60 ebp=88d5fc98 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
nt!ExDeferredFreePool+0x159:
8250c15e 8b10 mov edx,dword ptr [eax] ds:0023:0000d668=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8250c15e to 82479d24

STACK_TEXT:
88d5fbec 8250c15e badb0d00 825217bc 8464f7c8 nt!KiTrap0E+0x2ac
88d5fc98 8250d6e0 825216e0 00000001 00000000 nt!ExDeferredFreePool+0x159
88d5fd00 8242ac23 86841850 32706e50 8252113c nt!ExFreePoolWithTag+0x852
88d5fd44 82457445 00000000 00000000 8427b020 nt!PnpDeviceActionWorker+0x325
88d5fd7c 825f4b18 00000000 1e3170bd 00000000 nt!ExpWorkerThread+0xfd
88d5fdc0 8244da2e 82457348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+159
8250c15e 8b10 mov edx,dword ptr [eax]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+159

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+159

BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+159

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

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000d668, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8250c15e, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+159
8250c15e 8b10 mov edx,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: 88d5fbec -- (.trap 0xffffffff88d5fbec)
ErrCode = 00000000
eax=0000d668 ebx=00000014 ecx=000001ff edx=825217bc esi=825217bc edi=825216e0
eip=8250c15e esp=88d5fc60 ebp=88d5fc98 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
nt!ExDeferredFreePool+0x159:
8250c15e 8b10 mov edx,dword ptr [eax] ds:0023:0000d668=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8250c15e to 82479d24

STACK_TEXT:
88d5fbec 8250c15e badb0d00 825217bc 8464f7c8 nt!KiTrap0E+0x2ac
88d5fc98 8250d6e0 825216e0 00000001 00000000 nt!ExDeferredFreePool+0x159
88d5fd00 8242ac23 86841850 32706e50 8252113c nt!ExFreePoolWithTag+0x852
88d5fd44 82457445 00000000 00000000 8427b020 nt!PnpDeviceActionWorker+0x325
88d5fd7c 825f4b18 00000000 1e3170bd 00000000 nt!ExpWorkerThread+0xfd
88d5fdc0 8244da2e 82457348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+159
8250c15e 8b10 mov edx,dword ptr [eax]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+159

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+159

BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+159

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

0: kd> .trap 0xffffffff88d5fbec
ErrCode = 00000000
eax=0000d668 ebx=00000014 ecx=000001ff edx=825217bc esi=825217bc edi=825216e0
eip=8250c15e esp=88d5fc60 ebp=88d5fc98 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
nt!ExDeferredFreePool+0x159:
8250c15e 8b10 mov edx,dword ptr [eax] ds:0023:0000d668=????????

 

Wrapped Up

Ok guys thanks for your help.

Turns out it was my power supply, failing. Which I really thought it wouldn't be since it was just over a year old. Replaced it with an Antec Trio 550 while I sent my Corsair 620 away to be repped.

Cheers, you can close up the thread now.

btw keep up the good work guys, you're all doin a a bangup job here.

 

I had this problem on the wifes computer, the power supply was a 430 watt. I replaced it with a 550 watt with the huge fan, no more problems, ever....