• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I thought the problems were over...I was wrong.

L

lariz

Member
I recently made a post here after having to deal with a top of app crashes and BSOD's. I figured out that it was a simple video driver issue that could be fixed with a reinstall.
I bought a new 8800gt a week ago and installed it with the newest drivers. Everything went well from there. I played crysis and HL2 for about 8 hours with no lag, no BSOD, and no app crash. I thought my computer was finally stable....until I shut it down and went to bed.
I get up in the morning and go to class for a few hours. Afterwords I boot up my computer and get an hour of crysis in before work. In that hour I got 13 crashes to desktop and a BSOD.

What happened in this period of time?


Since then I've gotten random BSOD's and the always fun crashes to desktop from TF2, HL2 and WoW. After a week of it I decided to finally get to the bottom of this issue.
I will post my BSOD logs, my error logs, my NVIDIA graphics monitor and many other things.

WARNING: THIS POST IS LONG!


Let's get down to business. I'll start with my BSOD logs.

01/24/08
--------
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Thu Jan 24 14:06:01.596 2008 (GMT-5)
System Uptime: 0 days 6:09:33.453
Loading Kernel Symbols
...................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8b0edfcf, 8c90bac0, 8c90b7bc}



Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+d )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8b0edfcf, The address that the exception occurred at
Arg3: 8c90bac0, Exception Record Address
Arg4: 8c90b7bc, Context Record Address

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




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

FAULTING_IP:
dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+d
8b0edfcf c70704000000 mov dword ptr [edi],4

EXCEPTION_RECORD: 8c90bac0 -- (.exr 0xffffffff8c90bac0)
ExceptionAddress: 8b0edfcf (dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+0x0000000d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT: 8c90b7bc -- (.cxr 0xffffffff8c90b7bc)
eax=9c68981c ebx=c01e0100 ecx=87a1c5b0 edx=9d88511c esi=8e556908 edi=00000000
eip=8b0edfcf esp=8c90bb88 ebp=8c90bb9c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+0xd:
8b0edfcf c70704000000 mov dword ptr [edi],4 ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

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

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
00000000

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8b0ee1c7 to 8b0edfcf

STACK_TEXT:
8c90bb9c 8b0ee1c7 00000000 00000000 8e556908 dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+0xd
8c90bbb8 8b153cd0 9c689708 00000000 87a70838 dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0x1b
8c90bbd4 8b15132f 9c689708 00000000 87a70000 dxgkrnl!VIDMM_SEGMENT::ReAllocateOldResource+0xaf
8c90bbec 8b1517df 87a70838 87a70000 8b0e528f dxgkrnl!VIDMM_GLOBAL::CancelAllReclaimedAllocationsInList+0x23
8c90bbf8 8b0e528f 87a37a80 878aef10 84f57eb8 dxgkrnl!VIDMM_GLOBAL::CancelAllReclaimedAllocations+0x1f
8c90bc40 8b0e5f3f a058e5c8 00000000 84f57eb8 dxgkrnl!VIDMM_GLOBAL:😛repareDmaBuffer+0x78b
8c90bd48 8b0e45e7 878aef10 87f3bde0 8c90bd6c dxgkrnl!VidSchiSubmitRenderCommand+0x120
8c90bd58 8b0ed0a8 878aef10 00000000 87a37a80 dxgkrnl!VidSchiSubmitQueueCommand+0x61
8c90bd6c 8b12cce2 87a37a80 87a33d78 8c90bdc0 dxgkrnl!VidSchiRun_PriorityTable+0x24
8c90bd7c 81e254e0 87a37a80 8c900680 00000000 dxgkrnl!VidSchiWorkerThread+0x61
8c90bdc0 81c9159e 8b12cc81 87a37a80 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+d
8b0edfcf c70704000000 mov dword ptr [edi],4

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46899fd6

STACK_COMMAND: .cxr 0xffffffff8c90b7bc ; kb

FAILURE_BUCKET_ID: 0x7E_dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+d

BUCKET_ID: 0x7E_dxgkrnl!VIDMM_LINEAR_POOL::MarkBlockForEviction+d

Followup: MachineOwner


=============================
=============================
=============================

01/27/08
--------


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


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

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sun Jan 27 12:52:17.240 2008 (GMT-5)
System Uptime: 0 days 3:13:44.112
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 8b2c849c, 82414e68, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys


Probably caused by : dxgkrnl.sys ( dxgkrnl!VidSchiUpdateFlipDeviceStatus+0 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 8b2c849c, The address that the exception occurred at
Arg3: 82414e68, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
dxgkrnl!VidSchiUpdateFlipDeviceStatus+0
8b2c849c 8bff mov edi,edi

TRAP_FRAME: 82414e68 -- (.trap 0xffffffff82414e68)
ErrCode = 00000000
eax=fffffffe ebx=8525b5b8 ecx=00000000 edx=00000000 esi=8866b008 edi=00000000
eip=8b2c849c esp=82414edc ebp=82414f18 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VidSchiUpdateFlipDeviceStatus:
8b2c849c 8bff mov edi,edi
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 8b2c7833 to 8b2c849c

FAILED_INSTRUCTION_ADDRESS:
dxgkrnl!VidSchiUpdateFlipDeviceStatus+0
8b2c849c 8bff mov edi,edi

STACK_TEXT:
82414ed8 8b2c7833 8525b5b8 8866be18 00000000 dxgkrnl!VidSchiUpdateFlipDeviceStatus
82414f18 8b2c459c 8866be18 8866c008 88668a80 dxgkrnl!VidSchiProcessDpcVSyncCookie+0x1ca
82414f30 8b2c4652 8866c008 00000001 87126000 dxgkrnl!VidSchDdiNotifyDpcWorker+0x57
82414f54 8b851c91 8715b608 8703d8c8 8715b6c0 dxgkrnl!VidSchDdiNotifyDpc+0x6e
WARNING: Stack unwind information not available. Following frames may be wrong.
82414f88 81ca93ae 8715b9d8 8715b608 00000000 nvlddmkm+0x2dc91
82414ff4 81c90ecd 9789ed10 ffffffff ffffffff nt!KiRetireDpcList+0x147
82414ff8 9789ed10 ffffffff ffffffff ffffffff nt!KiDispatchInterrupt+0x3d
82414ffc ffffffff ffffffff ffffffff ffffffff 0x9789ed10
82415000 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415004 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415008 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241500c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415010 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415014 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415018 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241501c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415020 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415024 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415028 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241502c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415030 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415034 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415038 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241503c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415040 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415044 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415048 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241504c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415050 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415054 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415058 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241505c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415060 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415064 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415068 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241506c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415070 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415074 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415078 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241507c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415080 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415084 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415088 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241508c ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415090 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415094 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415098 ffffffff ffffffff ffffffff ffffffff 0xffffffff
8241509c ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150a0 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150a4 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150a8 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150ac ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150b0 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150b4 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150b8 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150bc ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150c0 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150c4 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150c8 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150cc ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150d0 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150d4 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150d8 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150dc ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150e0 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150e4 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150e8 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150ec ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150f0 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150f4 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150f8 ffffffff ffffffff ffffffff ffffffff 0xffffffff
824150fc ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415100 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415104 ffffffff ffffffff ffffffff ffffffff 0xffffffff
82415108 ffffffff ffffffff ffffffff ffffffff 0xffffffff


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!VidSchiUpdateFlipDeviceStatus+0
8b2c849c 8bff mov edi,edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgkrnl!VidSchiUpdateFlipDeviceStatus+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46899fd6

FAILURE_BUCKET_ID: 0x8E_BAD_IP_dxgkrnl!VidSchiUpdateFlipDeviceStatus+0

BUCKET_ID: 0x8E_BAD_IP_dxgkrnl!VidSchiUpdateFlipDeviceStatus+0

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

==========================
==========================
==========================

01/28/08
--------



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


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

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Jan 28 11:54:22.288 2008 (GMT-5)
System Uptime: 0 days 3:02:02.145
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {64, 5, 0, 8aaf4fbe}



Probably caused by : USBPORT.SYS ( USBPORT!MPf_InterruptService+e )

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

0: 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: 00000064, memory referenced
Arg2: 00000005, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8aaf4fbe, address which referenced memory

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




READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
00000064

CURRENT_IRQL: 5

FAULTING_IP:
USBPORT!MPf_InterruptService+e
8aaf4fbe 8b5264 mov edx,dword ptr [edx+64h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Wow.exe

TRAP_FRAME: 94397ca0 -- (.trap 0xffffffff94397ca0)
ErrCode = 00000000
eax=4f444648 ebx=85618200 ecx=86fa90e0 edx=00000000 esi=86fa90e0 edi=8716ec80
eip=8aaf4fbe esp=94397d14 ebp=94397d14 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
USBPORT!MPf_InterruptService+0xe:
8aaf4fbe 8b5264 mov edx,dword ptr [edx+64h] ds:0023:00000064=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8aaf4fbe to 81c8fd84

STACK_TEXT:
94397ca0 8aaf4fbe badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
94397d14 8aaf5e53 86fa90e0 8709aaf0 85618284 USBPORT!MPf_InterruptService+0xe
94397d28 81c90980 8716ec80 86fa9028 94397d64 USBPORT!USBPORT_InterruptService+0x38
94397d54 81c908f9 00000000 00000063 0012fb60 nt!KiChainedDispatch2ndLvl+0x44
94397d54 005bf833 00000000 00000063 0012fb60 nt!KiChainedDispatch+0x29
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fb60 00000000 00000000 00000000 00000000 0x5bf833


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!MPf_InterruptService+e
8aaf4fbe 8b5264 mov edx,dword ptr [edx+64h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: USBPORT!MPf_InterruptService+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b26d

FAILURE_BUCKET_ID: 0xD1_USBPORT!MPf_InterruptService+e

BUCKET_ID: 0xD1_USBPORT!MPf_InterruptService+e

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

==================
END OF BSOD LOGS
==================


I got the last log about 30 minutes ago while playing WoW. I had my iPod usb cable inserted into the side of my computer(only the cable, the ipod wasn't plugged in). I notice that I get this BSOD almost every time the cable is plugged in.



Next I'll list some error logs from event viewer:


In the last hour there have been 20 errors.
12 ACPI System errors which read:

-IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 6, function 0. Please contact your system vendor for technical assistance.
-IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 5, function 0. Please contact your system vendor for technical assistance.
-IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 3, function 0. Please contact your system vendor for technical assistance.

You get the idea...

1 EventSystem application error:

-The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\vistartm\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.


1 EventLog system error:

-The previous system shutdown at 11:53:38 AM on 1/28/2008 was unexpected.

1 Service control manager provider error:

-The following boot-start or system-start driver(s) failed to load:
spldr
Wanarpv6

And 5 DistributedCOM errors:

-DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}
-DCOM got error "1068" attempting to start the service fdPHost with arguments "" in order to run the server:
{145B4335-FE2A-4927-A040-7C35AD3180EF}
-DCOM got error "1084" attempting to start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}

=========
END OF EVENT LOGS
=========



Here's my NVIDIA Monitor:

http://i11.photobucket.com/alb...97/Skizi/nvidiamon.jpg



-My card never gets anywhere near 60C, even with Crysis on max resolution and very high settings.
-I've run memtest, 15 passes, no errors. I've also ran tons of other memory reading software.



Other problems:

-Everytime windows starts up I get a "Windows has blocked this program" window on the bottom right of my screen. it's blocking the app Steam.exe for whatever reason. I have it going through windows firewall and it's not even suppose to be loading on startup.

-I have the released NVIDIA drivers, 169.25. I've tried the beta drivers, but they seem to offer the same results.

-I have the nForce, 15.08 drivers. I've tried un-installing them, re-installing them and running without them.

-I've recently installed new realtek sound drivers for my onboard sound. I downloaded them from ASUS.com.


My System:

Intel core 2 duo E6600 @ 3.0GHz
Corsair 2GB RAM
NVIDIA 8800GT 512MB
ASUS P5N-E-SLI board
Windows vista ultimate 32


I appreciate any help that anyone may offer.
Thank you in advanced.




 
it appears that a possible DirectX issue, maybe a game installed a file when a patch was released that is not compatible or truncated.
 
It sounds like your Windows is completely messed up, or at least some software is causing it that.
I am curious why there is ACPI errors.
Is ACPI enabled in BIOS?

If I am you I would back up my files and reinstall the whole Windows
That perhaps saves time messing about what's wrong.

Is the Steam.exe from Valve? Have you scanned for virus and spyware
 
Originally posted by: AnnihilatorX
It sounds like your Windows is completely messed up, or at least some software is causing it that.
I am curious why there is ACPI errors.
Is ACPI enabled in BIOS?

If I am you I would back up my files and reinstall the whole Windows
That perhaps saves time messing about what's wrong.

Is the Steam.exe from Valve? Have you scanned for virus and spyware
Click to expand...

I've re-installed vista about 4 times now, I've even bought a new HD and clean installed it on that. Every time i re-install it will work fine for a few weeks and then have pretty much the same problems, and sometimes new ones would form.

Yes, it's from valve. I've scanned most of my apps for viruses, never found any.



[EDIT] Also, the ACPI suspend type is set to S1&S3 in bios.
 
All your system hardware should be Vista compatible.

Is your BIOS up to date?
The only other thing I can think of is a defective/low quality/underpowered Power Supply affecting the stability of the system hence ACPI errors.
 
Originally posted by: AnnihilatorX
All your system hardware should be Vista compatible.

Is your BIOS up to date?
The only other thing I can think of is a defective/low quality/underpowered Power Supply affecting the stability of the system hence ACPI errors.
Click to expand...

My bios version is : BIOS revision 0202, 11/22/06


How would I check my power supply?
 
lariz, like I said a game or program updated a directx file, best thing I can tell you is to try a fresh (wipe all partitions) and reload and use the mobo cd to install the drivers before doing any windows updates, and game installs, and do each, one at a time.
 
Originally posted by: robisbell
lariz, like I said a game or program updated a directx file, best thing I can tell you is to try a fresh (wipe all partitions) and reload and use the mobo cd to install the drivers before doing any windows updates, and game installs, and do each, one at a time.
Click to expand...

You're suggesting a complete computer restoration? is there a simpler way? And how can I make sure this doesn't happen again?

And does this also explain the ACPI errors?
 
what cards are installed in this machine? yes I am suggesting a fresh installation. there's no shortcutting unless you want something else to go wrong.
the ACPI errors, I must have breezed over them I was concentrating on the initial error message. is this using a valid MS certified disk when you installed Windows?
 
ah, that's one reason right there, this Vista does not have the drivers for your mobo at default.
why are you using a NIC when most mobo's have them builtin.
 
Very long story about the network card. I'll spare you the boring tale and summarize it for you: I moved to a new location, internet didn't work, had to re-install vista and buy a card in order to get it working. Should I remove it and use my onboard ethernet adapter once I re install vista?
 
The PSU seems fine.


If you have HDD space to spare, download a trail copy of Acronis True Image, take an image of your C drive. In this case should you want to go back you can. But it requires you to have another HDD or partition that has quite some space free.
Next, download all the Vista capable updated MB driver from Asus and save it to another HDD/Partion
Then, format C:, Unplug all add-in cards except graphics, and reinstall vista. Use the downloaded vista drivers

Make a system restore points after bare minimum PC is running without problem.
Add-in other hardware/software one by one. Do not use that netgear card if your motherboard have built in Ethernet. It's redundant and potential driver instability.

From the few months I've used Vista, I know how drivers is a pain to work with in Vista.
I feel your pain lol
 
I've just re-installed vista. I'm still getting ACPI errors, but not as much. Vista is updating now, afterwords I'll install the rest of the drivers and see what happens from there.


[EDIT] Ok, I think I've just solved my problem. It appears that "ATK0110 ACPI UTILITY " is the root of this whole problem. I've looked on MS forums and people have been having the same issues as me, yet they don't know what to do. Does anyone here know what this is and/or how to fix it?
 
"ATK0110 ACPI UTILITY" that's part of the mobo drivers, good reason why you're having problems because you're not setting the system up properly.
 
Originally posted by: robisbell
no, no, no.

1. install vista
2. install all the mobo drivers
3. install video card drivers
4. then update windows
Click to expand...

It's not working that way. As soon as vista boots for the first time it automatically installs drivers for different types of devices. Then when I run the mobo CD drivers I can't access the internet after.

The CD comes wiith 3 drivers:
-Nvidia chipset driver
-Realtek audio driver
-JMicron JMB36X RAID controller driver

Which of these is the ATK0110 ACPI UTILITY ?

It kind of works like this:
1. Vista comes up for the first time
2. I launch my mobo's driver CD
3. Install drivers
4. Internet doesn't work...can't install updates/other drivers


I've got running now, though I'm still getting ACPI errors. When running windows update it failed to install the ATK0110 ACPI UTILITY. Probably because it couldn't find it? Can I just download this from a site and update windows now...or should I re-install again?
 
you can stop it, that's the problem, you're letting it install incompatible drivers since it's a OEM version.
to install the drivers off of the CD, you do not need the internet.
 
I just re-installed again. I have updates turned off and so far my version of vista is clean. now at this time if I were to download the Nvidia chipset driver from my board's CD I would lose my ethernet adapter driver for some reason and not be able to access the internet...this usually results in me having to re-install again since there's nothing i can do without it.

Right now I have no ACPI errors in event viewer. i want to know exactly what drivers I need to install, so that when I run the update I don't get a "failed" message when installing ATK0110 ACPI UTILITY. I obviously can't run the nvidia chipset driver, so that leaves me with the Realtek audio driver and JMicron JMB36X RAID controller driver ...thats all that came on this CD. I think the chipset driver may be corrupt or incompatible, I'm not going to try to install it again.
 
That's why I asked you to download updated drivers from Asus, save it to a memory stick so you don't need access to the internet.
If it's a Vista compatibility problem, there should be updated drivers online.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top