Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Pc Freezes Randomly


  • Please log in to reply
14 replies to this topic

#1 TheGonK

TheGonK

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 21 December 2006 - 11:08 PM

Hi, My PC has been freezing randomly. When that happens, the system does not respond. There is no error message or blue screen of death. When it crashes, it does not automatically reboot. After pressing the restart button, my PC wont boot up, until I completely switched it off for some time. I scanned that PC with Avast Anti virus and it came back clean. Suspecting malware to be the problem, I posted a HijackThis log here http://www.bleepingcomputer.com/forums/top...tml#entry416831, and DaveM59 has checked my HijackThis Log. I'm using Windows XP Home SP2, and it is updated frequently.

Thanks for your help.

Hi TheGonK,

Welcome to Bleeping Computer. :thumbsup:

I have examined your HijackThis log and it shows no evidence of malware. There is a line

O4 - HKLM\..\Run: [KernelFaultCheck] %systemroot%\system32\dumprep 0 -k

this indicates that the system has crashed.

When the system freezes, does it show a blue screen with an error message? If so, the next time your computer crashes, please write down the entire message, including all numbers and letters. Post that information in a new topic on the Windows XP forum, not here. Please mention that I have checked your log for malware.

If the system stops responding and does not put up a blue screen, post that information to the same forum.

The only thing I can do is to press the restart button on the PC and my PC wont boot up for a random time.


Be sure to mention that after the system crashes, it will not reboot right away. This may be an important clue.

My guess is that you have a hardware failure, but there are folks at the XP forum who have a lot more experience than I do. They will be able to guide you in diagnosing the problem.

One suggestion -- if you do not have an up-to-date backup of your data files, make one now.

Good luck,

Dave


Edited by TheGonK, 22 December 2006 - 12:21 AM.


BC AdBot (Login to Remove)

 


#2 acklan

acklan

    Bleepin' cat's meow


  • Members
  • 8,529 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Baton Rouge, La.
  • Local time:03:08 AM

Posted 22 December 2006 - 10:24 AM

A heat problem or bad memory module can cause these problems also. Both are easy to determine.
Follow the instruction in the following link to determine if it is heat relate because of dirt or an broken fan. Cleaning the Interior of your PC
The memory test is just as easy. Not as fun if you like to tinker with the hardware, like you would cleaning the inside of the computer. It consists of a program, Mem86 memory tester, that either boots from a floppy or CD.
I would start with the memory test. I am not saying this isyour problem, but it is an easy way to rule out two possibilities.
"2007 & 2008 Windows Shell/User Award"

#3 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 22 December 2006 - 11:35 PM

I did the test and I left it for some time. The test passed 3 times

#4 fozzie

fozzie

    aut viam inveniam aut faciam


  • Members
  • 3,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Ossendrecht/The Netherlands
  • Local time:10:08 AM

Posted 23 December 2006 - 04:41 AM

Did you install any(P2P downloaded) software recently or connected any hardware?

#5 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 23 December 2006 - 05:15 AM

Did you install any(P2P downloaded) software recently or connected any hardware?

I did not install any P2P downloaded software. The only hardware I connected was my portable hard drive.

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:08 AM

Posted 24 December 2006 - 09:39 AM

Usually this sort of thing happens because of an error in WIndows - but notice I used the word usually! :thumbsup:

Try using this link to see if you can find any messages about the freezes: http://www.bleepingcomputer.com/forums/top...tml#entry409491

Although it was written for BSOD's - the messages should be similar for this problem. In particular, keep your eye open for error messages relating to applications and hung applications (in addition to the BSOD stuff).
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 Herk

Herk

  • Members
  • 1,609 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:S.E. Idaho, USA
  • Local time:05:08 AM

Posted 24 December 2006 - 04:59 PM

After pressing the restart button, my PC wont boot up, until I completely switched it off for some time.


This statement leads me to believe you're having a power supply problem. It's the most common piece of hardware to fail. Depending on how it fails, it can destroy other hardware. It's possible that it's something else, but I'd certainly think seriously about replacing it.

Heat is also a common factor, and Acklan's advice is excellent.

#8 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 27 December 2006 - 06:36 AM

I took the computer apart and placed all the parts back and I cleaned up the PC with the help of an expert. However now I have a new problem: random shut downs. So far it occurred 3 times : twice within 15 seconds after windows xp starts and the third time while I was using Ubuntu live CD.

Edited by TheGonK, 27 December 2006 - 07:58 AM.


#9 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 04 January 2007 - 11:59 PM

Now my PC has a new motherboard after the random shutdowns. I disabled automatic restarts and now I am plagued with BSODs. I also noticed that the time is always displayed wrongly when I start up.


Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Thu Jan 4 10:46:23.265 2007 (GMT+8)
System Uptime: 0 days 0:07:51.828
Loading Kernel Symbols
........................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80585490, f86b5bf8, 0}

Probably caused by : ntoskrnl.exe ( nt!CmpDereferenceNameControlBlockWithLock+40 )

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

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: c0000005, The exception code that was not handled
Arg2: 80585490, The address that the exception occurred at
Arg3: f86b5bf8, 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:
nt!CmpDereferenceNameControlBlockWithLock+40
80585490 8b08 mov ecx,dword ptr [eax]

TRAP_FRAME: f86b5bf8 -- (.trap fffffffff86b5bf8)
ErrCode = 00000000
eax=00000004 ebx=00000000 ecx=00000000 edx=00000754 esi=e1222c1c edi=e1222c18
eip=80585490 esp=f86b5c6c ebp=f86b5c74 iopl=0 nv up ei pl nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
nt!CmpDereferenceNameControlBlockWithLock+0x40:
80585490 8b08 mov ecx,dword ptr [eax] ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 80585377 to 80585490

STACK_TEXT:
f86b5c74 80585377 e1222c18 00000405 e1235ef0 nt!CmpDereferenceNameControlBlockWithLock+0x40
f86b5c88 80655270 e1235ef0 e2f575c0 e21bddd0 nt!CmpCleanUpKcbCacheWithLock+0x22
f86b5c98 8065529e e21bddd0 f86b5cc0 80652eb3 nt!CmpCleanUpKCBCacheTable+0x2d
f86b5ca4 80652eb3 e21bddd0 00000000 00000020 nt!CmpSearchForOpenSubKeys+0xb
f86b5cc0 8064c815 e2f575c0 00000020 e21bddd0 nt!CmUnloadKey+0x32
f86b5d58 804df06b 0006faec 0006fb04 7c90eb94 nt!NtUnloadKey+0x18c
f86b5d58 7c90eb94 0006faec 0006fb04 7c90eb94 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006fb04 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpDereferenceNameControlBlockWithLock+40
80585490 8b08 mov ecx,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpDereferenceNameControlBlockWithLock+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

FAILURE_BUCKET_ID: 0x8E_nt!CmpDereferenceNameControlBlockWithLock+40

BUCKET_ID: 0x8E_nt!CmpDereferenceNameControlBlockWithLock+40

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

Edited by TheGonK, 05 January 2007 - 01:38 AM.


#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:08 AM

Posted 05 January 2007 - 09:38 AM

Wow, this is a tough one! Here's a link to the error message: http://www.osronline.com/ddkx/ddtools/bccodes_59k7.htm

Does it still shut down when using the Ubuntu Live CD?

My reading suggests that you try:
1) running chkdsk /f /r
2) running a memory test such as this free one: http://www.memtest86.com/
3) searching your Event Viewer for other errors that may point to this one.
4) running Driver Verifier (verifier.exe) to eliminate the drivers. Here's a link to an explanation: http://support.microsoft.com/kb/q244617/ I haven't had any luck making sense out the results of this program - I primarily look for unsigned drivers and update them first.

Good luck!
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 05 January 2007 - 10:42 PM

Wow, this is a tough one! Here's a link to the error message: http://www.osronline.com/ddkx/ddtools/bccodes_59k7.htm

Does it still shut down when using the Ubuntu Live CD?

My reading suggests that you try:
1) running chkdsk /f /r
2) running a memory test such as this free one: http://www.memtest86.com/
3) searching your Event Viewer for other errors that may point to this one.
4) running Driver Verifier (verifier.exe) to eliminate the drivers. Here's a link to an explanation: http://support.microsoft.com/kb/q244617/ I haven't had any luck making sense out the results of this program - I primarily look for unsigned drivers and update them first.

Good luck!


The shutdown problems were caused by the old motherboard, which has been replaced. I reformatted and installed windows xp.
First I ran chkdsk and it came back clean.
Next, I ran the memtest86 and there were 910 errors.
Failing Address
0000f36b5c0 - 243.6MB
0000f36b5c8 - 243.6MB
0000f36b5d0 - 243.6MB
0000f36b5d8 - 243.6MB
0000f36b5e8 - 243.6MB
0000f36b5f0 - 243.6MB
0000f36b5f8 - 243.6MB
0000f36b608 - 243.6MB
0000f36b610 - 243.6MB
0000f36b618 - 243.6MB

After reformatting, I got my first BSOD. So I ran the debugger.
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Jan 6 13:11:48.421 2007 (GMT+8)
System Uptime: 0 days 0:25:21.005
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf826fa2, a8b87514, 0}

Probably caused by : win32k.sys ( win32k!xxxUpdateWindow2+91 )

Followup: MachineOwner
---------
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: c0000005, The exception code that was not handled
Arg2: bf826fa2, The address that the exception occurred at
Arg3: a8b87514, 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!xxxUpdateWindow2+91
bf826fa2 3b7008 cmp esi,dword ptr [eax+8]

TRAP_FRAME: a8b87514 -- (.trap ffffffffa8b87514)
ErrCode = 00000000
eax=00000001 ebx=e3252608 ecx=00000b02 edx=0000000b esi=bc636c50 edi=00000000
eip=bf826fa2 esp=a8b87588 ebp=a8b8759c iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
win32k!xxxUpdateWindow2+0x91:
bf826fa2 3b7008 cmp esi,dword ptr [eax+8] ds:0023:00000009=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: SpybotSD.exe

LAST_CONTROL_TRANSFER: from bf826ed1 to bf826fa2

STACK_TEXT:
a8b8759c bf826ed1 bc636c50 00000001 bc636c50 win32k!xxxUpdateWindow2+0x91
a8b875bc bf8370dd bc636c50 00000001 a8b875e8 win32k!xxxInternalUpdateWindow+0x6f
a8b875cc bf9067d1 bc636c50 9f040f89 a8b87628 win32k!xxxUpdateWindow+0xf
a8b875e8 bf906a82 e12fe628 bc66bfd8 9f040f89 win32k!xxxUpdateThreadsWindows+0x3b
a8b87638 bf906f2c e12fe628 00000000 00000000 win32k!xxxDrawDragRect+0x258
a8b876cc bf867dba bc6773c0 00000003 00a7032a win32k!xxxMoveSize+0x345
a8b87704 bf80a3fb bc6773c0 0000f003 00a7032a win32k!xxxSysCommand+0x18c
a8b87764 bf80f57e bc6773c0 00000112 0000f003 win32k!xxxRealDefWindowProc+0xc97
a8b8777c bf823bc7 bc6773c0 00000112 0000f003 win32k!xxxWrapRealDefWindowProc+0x16
a8b87798 bf80f7c5 bc6773c0 00000112 0000f003 win32k!NtUserfnDWORD+0x27
a8b877d0 804de7ec 000202a0 00000112 0000f003 win32k!NtUserMessageCall+0xae
a8b877d0 7c90eb94 000202a0 00000112 0000f003 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f450 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxUpdateWindow2+91
bf826fa2 3b7008 cmp esi,dword ptr [eax+8]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

SYMBOL_NAME: win32k!xxxUpdateWindow2+91

FAILURE_BUCKET_ID: 0x8E_win32k!xxxUpdateWindow2+91

BUCKET_ID: 0x8E_win32k!xxxUpdateWindow2+91

Followup: MachineOwner
---------
kd> lmvm win32k
start end module name
bf800000 bf9c1180 win32k (pdb symbols) c:\symbols\win32k.pdb\D8788E4736B34ED5B8516DBB9D45E9942\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file: c:\symbols\win32k.sys\43446A581c1180\win32k.sys
Image path: win32k.sys
Image name: win32k.sys
Timestamp: Thu Oct 06 08:05:44 2005 (43446A58)
CheckSum: 001CB2E4
ImageSize: 001C1180
File version: 5.1.2600.2770
Product version: 5.1.2600.2770
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 041d.04b0
CompanyName: Microsoft Corporation
ProductName: Operativsystemet Microsoft® Windows®
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 5.1.2600.2770
FileVersion: 5.1.2600.2770 (xpsp_sp2_gdr.051005-1513)
FileDescription: Win32-drivrutin för flera användare
LegalCopyright: © Microsoft Corporation. Med ensamrätt.


Thanks for your reply.

Edited by TheGonK, 06 January 2007 - 12:38 AM.


#12 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 07 January 2007 - 05:32 AM

Now I keep getting this BSOD within minutes of starting up windows xp.
STOP: 0x0000008E (0xC0000005, 0x8059B424, 0xF855EBCC, 0x00000000). Is my RAM be the cause of the problems and the failed memtest?

#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:08 AM

Posted 07 January 2007 - 09:59 AM

Yes, 910 errors in the RAM is a lot - I've had spontaneous reboot problems in my son's computer with only 17 errors.

If you have multiple sticks of RAM, try testing them one at a time to find out which are bad. If all are bad, then try other slots to rule out the slots being bad.

Yesterday we did this on an older PC and found that it was actually one of the slots that was bad (rather than the RAM) - so it turned into a motherboard replacement rather than a RAM issue.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#14 TheGonK

TheGonK
  • Topic Starter

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Location:Singapore
  • Local time:05:08 PM

Posted 23 January 2007 - 09:06 PM

After many weeks I finally found the cause : a faulty motherboard. So it got replaced and so far I did not encounter any problems. Thanks for your help.

#15 thebeerdrain

thebeerdrain

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:09:08 AM

Posted 15 February 2010 - 12:51 PM

ACKLAN you are a god!! brilliant advise about interior cabinet cleaning. Took me about 45 mins and cost me about 6 gbp.
Thanks for the advise!!!!!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users