Computer freezing up

Status
Not open for further replies.
Hi All,

I've been having intermittent problems with my computer freezing up. I bought and installed 2 x 1gb PC3200 ram modules. And I bought a Logitech wireless keyboard and mouse combo.

Installed the combo and it all went sweet, no problems. Took the computer apart. I had 2 x 256mb ram sticks in pos#1 and #3. I added my 2 new sticks in pos#3 and #4. Plugged the usb wireless receiver back in and booted up. Seemed alright, put software CD in computer and it locked up.

I restarted and it froze in about 5 seconds. I reverted back to my standard keyboard and mouse and got back to the software installation which required the receiver plugged in which froze the computer again.

I restarted and removed the receiver but after a few minutes I got that blue screen memory_management error. So in the next reboot I removed the CD and it's been going good for at least 10 minutes.

Can someone give me some suggestions? Could the CD have caused the issues?

Also is there a specific way of installing ram? I noticed the 2 new ram modules were a little difficult to push down so the white clips locked. But all 4 definitely locked and both the system specs screen and the ram optimizer accurately register that I now have 2.5g ram.

Thanks for any suggestions.
 
Unlikely it's the CD itself, but maybe something that is loaded from the CD. Have you tried using other CDs to see fi the CD drive is the problem?
 
It froze again without the CD in the drive. I don't think anything was installed off the CD.

This time though there was no actual description on the blue screen. Instead it reference file win32k.sys. Any ideas?
 
I reread your description and the only change you made that's left is the new RAM. Try removing it and see if the freezing stops.
 
I want to leave the new ram modules as the absolute last option. I've taken out the 2 x 256mb modules and I generated the minidump for the original win32k.sys error. Can anyone glean any useful information from the following?


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: c0000005, The exception code that was not handled
Arg2: bf82686a, The address that the exception occurred at
Arg3: acf2bfec, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
win32k!DeleteHrgnClip+6
bf82686a 8b7508 mov esi,dword ptr [ebp+8]

TRAP_FRAME: acf2bfec -- (.trap 0xffffffffacf2bfec)
Unable to read trap frame at acf2bfec

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf803ec2 to bf82686a

STACK_TEXT:
acf2c064 bf803ec2 e70840c0 acf2c0f8 00f1ef88 win32k!DeleteHrgnClip+0x6
acf2c07c bf815e35 06010feb 00000001 00f1ef88 win32k!ReleaseCacheDC+0xe9
acf2c090 bf815ef3 bc7d0848 acf2c0b8 acf2c124 win32k!xxxEndPaint+0x12
acf2c114 804dd99f 0001007e 00f1ef48 00f1ef8c win32k!NtUserEndPaint+0x6b
acf2c114 7c90eb94 0001007e 00f1ef48 00f1ef8c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00f1ef8c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!DeleteHrgnClip+6
bf82686a 8b7508 mov esi,dword ptr [ebp+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!DeleteHrgnClip+6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0x8E_win32k!DeleteHrgnClip+6

BUCKET_ID: 0x8E_win32k!DeleteHrgnClip+6

Followup: MachineOwner



Thanks everyone
 
Time for the last option! Put the old RAM modules back in and take out the new ones! Let's see if the freezing stops! (I'll bet it will!)

You new RAM might be flacky. It's not uncommon.
 
I seem to have fixed it, hopefully. Everything is working smoothly including the wireless keyboard and mouse. I think one of the 2 unused slots that I first placed the new ram modules in were faulty.

I had left the sides off the PC for quite a long time and I'm guessing that dust has settled into the unused slots. Is that permanent damage or can it be fixed easily?
 
Status
Not open for further replies.
Back