TechSpot

Computer Randomly Crashes/Restarts

By cougarelite
Nov 28, 2007
Topic Status:
Not open for further replies.
  1. Hey,

    I just joined the forum, and I'm in need of some help. I got this computer from my brother a couple weeks ago, and I tried starting it up. Everything started, but every now and then when I'd open a program or something, the screen would change to some strange image. This image changes from time to time, it could be just green with a square in the middle, a checkerboard pattern or just abstract lines. It's really weird. Anyways it would flash to that and the only way to get out of it is to restart. Sometimes it goes straight to this at the Windows XP Welcome screen. Usually though it's when I'm in a game and it tries to load new graphics. I tried reformatting my hard drive and reinstalling XP but no improvement. I've tried updating my video card with the latest drivers and it hasn't helped a bit. These are my specs:

    AMD Athlon 64 3400+
    1 GB RAM
    GeForce 5700 LE 256 MB
    Asus K8V-SE Deluxe motherboard

    Here are some errors I found in the event viewer (not sure if they come into play here):

    Error code 1000008e, parameter1 c0000005, parameter2 bf06c020, parameter3 f6eb7b3c, parameter4 00000000.
    Category (102) Event ID: 1003

    Error code 1000008e, parameter1 c0000005, parameter2 bf06c020, parameter3 b8de3b3c, parameter4 00000000.
    Category (102) Event ID: 1003

    Error code 100000ea, parameter1 862aada8, parameter2 862db3b8, parameter3 f7a3fcb4, parameter4 00000001.
    Category (102) Event ID: 1003

    Error code 1000008e, parameter1 c0000005, parameter2 bf06d867, parameter3 ee16fb40, parameter4 00000000.
    Category (102) Event ID: 1003

    Error code 1000008e, parameter1 c0000005, parameter2 bf06d867, parameter3 f4eb1b40, parameter4 00000000.
    Category (102) Event ID: 1003

    Oh and none of those errors above took place at the same time a crash did, so I'm not sure if they are related. I really hope someone can help me solve this. Any suggestions are welcome.

    What should I do?

    Thanks
  2. pioneerx01

    pioneerx01 TS Maniac Posts: 345

    oh I have seen this title so many times...but yours is a unique on I must say.
    First think I would do is update the drivers, but you have already done that.

    Try and see if any other drivers are not installed by going to control panel and add/remove hardware. Follow through the screens and those in yellow triangle need installing. (this probably will not do anything, but try it anyway)

    Since you have already reinstalled XP again (last thing I would do) we can pretty much rule out OS problem, unless something that is installed on the PC is messing the thing up. Could it be the monitor?

    Right click on my Computer and go to manage then event viewer followed by system and 2xclick on the most recent warnings or errors. There you will find a link to Microsoft's website and see what they say.

    Lastly post your minidumps (if you have any) located in C/windows/minidump.
    Someone else is going to have to look through them, because I cant read them or whatever error codes you have written up there.

    you stated that you have 1gb ram. one stick or two? if two are they the same?

    keep us posted....
  3. venu.k

    venu.k TS Rookie

    Hai, Just remove Ur RaM and cleanse it with smooth cloth then insert properly,Some time RAm may get in dust that's why it's autometically restart the system.,
  4. random restarts may be due to corrupted RAM or a corrupt hard drive. since yours restarts, i'd say it's the RAM you should look at first. the way to test the RAM is to download Memtest, and see if your RAM gets any errors. if the answer is yes, it gets errors....you know where your problem is. and the only way to fix that is to buy a new RAM card or two.

    the same pretty much goes with the hard drive. if you can, try to plug it into a working computer. and if you get problems, then you know its the hard drive. or see if your hard drive manufacturer offers a diagnostic that will tell you if it is corrupted or not.

    and if it is, the answer there is the same as for the ram. only way to fix it is to get a new one. 50 bucks on newegg.com for a brand new western digital 160gig hard drive.

    check them out first.

    the only other thing i could see as a possible reason is a power failure. but your parts aren't very taxing. so i doubt it's that.
  5. aspirulito

    aspirulito TS Rookie Posts: 51

    it could also be your mobo.. inspect it for bad capacitors... u will know a capacitor is bad if it has rust or if the top is popped up.
  6. cougarelite

    cougarelite TS Rookie Topic Starter

    Thanks a lot for the replies! I'm going to try all these suggestions out. When I get home, I'll test with MemTest, try cleaning the ram and I'll post any minidumps if I have any. Oh and I have two sticks of 512 MB RAM and they are the same. I'll post back when I have any news.
  7. cougarelite

    cougarelite TS Rookie Topic Starter

    We ll I tried out MemTest using a bootable CD, and it didn't go how I expected it to. Most people say they let it run for hours. Mine just showed the MemTest screen for about 30 seconds, then the top half disappeared and left just the bottom. It was just the bottom of my screen in blue. Here's some information I recorded:

    Bits in Error Mask: 0001fffc
    Bits in Error - Total 15 Min 0 Max 14 Avg 87
    Max Contiguous Errors: 2

    Test
    0..... 56
    1..... 24
    2..... 40
    3..... 56
    4..... 72
    5..... 88
    6..... 104
    7..... 120
    8..... 136
    9..... 152
    10.... 168

    That's all I wrote. I'll take a picture of the screen if it helps. I don't understand how it tested everything in under a minute. Did I do something wrong, or all those all real errors? Please help!

    I also have attached 4 minidumps I found in the folder. There are more but the file size is too big.
  8. cpc2004

    cpc2004 TS Rookie Posts: 2,044

    From the minidump debug report, the culprit maybe nVidia Display card driver. If you search google, someone encounter bugcheck code 8E at nVidia display card driver with your version. The timestamp of your nVidia display card driver is 472528F5. Install older or more current version may resolve the blue screen problem.

    nv4_disp.dll Mon Oct 29 08:27:33 2007 (472528F5)

    Summary of your debug report
    Mini112507-04.dmp BugCheck 100000EA, {862aada8, 862db3b8, f7a3fcb4, 1}
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
    Probably caused by : ntkrnlpa.exe ( nt!KiDispatchInterrupt+7f )

    Mini112607-01.dmp BugCheck 1000008E, {c0000005, bf06c020, b8de3b3c, 0}
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    Probably caused by : nv4_disp.dll ( nv4_disp+5a020 )

    Mini112607-02.dmp BugCheck 1000008E, {c0000005, bf06c020, f6eb7b3c, 0}
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    Probably caused by : nv4_disp.dll ( nv4_disp+5a020 )

    Mini112807-01.dmp BugCheck 1000008E, {c0000005, bf06c020, b938fb3c, 0}
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    Probably caused by : nv4_disp.dll ( nv4_disp+5a020 )
  9. mms

    mms TS Rookie

    Hi CPC2004,


    I have been struggling with this BSOD problem for long. I work from home and am not able to part with this computer to send it to "emachines" for a diagnosis.

    I have tried all the things possible, like reformatting the system, loading the drivers etc. I tried the speedfan utility. Itshows normal results. Yesterday, I changed thepower supply too. I did not have reboots from yesterday night to today afternoon. I thought the power supply fixed the issue. But, no... The problem persists. It only reduced the frequency
    of the reboots.

    Frankly, I am tired, sad and exhausted. I am not good at reading with debugging thing. But, I am pasting what it showed. Can you please go through it and point out the error?

    It will a great christmas gift for me if somebody could solve my problem.

    Thanks.





    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini122207-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_qfe.070227-2300
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sat Dec 22 12:20:18.921 2007 (GMT-6)
    System Uptime: 0 days 2:26:40.610
    Loading Kernel Symbols
    ...............................................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, bf80114f, f6fc46b8, 0}



    Probably caused by : win32k.sys ( win32k!ThreadUnlock1+14 )

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

    0: 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: bf80114f, The address that the exception occurred at
    Arg3: f6fc46b8, 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!ThreadUnlock1+14
    bf80114f ff4804 dec dword ptr [eax+4]

    TRAP_FRAME: f6fc46b8 -- (.trap 0xfffffffff6fc46b8)
    ErrCode = 00000002
    eax=4397bf28 ebx=bc6917a8 ecx=f6fc4758 edx=f6fc4c70 esi=e26064f8 edi=bc68bf28
    eip=bf80114f esp=f6fc472c ebp=f6fc4790 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    win32k!ThreadUnlock1+0x14:
    bf80114f ff4804 dec dword ptr [eax+4] ds:0023:4397bf2c=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: UdaterUI.exe

    LAST_CONTROL_TRANSFER: from bf83f323 to bf80114f

    STACK_TEXT:
    f6fc4728 bf83f323 0012f6e4 f6fc47e8 bf8f64fd win32k!ThreadUnlock1+0x14
    f6fc4790 bf8f648b 0368bf28 00000000 00000001 win32k!xxxCallHook2+0x2cc
    f6fc47ac bf8e32dc 00000000 00000001 00000002 win32k!xxxCallNextHookEx+0x2d
    f6fc4800 bf8f6408 00000003 00000000 00000001 win32k!NtUserfnHkINLPMSG+0x3a
    f6fc481c 805409ac 00000000 00000001 0012f6c8 win32k!NtUserCallNextHookEx+0xa5
    f6fc481c 7c90eb94 00000000 00000001 0012f6c8 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f5e8 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!ThreadUnlock1+14
    bf80114f ff4804 dec dword ptr [eax+4]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: win32k!ThreadUnlock1+14

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

    FAILURE_BUCKET_ID: 0x8E_win32k!ThreadUnlock1+14

    BUCKET_ID: 0x8E_win32k!ThreadUnlock1+14

    Followup: MachineOwner
    ---------
  10. cpc2004

    cpc2004 TS Rookie Posts: 2,044

    Hi MMS.

    Open a new thread for a new problem. Attach 5 to 6 minidumps at your new threads.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.