« previous next »
Pages: [1] 2   Go Down

Author Topic: Minidump  (Read 628 times)

Offline Slash27

  • Plutonium Member
  • *******
  • Posts: 12798
Minidump
« on: November 15, 2003, 06:51:22 PM »
My pc has began to shut down and restart on its own. After the restart I get a " Your system has recovered from a serious error" message. The files causing the problem contain "Minidump" in the name. What the hell is this? I sent the error report to MS but all it would tell me is that an unknown driver caused it. Anyone have a clue as to what a minidump is and how to fix it?
Logged

Offline Mars

  • Zinc Member
  • *
  • Posts: 24
      • http://www.screaminmeanies.com
Minidump
« Reply #1 on: November 15, 2003, 07:15:47 PM »
Sounds like you've been wacked by a worm, trojan or some other sort of malware. Make sure your Anti-Virus software is up to date and try scanning the system and see if something rears it head.  :eek:
Logged
"NO!!......NO!!!!..I WON'T eat it!!"
                    -Christopher Walken in "Mouse Hunt"-

Offline zmeg

  • Silver Member
  • ****
  • Posts: 936
Minidump
« Reply #2 on: November 15, 2003, 10:30:45 PM »
Check the cooling fan on your motherboard chip.
Logged

Offline Dinger

  • Silver Member
  • ****
  • Posts: 1705
Minidump
« Reply #3 on: November 15, 2003, 11:06:45 PM »
uhh.
shut down and restart is the XP default handling of a system error.  In the past, you would have gotten a BSOD.  You can still get a BSOD, you just need to change the system settings with regard to system error handling.
When you then get the BSOD, you can copy down the error type that caused it, and the register values.
For example, it often is a driver error.  The STOP error type, and the memory registers listed will help you determine which is the offending driver.
Logged

Offline Saltty

  • Zinc Member
  • *
  • Posts: 33
Minidump
« Reply #4 on: November 16, 2003, 01:45:31 AM »
Same trouble here....I think it maybe be a printer driver that's not xp compliant. Gwad I wish I'd ordered this box with 98 se....xp been a pain in my@#$%. Will let ya know what I find...Loading new driver from epson now.

Hey Dinger how the heck are ya!!!
« Last Edit: November 16, 2003, 01:48:52 AM by Saltty »
Logged

Offline Saltty

  • Zinc Member
  • *
  • Posts: 33
Minidump
« Reply #5 on: November 16, 2003, 04:33:24 AM »
Well I ran my virus program and it was a worm....
Logged

Offline qts

  • Nickel Member
  • ***
  • Posts: 782
      • None yet
Minidump
« Reply #6 on: November 16, 2003, 05:28:44 AM »
Just for reference, minidump is not the cause of the error, it's a 64K file called minidump.dmp which contains error information. Go to the Properties tab of My Computer and click the Advanced Tab then Startup and Recovery. Look under Write Debugging Information and you'll see that minidump.dmp gets created when you have 'Small Memory Dump' selected.
Logged

Offline Heater

  • Silver Member
  • ****
  • Posts: 1381
Minidump
« Reply #7 on: November 16, 2003, 09:17:01 AM »
to expand on what qts said above,
the minidump can be used with the debugger & symbols from Microsoft to track down the root cause of the problem. the backtrace from the minidump looks something like this:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini113002-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: C:\windows;C:\WINDOWS\system32
Windows XP Kernel Version 2600 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054a130
Debug session time: Sat Nov 30 22:22:19 2002
System Uptime: 0 days 1:19:08.813
Loading Kernel Symbols
............................. ............................. ............................. ............................. ................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 0, 86e17188}

unable to get pool big page table - either wrong symbols or pool tagging is disabled
Bad allocation size @86e17000, zero is invalid
Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+ae )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 00000000, Memory contents of the pool block
Arg4: 86e17188, Pointer to pool header

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

unable to get pool big page table - either wrong symbols or pool tagging is disabled
Bad allocation size @86e17000, zero is invalid

BUGCHECK_STR:  0xc2_7

DEFAULT_BUCKET_ID:  DRIVER_FAULT

LAST_CONTROL_TRANSFER:  from 8053850d to 804f52af

IRP_ADDRESS:  85872578

STACK_TEXT:  
f7aeeb10 8053850d 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x19
f7aeeb58 804f0514 86e17188 00000000 858725b8 nt!ExFreePoolWithTag+0x23b
f7aeebac 804f9a29 858725b8 f7aeebf8 f7aeebec nt!IopCompleteRequest+0xf4
f7aeebfc 804fd5ba 00000000 00000000 00000000 nt!KiDeliverApc+0xb1
f7aeec18 804f6044 804f5dc2 e1ff6248 00000000 nt!KiSwapThread+0x86
f7aeec50 bf879e88 00000003 85ed9418 00000001 nt!KeWaitForMultipleObjects+0x282
f7aeec88 bf879dd2 00000002 85ed9418 bf80c937 win32k!xxxMsgWaitForMultipleObjects+0xae
f7aeed34 bf80b656 e1ff6248 00000001 f7aeed64 win32k!xxxDesktopThread+0x182
f7aeed44 bf874990 bf994180 f7aeed64 0071fff4 win32k!xxxCreateSystemThreads+0x68
f7aeed54 805303c4 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x20
f7aeed54 7ffe0304 00000000 00000022 00000000 nt!KiSystemService+0xc9
00000000 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
win32k!xxxMsgWaitForMultipleObjects+ae
bf879e88 8945fc           mov     [ebp-0x4],eax

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  win32k!xxxMsgWaitForMultipleObjects+ae

MODULE_NAME:  win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3d6de5e5

STACK_COMMAND:  kb

BUCKET_ID:  0xc2_7_win32k!xxxMsgWaitForMultipleObjects+ae

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

0: kd> ! Process
GetUlongFromAddress: unable to read from 8054aad4
Could not find Session Id at f7dc1000.
PROCESS 85d62598  SessionId: 0  Cid: 02c0    Peb: 7ffdf000  ParentCid: 0290
    DirBase: 0b7ce000  ObjectTable: e1b8f700  TableSize:   0.
    Image: csrss.exe
    VadRoot 85ab5e40 Vads 91 Clone 0 Private 299. Modified 2088. Locked 0.
    DeviceMap e1000138
    Token                             e1b80030
GetUlongFromAddress: unable to read from 80549120
unable to read memory @ 7ffe0000
    ElapsedTime                     1172:59:15.0968
    UserTime                          0:00:00.0000
    KernelTime                        0:00:00.0000
    QuotaPoolUsage[PagedPool]         34832
    QuotaPoolUsage[NonPagedPool]      5888
    Working Set Sizes (now,min,max)  (731, 50, 345) (2924KB, 200KB, 1380KB)
    PeakWorkingSetSize                1210
    VirtualSize                       20 Mb
    PeakVirtualSize                   39 Mb
    PageFaultCount                    4026
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      360
Logged
HiTech is a DWEEB-PUTZ!
I have multiple personalities and none of them like you !!!

Offline Slash27

  • Plutonium Member
  • *******
  • Posts: 12798
Minidump
« Reply #8 on: November 27, 2003, 01:27:28 AM »
So should I disable the auto restart on a memory dump? And how do I fix the memory dump?  If you guys already told me how to fix it Im sorry, Im not computer savy at all. You may have to break out finger paints and playdough to explain it to me.
Logged

Offline qts

  • Nickel Member
  • ***
  • Posts: 782
      • None yet
Minidump
« Reply #9 on: November 27, 2003, 02:12:08 PM »
Absolutely. If you don't disable autorestart, you could get youself stuck in a reboot loop, with your PC going more and more wrong, and being unable to diagnose the root cause. This is particularly important when you have your computer on 24/7 and can't intervene because you're asleep or at work. It's better to wake to a BSOD than a totally screwed machine.
Logged

Offline boxboy28

  • Gold Member
  • *****
  • Posts: 2265
      • http://none
Minidump
« Reply #10 on: November 27, 2003, 09:17:28 PM »
from my experience whan your getting those erros it 1 of 3 things

1st your power suply isnt giving stable V's to the 3 parts it supplies

2nd your ram isnt running at the right speed for the CPU.

3rd ive heard of people using the onboard LAN JACK an having probelms with it, if it happens when your on the net then look for updated drivers.
Logged
^"^Nazgul^"^    fly with the undead!
Jaxxo got nice tata's  and Lyric is Andre the giant with blond hair!

Offline SixxGunn

  • Copper Member
  • **
  • Posts: 125
Minidump
« Reply #11 on: November 28, 2003, 12:15:50 AM »
Slash

This may not be the case in your situation.

Do you have WinXP, And if so have you resently done a system restore.

There is a patch at the microsoft download site that describes just what you are talking about. And will fix your problem.

I will look and see if I can find it again, its been a few weeks since I saw it.

If I find the DL patch I'll post a link to it.
Logged

Offline SixxGunn

  • Copper Member
  • **
  • Posts: 125
Minidump
« Reply #12 on: November 28, 2003, 12:38:57 AM »
Logged

Offline Slash27

  • Plutonium Member
  • *******
  • Posts: 12798
Minidump
« Reply #13 on: November 28, 2003, 10:24:10 AM »
Thank you.  Ill check it out and get back to you.
Logged

Offline Saltty

  • Zinc Member
  • *
  • Posts: 33
Minidump
« Reply #14 on: November 28, 2003, 10:58:44 PM »
Slash I been having to same trouble.....here what I've done to now to try to track it down.
system is
Asus A7N8X Deluxe mb
2800 amd cpu
2 512 matched Kingston ram
9600 ati raedon vid

I 've memtested my ram....booted them one at a time...still crashed

flash latest bios on motherboard

updated Ati drivers for video card

updated xp

no luck...not much hair left either...damn
I have tried to use dumpchk on my minidump file but I can't seem to get the file path correct to open it
heres the error message I get
BCCode : 9c     BCP1 : 00000000     BCP2 : 805366F0     BCP3 : C4204000    
BCP4 : 00000136     OSVer : 5_1_2600     SP : 1_0     Product : 256_1

I can say my system stay up much longer now that i've flash the bios
Temps seem fine....cpu is 46c  voltages are 12v 12.672 5v 4.811
 3.3v 3.312
lets hope for some expert help here
Saltty
« Last Edit: November 28, 2003, 11:06:22 PM by Saltty »
Logged
Pages: [1] 2   Go Up
« previous next »