What are these files?

Phumfeinz · 04-08-2006, 03:46 PM

My computer crashed, and came back saying it recovered from a serious error. The files included were:

C:\WINDOWS\Minidump\Mini040806-02.dmp
C:\DOCUME~1\Jake\LOCALS~1\Temp\WER1.tmp.dir00\sysd ata.xml

Are these important?

**dragon2309** · 04-08-2006, 03:53 PM

your mistaken, they are not the files that CAUSED the error, they are the files created by windows to send off in the error report to microsoft. If you send the error report, it should tell you there is extra info and then it will take you to Microsoft Online Crash Analyser. there it should give you a general idea about what caused the crash....

dragon

Phumfeinz · 04-08-2006, 03:55 PM

Ah right, thanks.

**dragon2309** · 04-08-2006, 04:00 PM

no problem, you may also be able to view the error, if you go to Control Panel - click on Administrative Tools - then click on Event Viewer. When it opens click SYSTEM and then scroll through to the approx time/dat where the crash ocured, you can sometimes tell what happened by looking at these logs.

dragon

Phumfeinz · 04-08-2006, 04:18 PM

Thanks. I believe it was something to do with this:

The Application Management service terminated with the following error:
The specified module could not be found.

or

The open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\System32\wbem\wmiaprpl.dll" has taken longer than the established wait time to complete. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted.

04-08-2006, 03:46 PM	#1 (permalink)
Phumfeinz Silver Member Join Date: Apr 2005 Posts: 120	What are these files? My computer crashed, and came back saying it recovered from a serious error. The files included were: C:\WINDOWS\Minidump\Mini040806-02.dmp C:\DOCUME~1\Jake\LOCALS~1\Temp\WER1.tmp.dir00\sysd ata.xml Are these important?

04-08-2006, 03:53 PM	#2 (permalink)
dragon2309 P.I Dragon Join Date: May 2005 Location: KENT, UK Age: 20 Posts: 8,429	your mistaken, they are not the files that CAUSED the error, they are the files created by windows to send off in the error report to microsoft. If you send the error report, it should tell you there is extra info and then it will take you to Microsoft Online Crash Analyser. there it should give you a general idea about what caused the crash.... dragon __________________ Intel Core2Duo E6600 @ 3.1Ghz - (__CPU__) eVGA 680i SLi - (__MOB__) 4Gb Corsair Dominator DDR2-800 (4x1024Mb) - (__RAM__) 250Gb Western Digital SATAII 7200rpm - (__HDD__) nVidia BFG 8800GTS OC 320Mb - (__GFX__) LG DVD+/-RW 18x DVD-RAM - (__OPT__) Triple Boot - [XP Pro] + [Vista Ultimate] + [Ubuntu 7.10] - (__OS__) [3DMARK'03 :: 25,587] --- [3DMARK'05 :: 13,989] --- [3DMARK'06 :: 8791] - (__BENCHMARKS__) dragon2309.co.uk - a little slice of geek

04-08-2006, 04:00 PM	#4 (permalink)
dragon2309 P.I Dragon Join Date: May 2005 Location: KENT, UK Age: 20 Posts: 8,429	no problem, you may also be able to view the error, if you go to Control Panel - click on Administrative Tools - then click on Event Viewer. When it opens click SYSTEM and then scroll through to the approx time/dat where the crash ocured, you can sometimes tell what happened by looking at these logs. dragon __________________ Intel Core2Duo E6600 @ 3.1Ghz - (__CPU__) eVGA 680i SLi - (__MOB__) 4Gb Corsair Dominator DDR2-800 (4x1024Mb) - (__RAM__) 250Gb Western Digital SATAII 7200rpm - (__HDD__) nVidia BFG 8800GTS OC 320Mb - (__GFX__) LG DVD+/-RW 18x DVD-RAM - (__OPT__) Triple Boot - [XP Pro] + [Vista Ultimate] + [Ubuntu 7.10] - (__OS__) [3DMARK'03 :: 25,587] --- [3DMARK'05 :: 13,989] --- [3DMARK'06 :: 8791] - (__BENCHMARKS__) dragon2309.co.uk - a little slice of geek

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

04-08-2006, 03:55 PM	#3 (permalink)
Phumfeinz Silver Member Join Date: Apr 2005 Posts: 120	Ah right, thanks.

04-08-2006, 04:18 PM	#5 (permalink)
Phumfeinz Silver Member Join Date: Apr 2005 Posts: 120	Thanks. I believe it was something to do with this: The Application Management service terminated with the following error: The specified module could not be found. or The open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\System32\wbem\wmiaprpl.dll" has taken longer than the established wait time to complete. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted.