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

system error


  • Please log in to reply
2 replies to this topic

#1 chugg

chugg

  • Members
  • 627 posts
  • OFFLINE
  •  
  • Local time:02:59 PM

Posted 08 October 2008 - 01:18 AM

I got the blue screen upon start up saying serious system error. So i turned the power on and off and microsoft message came up asking me to send an error report. The report popped up about whats wrong and below is what it said. Is this serious?

C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\WERe8ec.dir00\Mini100808-01.dmp
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\WERe8ec.dir00\sysdata.xml

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,536 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:59 PM

Posted 08 October 2008 - 07:31 AM

I believe the message displayed only reflects that there was a minidump and subsequent report.

Seeing the details of the minidump report would probably prove more fruitful than focusing on the error message about the minidump.

What's reflected as recent errors in Event Viewer?

Louis

#3 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:03:59 PM

Posted 08 October 2008 - 04:00 PM

Try this procedure to read the dump file from the Blue Screen error. It may appear intimidating, but just go through it step-by-step and it'll work for you. Any problems, just post back and we'll figure out what to do.

INTRODUCTION: A memory dump is what happens when Windows crashes. The memory is dumped into the pagefile and saved for the next reboot. Once Windows reboots, it reclaims the memory dump data from the pagefile and saves it to a file (usually ending in .dmp). Analyzing these dump files can help to figure out what's causing your system to crash. While they don't offer a "sure" fix, they provide clues to the cause of the crash so that we can work on fixing them. In my experience most system crashes are caused by faulty/corrupted drivers, malware, or hardware failures (in that order).

Step 1: The first thing to do when your system crashes is to reboot - that'll save the memory dump file so it's able to be accessed. Windows may ask permission to send the file for online analysis. I would suggest always allowing it to be sent. Most times you won't get anything back, but occasionally it'll point out the problem and will save you a lot of work. Also, quite often the first crash is also the only crash (as Windows will fix the problem when it reboots) - so there's no need to worry unless the crashes repeat themselves. If you can't get into Windows (either in normal or Safe Mode), then just post straight to the appopriate forum and we'll work from there.

Windows Vista: http://www.bleepingcomputer.com/forums/f/72/windows-vista/
Windows XP: http://www.bleepingcomputer.com/forums/f/56/windows-xp-home-and-professional/
Windows 2000: http://www.bleepingcomputer.com/forums/f/83/windows-nt200020032008/


Step 2: The next thing to do is to ensure that you're free of malware. Malware can get onto your system and corrupt your installed protection (and can cause system crashes), so I'd suggest you perform one of the free, online scans at this link: http://www.bleepingcomputer.com/blogs/usas...?showentry=1252

Step 3: Once that's over with, search your hard drive for files ending in .dmp There are several types that Windows saves:
1) A complete memory dump or a kernel memory dump - usually saved in the C:\Windows directory and named MEMORY.DMP
2) A small memory dump (AKA "minidump") - usually saved in the C:\Windows\Minidump directory. These are named Miniwwxxyy-zz.dmp - where the ww is the number of the month, the xx is the number of the day, the yy is the number of the year, and the zz is the number of the crash dump that day (ie: Mini070108-03.dmp is the 3rd minidump generated on July 1, 2008)

On some systems the directories where the dump files are stored are protected by being identified as Hidden and System files.
To show Hidden and System files in Windows Explorer, go to Start...All Programs...Accessories...Windows Explorer.
- Once opened, select the Tools...File Options menu item (in Vista you may have to press and hold the "Alt" key to view this menu).
- Then go to the View tab and check the box to "Show Hidden Files and Folders", and also uncheck "Hide Protected Operating System Files".
- You will get a dialog that asks you if you're sure you want to do this - click on "Yes" to allow the change
- Then click OK to the prompts to exit the dialog and you'll be able to view these hidden and system directories.
CAVEAT - these files are hidden for a reason - messing with some of them can cause problems with your system.

Step 4: Once you've located the memory dump file(s), then you'll have to get a debugger to analyze them. The one that I'm familiar with is the free Microsoft Debugging Tools for Windows. Download the version (32 or 64 bit) that's appropriate for the operating system that you'll be running the debugger on. Here's the link: http://www.microsoft.com/whdc/devtools/deb...ng/default.mspx

Once it's downloaded, double click on it to install it. Once it's installed, open the debugger by going to Start...All Programs...Debugging Tools For Windows...and click on WinDbg. Once you've opened the program, click on the File menu item, then on Symbol File Path.

Step 5: In the window that opens, insert the exact text on the next line in the Symbol File Path box (this is a critical step, if done incorrectly you'll end up with symbol errors):

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

It's easiest to copy it, then paste it into the box. Once that's done, click on OK to exit the dialog. Next, click on File...Save Workspace. This'll save the symbol path for future use.

Step 6: Next, go to File...Open Crash Dump and browse to the location of the memory dump file and double click on it to load it into the Debugger. You may be prompted to save the workspace again - just answer "No" to it. A window will open and the dump file text will fill the debugging screen.

Here's an example of of an analysis report from a Minidump file (complete and kernel dumps are much larger):

Microsoft Windows Debugger Version 6.8.0004.0 AMD64
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR\Desktop\Mini070108-03.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) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Tue Jul 1 16:28:22.439 2008 (GMT-4)
System Uptime: 0 days 0:04:00.921
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 84c64731, f4fecc3c, 0}



Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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


Step 7: The next step is to click on the !analyze -v link that's highlighted in blue in the above report. This will generate more information and will look something like this:

Microsoft Windows Debugger Version 6.8.0004.0 AMD64
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR\Desktop\Mini070108-03.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) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Tue Jul 1 16:28:22.439 2008 (GMT-4)
System Uptime: 0 days 0:04:00.921
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 84c64731, f4fecc3c, 0}



Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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: 84c64731, The address that the exception occurred at
Arg3: f4fecc3c, 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:
+ffffffff84c64731
84c64731 ?? ???

TRAP_FRAME: f4fecc3c -- (.trap 0xfffffffff4fecc3c)
Unable to read trap frame at f4fecc3c

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 84c64731

STACK_TEXT:
f4feccac 00000000 00000000 01790000 00000000 0x84c64731


STACK_COMMAND: .trap 0xfffffffff4fecc3c ; kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x8E_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x8E_ANALYSIS_INCONCLUSIVE

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


Step 8: Once this is done, copy the text of the dump file analysis report. To do this, select the Edit menu item in the Debugging Tools window, then select Copy Window Text to Clipboard. Then return to Bleeping Computer and paste the information into your next post.

Step 9: If you haven't started a topic for your issue yet, you can start one at the appropriate link below. Please be sure and let us know the make and model of your system along with the symptoms that you're experiencing.

Windows Vista: http://www.bleepingcomputer.com/forums/f/72/windows-vista/
Windows XP: http://www.bleepingcomputer.com/forums/f/56/windows-xp-home-and-professional/
Windows 2000: http://www.bleepingcomputer.com/forums/f/83/windows-nt200020032008/


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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users