System Crashes...but why??

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
For a long time, my computer has been getting fatal errors and restarting.
It frequently occurs when inserting a cd/dvd or working with a disc already
in the drive. I suspected the driver for the disc drive was at fault. I just
replaced the drive with a brand new one and the first thing it did was
restart when I put a disc in the drive. The event log showed the following
error:

Error code 100000d1, parameter1 052349e4, parameter2 00000002, parameter3
00000001, parameter4 122171f3.

Anyone know how to figure out what's going on?
 
Thank you, I have not had a chance to try that yet (my power supply died...)
but I will post back my results.
 
Ok, so I installed the only hotfix that sounded like it applied to my
situation and it did not resolve the issue. Microsoft indicates that this
error message means that I do have a bad device driver, but how do I find the
driver?? I'd really rather not reformat just for my cd drives, especially
when I might reinstall the culprit driver.
 
Here's what I've been able to get from the debugger but I'm not sure what to
do with it...


Loading Dump File [C:\WINDOWS\Minidump\Mini031807-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV**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, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Mar 18 15:20:22.703 2007 (GMT-7)
System Uptime: 0 days 3:23:31.383
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {5450018, 2, 1, 7c911713}

Probably caused by : Unknown_Image ( INVALID_CONTEXT )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 05450018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c911713, address which referenced memory

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


CURRENT_IRQL: 2

FAULTING_IP:
+7c911713
7c911713 66894118 mov word ptr [ecx+18h],ax

PROCESS_NAME: explorer.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT

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

0: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
02fbf67c 7c820fd6 000a0000 00000000 01d41b70 0x7c911713
02fbf6ac 7ca0cad5 001147e0 0013e850 00000005 0x7c820fd6
02fbf6d4 7ca0c80b 02fbf6e8 02fbf910 00000000 0x7ca0cad5
02fbf8f4 7ca9af78 02fbf910 02fbf91c 7ca9afd3 0x7ca0c80b
02fbf900 7ca9afd3 0017e65c 02fbf930 00000004 0x7ca9af78
02fbf91c 7cb35518 02fbf930 00000004 02fbf9a0 0x7ca9afd3
02fbf93c 7caa0ea8 000b2998 00000000 00000000 0x7cb35518
02fbf960 7caa0fcc 7c9d86a8 000b2998 00000000 0x7caa0ea8
02fbf97c 7cb1edeb 01dda330 00000000 00000000 0x7caa0fcc
02fbf9ac 7cb219cb 0225f508 0226ba28 0224cdb8 0x7cb1edeb
02fbf9d4 7cb21a7a 00000000 00000000 02fbfb60 0x7cb219cb
02fbf9e4 7ca48d7d 00000000 039efdf8 7c9f75e8 0x7cb21a7a
02fbfb60 7c9f1da1 002300da 000004a8 00000000 0x7ca48d7d
02fbfba4 77d48734 002300da 000004a8 00000000 0x7c9f1da1
02fbfbd0 77d48816 7c9f1d4b 002300da 000004a8 0x77d48734
02fbfc38 77d489cd 000a5418 7c9f1d4b 002300da 0x77d48816
02fbfc98 77d48a10 02fbfcd8 00000000 02fbfcc0 0x77d489cd
02fbfca8 75f9d7c5 02fbfcd8 00000000 01dd70c8 0x77d48a10
02fbfcc0 75fa527a 02fbfcd8 0011ac10 00000000 0x75f9d7c5
02fbff34 80584c8a 86150be8 857ebda8 7ffaf000 0x75fa527a
 
Hi everyone,
I finally figured out the problem and have seen it on another computer too. It was MusicMatch Jukebox. Once I uninstalled music match the error went away. I Figured it out by analyzing minidumps using Microsoft Debugging Tools for Windows
 
Back
Top