PC had been running about 41 minutes, the last 10 minutes in i had opened league of legends launcher and started watching a streaming video on palemoon before the bluescreen.
· OS - Windows 7 · 64 bit. · What was original installed OS on system? windows xp. · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer) - full retail version · Age of system - psu 5 years old. rest of system 8-18 months old. · Age of OS installation - have you re-installed the OS? 2 years old.
· CPU - AMD Phenom(tm) IIx4 B55 Processor 3.82 GHz · Video Card - Radeon HD 6770 1GB · MotherBoard - GA-MA770T-UD3 · Power Supply - Arctic Power 600W PSU · System Manufacturer · Exact model number - homebuilt
<Disclosure: I know the owner and machine in question here.>
I don't recall trying to debug an 0x18 before, so I really could do with someone checking this over. The !object fffffa800462bc18 command - which might be the most useful with this type of bugcheck - was a dead end for me, so I'll throw in a couple of guesses based on the oldest 3rd party driver and the PC usage at the time of the crash.
I'm leaning towards an old wireless driver, download the latest one directly from here. Don't install it yet!
Download using the button below to a convenient place such as your desktop and unzip it.
NOTE: After downloading, DO NOT RUN THE FILE YET. Please proceed to Step 2.
To properly install adapter software, please remove drivers that were previously installed.
To uninstall, go to Start > Programs > NETGEAR WNA3100 adapter > Uninstall NETGEAR WNA3100 adapter .
Unplug the WNA3100 adapter from your computer.
Run the file you just downloaded and follow the on-screen install instructions.
That should result in the 2007 scmndisp.sys driver updating to June 2011.
I also wonder whether the recently updated Flash plugin (yes, it's now NPSWF64_11_3_300_262.dll) was part of this, revert the Flash plugin version to 188.8.131.52 by carefully following the instructions here: http://forums.adobe.com/message/4487439#4487439
Don't forget to check the box to warn about an update - don't allow it to update until we know there's a reasonably stable version.
Satrow, you're doing it right. First thing I would've done would also check the object details. As you can figure from the lengthy description of this bugcheck, the 4th parameter in the bugcheck is evidently showing that the reference count for the object dropped below zero (hence it underflowed and rolled backwards to ffffffffffffffff).
The only way to debug this would be to either sic Driver Verifier on it, or to hand us a kernel dump of the crash.
BTW, 5 year old PSU? May wanna change that, regardless if it's involved with this or not.