BSOD occuring randomly don't know the cause

carwiz said:

Bugcheck 18 is usually caused by a poorly written or otherwise faulty driver. In the last last case, it may be your ATI Radeon drivers. Always download drivers from the manufacturer's site. Don't rely on third-party support for critical drivers. Also, make sure you have the latest version of Firefox and run full malware scan.

You didn't include valuable additional information in your zip file so further diagnostics may not be offered until the complete file set is provided. Good luck.


BugCheck 18, {854d8418, 856d8768, 1, 1}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+176b2

Thank you. I've rolled back my driver and set the computer to make a complete memory dump.
Also an error from Windows Script Host appeared on startup- error 800C0005 about a msxml3.dll file. I'll post again if I still BSOD.

You need to update all your ATI drivers including Catalyst Control Center or remove it. The ATI display drivers are still the cause of the Bugcheck 18. This is a driver fault. The drivers are either not compatible with your hardware or not compatible with linking software.

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 85cbf418, Object type of the object whose reference count is being lowered
Arg2: 873cd080, Object whose reference count is being lowered
Arg3: 00000001, Reserved
Arg4: 00000001, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object’s reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

FOLLOWUP_IP:
atikmdag+176b2
944296b2 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: atikmdag+176b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50d224e9
FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_atikmdag+176b2
BUCKET_ID: 0x18_CORRUPT_REF_COUNT_atikmdag+176b2
Followup: MachineOwner
---------
3: kd> lmvm atikmdag
start end module name
94412000 94d95000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Wed Dec 19 14:34:49 2012 (50D224E9)
CheckSum: 009386DC
ImageSize: 00983000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
3: kd> !object 873cd080
GetUlongFromAddress: unable to read from 83da5824
Could not read ObjectType address