• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 659
  • Last Modified:

Windows XP Blue Screen Issues.

I have a windows XP laptop that I cannot seem to figure out what is causing persistent Blue Screens.  Following is the analysis from the crash dump:

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 84673008, Address of the IRP
Arg2: 00001bc0
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS:  84673008

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from 00000000 to 804f9f43

STACK_TEXT:  
f60aed94 00000000 00000023 00000003 00000002 nt!_woutput+0x414


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d              pop     ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!_woutput+414

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a784394

FAILURE_BUCKET_ID:  0x44_nt!_woutput+414

BUCKET_ID:  0x44_nt!_woutput+414

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

Any help?  Attached is the mini-dump.
Mini011210-01.dmp
0
Shearers
Asked:
Shearers
  • 5
  • 2
  • 2
1 Solution
 
rixlabsCommented:
Hi,

try this to verify the integrity of your's RAM
http://hcidesign.com/memtest/

0
 
ShearersAuthor Commented:
Memory test ran with no errors detected.
0
 
rixlabsCommented:
to exclude harware problem you can try to use a Live distro of linux and try to stress you machine.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ShearersAuthor Commented:
OK, so you must have missed the crashdump, which points to a driver issue?
0
 
optomaCommented:
That minidump points to the video driver. Get the latest chipset drivers and/or graphics card drivers.

Upload two other recent minidump files to confirm that they all the same.
0
 
ShearersAuthor Commented:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 84c96008, Address of the IRP
Arg2: 00000d64
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS:  84c96008

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 00000000 to 804f9f43

STACK_TEXT:  
f7a1dd1c 00000000 00000044 84c96008 00000d64 nt!_woutput+0x414


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d              pop     ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!_woutput+414

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a784394

FAILURE_BUCKET_ID:  0x44_nt!_woutput+414

BUCKET_ID:  0x44_nt!_woutput+414

Followup: MachineOwner
---------
0
 
ShearersAuthor Commented:
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 86163cd8, Address of the IRP
Arg2: 00000d64
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS:  86163cd8

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80520824 to 8053767a

STACK_TEXT:  
f7234cd4 80520824 00000044 86163cd8 00000d64 nt!MiRemoveUnusedSegments+0x3e3
f7234d0c f76f299e 00000000 86163cd8 86163cd8 nt!MiSetSystemCodeProtection+0x148
f7234d20 805184c9 861f8030 86163cd8 861f20e0 usbhub!USBH_PortIdleNotificationCancelRoutine+0xa2
f7234d38 f77128a0 86163cd8 861415d0 861f20e0 nt!KiNpxFrameToEm87State+0x62
WARNING: Stack unwind information not available. Following frames may be wrong.
f7234d58 f7712b59 001f20e0 861f2028 f7234d7c tosrfusb+0x68a0
f7234d68 8056df51 861f2028 861415d0 8056a5fc tosrfusb+0x6b59
f7234d7c 804e23b5 861415d0 00000000 861a8020 nt!RtlCompareUnicodeString+0x44
f7234dac 80575723 861415d0 00000000 00000000 nt!LsapPort+0x41
f7234db0 861415d0 00000000 00000000 00000000 nt!PsRevertThreadToSelf+0x1
f7234ddc 804ec6d9 804e22f1 80000001 00000000 0x861415d0
00000000 00000000 00000000 00000000 00000000 nt!Magic86400000+0x201


STACK_COMMAND:  kb

FOLLOWUP_IP:
tosrfusb+68a0
f77128a0 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  tosrfusb+68a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tosrfusb

IMAGE_NAME:  tosrfusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44896c2e

FAILURE_BUCKET_ID:  0x44_tosrfusb+68a0

BUCKET_ID:  0x44_tosrfusb+68a0

Followup: MachineOwner
---------
0
 
optomaCommented:
Sorry, attach minidumps (*.dmp)
0
 
ShearersAuthor Commented:
Problem resolved by re-installing drivers
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now