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

BSOD yesterday


  • Please log in to reply
1 reply to this topic

#1 Necrotheologist

Necrotheologist

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:09 PM

Posted 15 July 2010 - 01:18 PM

The system is running Windows XP service pack 3 and it is a Dell XT/2. The system has been rebooted and seems fine so far, I'm just wondering what the cause might be.

I've managed to pull the dump file out, but this is the first time I'm looking at something like this, so I'm not sure how to read this block of data. Any help would be appreciated! Thanks!


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


Loading Dump File [C:\Documents and Settings\mcroberts\Desktop\Katy Dump\Mini071410-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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jul 14 17:50:51.031 2010 (UTC - 7:00)
System Uptime: 2 days 10:16:53.727
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bf8059e6, 0, 8054b51a, 2}


Could not read faulting driver name
Unable to load image \SystemRoot\system32\DRIVERS\igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
Probably caused by : igxpmp32.sys ( igxpmp32+5460d )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bf8059e6, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8054b51a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bf8059e6

FAULTING_IP:
nt!ExFreePoolWithTag+23a
8054b51a 668b4efa mov cx,word ptr [esi-6]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

TRAP_FRAME: ba50bc64 -- (.trap 0xffffffffba50bc64)
ErrCode = 00000000
eax=bf805900 ebx=8a85e020 ecx=bf8059ec edx=89d20358 esi=bf8059ec edi=87d22130
eip=8054b51a esp=ba50bcd8 ebp=ba50bd0c iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ExFreePoolWithTag+0x23a:
8054b51a 668b4efa mov cx,word ptr [esi-6] ds:0023:bf8059e6=905b
Resetting default scope

LAST_CONTROL_TRANSFER: from 80520386 to 804f9f43

STACK_TEXT:
ba50bbe4 80520386 00000050 bf8059e6 00000000 nt!KeBugCheckEx+0x1b
ba50bc4c 805445b0 00000000 bf8059e6 00000000 nt!MmAccessFault+0x9a8
ba50bc4c 8054b51a 00000000 bf8059e6 00000000 nt!KiTrap0E+0xd0
ba50bd0c 804f1af3 bf8059ec 00000000 ba50bd28 nt!ExFreePoolWithTag+0x23a
ba50bd1c b80bf60d bf8059ec ba50bd68 b8079158 nt!IoFreeWorkItem+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
ba50bd28 b8079158 bf8059ec 87d22130 89d20040 igxpmp32+0x5460d
ba50bd68 80576ad5 89d20040 9a9d39a4 8056485c igxpmp32+0xe158
ba50bd7c 80538789 87d22130 00000000 8a85e020 nt!IopProcessWorkItem+0x13
ba50bdac 805cff62 87d22130 00000000 00000000 nt!ExpWorkerThread+0xef
ba50bddc 8054611e 8053869a 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
igxpmp32+5460d
b80bf60d ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: igxpmp32+5460d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igxpmp32

IMAGE_NAME: igxpmp32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49777abe

FAILURE_BUCKET_ID: 0x50_igxpmp32+5460d

BUCKET_ID: 0x50_igxpmp32+5460d

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,286 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:09 PM

Posted 15 July 2010 - 02:03 PM

For info only, http://support.microsoft.com/kb/894278.

I am moving this thread to Am I Infected forum.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users