Software

Ask something
Question Locked

Vista locks up randomly when clicking on objects

0 helpful
9 replies

by jackaluk

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I posted a while back with the error code 4609 appearing, and the pc restarting, the error was resolved, and the pc has been working fine for a couple of weeks, now however, the problem has started again. Now though, the computer will randomly lock up, with nothing happening on screen, the mouse doesnt move, nothing. All i have to identify the problem is the error code 4609, and the message:
"The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\rtm\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.".
As I say, the problem I had before was resolved by reinstalling mouse and keyboard drivers, however, i'm not sure its driver related this time, as the drivers have been fine for the last couple of weeks.
Any help would be appreciated!
Cheers

9 replies

by thumbsup2

Sounds like a bad controler, or possibly heat related. Is the waranty still good? It needs to go in for repair.

by jackaluk

hi, the computer i'm using is completely custom built, the heat is fine, at the moment the case's temp is 25C, which isnt too bad.

by rob miners

replacing your Keyboard and Mouse with something that doesn't require Drivers to be installed and will be automatically detected..

< You didn't reinstall the drivers I hope. >

by jackaluk

Right, i've come to the conclusion it isn't the keyboard, as I uninstalled the drivers for it, plugged in a completely different keyboard, which auto detected, but the same problem still arises. I haven't got a spare mouse to hand, so i'll try that later.
Cheers

by rob miners

My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.

This will Blue Screen the PC. Take note of Stop 0X000000 error message and post it.

Or if you are feeling adventurous

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

To download and install the Windows debugging tools, visit the following Microsoft Web site:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
FAULTING_THREAD: 864f6a98

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

STACK_TEXT:
f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

FOLLOWUP_IP:
sgiul50!DrvBitBlt+585
bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: sgiul50!DrvBitBlt+585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

by nepenthe0

In the Run Menu, type

chkdsk.exe C: /F

and hit Enter. The program will look for sector errors and will [i]fix[/i] them at the next boot. There is no risk to your data, but it goes without saying that it's always a good idea to back up important data.

Please post back in this thread for further assistance, or to report what actually resolved the glitch.

Rick/Portland, OR

by jackaluk

Hi,
I've tried this a few times already, unfortunately it doesn't help.
Cheers though

by jackaluk

I've just found that the pc doesn't just lock up, it has also started either restarting, or locking up, it seems to be completely random, with only the same error appearing in the event viewer.

This discussion is closed to new replies.