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

Minidump error


  • Please log in to reply
No replies to this topic

#1 n1954

n1954

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:07 AM

Posted 15 March 2009 - 08:11 AM

I keep getting a Minidump error and it reboots computer. I have the following:
Windows XP Home Edition
Dell Dimision Dim 300
Intel Celeron 2.66 GHZ
512 Ram

I have tried different memory, different power supply, ran scannow, ran chkdsk, ran different repairs with no avail. I have taken everything out down to the basic. It seems to be a software glitch and I can not figure this out. :thumbsup:
Any help would greatly be appreciated.
Below is the Windows Debugger info that I followed from somes post on this site.




Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


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

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Mar 15 08:09:21.140 2009 (GMT-5)
System Uptime: 0 days 0:00:25.687
Loading Kernel Symbols
...............................................................
.................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {10f0e534, 2, 0, 82777817}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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: 10f0e534, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 82777817, address which referenced memory

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


READ_ADDRESS: 10f0e534

CURRENT_IRQL: 2

FAULTING_IP:
+2e5
82777817 8b5218 mov edx,dword ptr [edx+18h]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f850eb6c to 82777817

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
eed2598c f850eb6c eed25a7b 00000001 00360037 0x82777817
eed25990 eed25a7b 00000001 00360037 00440033 NDIS!ndisMiniDriverListLock
eed25994 00000000 00360037 00440033 00a80004 0xeed25a7b


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0xD1_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0xD1_ANALYSIS_INCONCLUSIVE

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

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users