TechSpot

Computer randomly restarts

By scr1b3
Jun 21, 2011
Post New Reply
  1. This all starting three days ago when I was just surfing the web and had a Word document open. The computer randomly restarted itself and has continue at least three times a day since then. I've already scanned computer for viruses and trojans using Symantec and Malwarebytes. Can someone please help me resolved this issue?

    Crash Dump:



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


    Loading Dump File [C:\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Missing image name, possible paged-out or corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_0000000c
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000c
    Debugger can not determine kernel base address
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.101209-1647
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Jun 20 15:22:52.819 2011 (UTC - 7:00)
    System Uptime: 0 days 1:11:03.703
    Missing image name, possible paged-out or corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_0000000c
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000c
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    Missing image name, possible paged-out or corrupt data.
    .Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - NTSTATUS 0xC0000147

    Loading unloaded module list
    ...Image path too long, possible corrupt data.
    Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .....Image path too long, possible corrupt data.
    Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Image path too long, possible corrupt data.
    ...
    WARNING: .reload failed, module list may be incomplete
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {a92bdffc, ff, 0, 80545b7f}

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    *** WARNING: Unable to verify timestamp for Unknown_Module_0000000c
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000c
    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 1
    Missing image name, possible paged-out or corrupt data.
    Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - NTSTATUS 0xC0000147
    WARNING: .reload failed, module list may be incomplete
    Missing image name, possible paged-out or corrupt data.
    Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - NTSTATUS 0xC0000147
    WARNING: .reload failed, module list may be incomplete
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
     
  2. scr1b3

    scr1b3 TS Rookie Topic Starter Posts: 22

    I just uploaded the crash dump file.

    Thank you very much
     

    Attached Files:

  3. skipper86

    skipper86 TS Rookie Posts: 19

    did u scanned your registry for broken entries... this problem may occur to corrupt registry entries...! Download Registry Fixing tool..!
    http://www.reginout.com/
     
  4. scr1b3

    scr1b3 TS Rookie Topic Starter Posts: 22

    I will try that today. Thank you
     
  5. scr1b3

    scr1b3 TS Rookie Topic Starter Posts: 22

    Well that didn't work, I just got another BSOD again today.
     
  6. faizanshakyboy

    faizanshakyboy TS Rookie

    Solution

    i tried this fix and it worked:

    Remove flashy games and/or untrusted antiviruses/antispywares. Conduct the security scan through the most powerful scanners only.

    Article Source: http://EzineArticles.com/4247551
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...