2008-04-06, 09:21
  #1
Medlem
Hej!
Hur öppnar jag denan fil så att jag kan läsa den?
Mini040608-01.dmp
Citera
2008-04-06, 09:47
  #2
Medlem
Förbannads avatar
http://filext.com/file-extension/dmp

Varsågod.
Citera
2008-04-06, 09:52
  #3
Medlem
Citat:
Ursprungligen postat av Förbannad
http://filext.com/file-extension/dmp

Varsågod.


Tack, men tror jag är blind, står inte vad jag kan läsa filen med för program =/
Citera
2008-04-06, 09:59
  #4
Medlem
Packans avatar
Citat:
Ursprungligen postat av Softar
Tack, men tror jag är blind, står inte vad jag kan läsa filen med för program =/


Citat:
Various programs use this extension; too many to list individually. Take clues from the location of the file as a possible pointer to exactly which program is producing the file. The file's date and time can also help if you know which programs you were running when the file was written.

Beror alltså helt på vad det är.
Citera
2008-04-06, 10:10
  #5
Medlem
Här är min debug fil som jag fick efter bluscreen hur f*n vet jag vad som orsakade felet?

Citat:
Citat:
Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Users\Robin\Desktop\Mini040608-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;C:\Windows\system32 \drivers
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
Debug session time: Sun Apr 6 08:54:28.261 2008 (GMT+2)
System Uptime: 0 days 13:53:51.930
Loading Kernel Symbols
.................................................. .................................................. ....................................
Loading User Symbols
Loading unloaded module list
......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 113d, 8bf0007, 850c1a10}

*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
GetPointerFromAddress: unable to read from 821315ac
Unable to read MiSystemVaType memory at 821117e0
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify checksum for msrpc.sys
*** WARNING: Unable to verify checksum for Fs_Rec.SYS
*** WARNING: Unable to verify checksum for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for AmdLLD.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify checksum for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for iMON_PAD.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify checksum for TSDDD.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for spsys.sys -


Probably caused by : klim6.sys ( klim6+1eb0 )

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

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* 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: 0000113d, (reserved)
Arg3: 08bf0007, Memory contents of the pool block
Arg4: 850c1a10, Address of the block of pool being deallocated

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

GetPointerFromAddress: unable to read from 821315ac
Unable to read MiSystemVaType memory at 821117e0



POOL_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
Unable to read MiSystemVaType memory at 821117e0
850c1a10

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: Azureus.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 820e7ce8 to 820d8681
Citera
2008-04-06, 16:16
  #6
Medlem
tempeZZts avatar
Minidumpfiler

Minidumpfilerna är de som skickas som rapport till Microsoft när systemet frågar dig om du vill skicka en sådan. Det är inte lätt att tyda en sådan dump, men lite hjälp på vägen kan du kanske få här:

http://support.microsoft.com/kb/315263/sv
Citera

Skapa ett konto eller logga in för att kommentera

Du måste vara medlem för att kunna kommentera

Skapa ett konto

Det är enkelt att registrera ett nytt konto

Bli medlem

Logga in

Har du redan ett konto? Logga in här

Logga in