Lỗi màn hình xanh xin các bác giúp em với

**blacksea** · 25-09-2008 07:10

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

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

Symbol search path is: SRV*c:\websymbols*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, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Sep 24 12:23:53.937 2008 (GMT+7)
System Uptime: 0 days 1:02:48.655
Loading Kernel Symbols
.................................................. .................................................. .........................
Loading User Symbols
Loading unloaded module list
..............
Unable to load image gHidPnp.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gHidPnp.Sys
*** ERROR: Module load completed but symbols could not be loaded for gHidPnp.Sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f7aaa584, 2, 0, f76d95b2}

Probably caused by : gHidPnp.Sys ( gHidPnp+25b2 )

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

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

READ_ADDRESS: f7aaa584

CURRENT_IRQL: 2

FAULTING_IP:
gHidPnp+25b2
f76d95b2 803e03 cmp byte ptr [esi],3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 804e18ef to f76d95b2

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805572a4 804e18ef 8980b2d0 8952c008 8980b388 gHidPnp+0x25b2
805572d4 ba2830d5 8952c008 88f29cc0 89748028 nt!IopfCompleteRequest+0xa2
8055733c ba283d47 88fc2a98 00000000 897487d8 USBPORT!USBPORT_CompleteTransfer+0x373
8055736c ba284944 026e6f44 897480e0 897480e0 USBPORT!USBPORT_DoneTransfer+0x137
805573a4 ba28613a 89748028 804e56ec 89748230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
805573d0 ba29424b 89748028 804e56ec 89748028 USBPORT!USBPORT_DpcWorker+0x224
8055740c ba2943c2 89748028 00000001 80561f20 USBPORT!USBPORT_IsrDpcWorker+0x38f
80557428 804dcd12 8974864c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80557440 80561cc0 ffdffc50 00000000 80561cc0 nt!KiRetireDpcList+0x61
80557450 804dcbf7 00000000 0000000e 00000000 nt!KiIdleThread0
80557454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

STACK_COMMAND: kb

FOLLOWUP_IP:
gHidPnp+25b2
f76d95b2 803e03 cmp byte ptr [esi],3

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: gHidPnp+25b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: gHidPnp

IMAGE_NAME: gHidPnp.Sys

DEBUG_FLR_IMAGE_TIMESTAMP: 469f4747

FAILURE_BUCKET_ID: 0xD1_gHidPnp+25b2

BUCKET_ID: 0xD1_gHidPnp+25b2

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

0: kd> lmvm gHidPnp
start end module name
f76d7000 f76e1000 gHidPnp T (no symbols)
Loaded symbol image file: gHidPnp.Sys
Image path: gHidPnp.Sys
Image name: gHidPnp.Sys
Timestamp: Thu Jul 19 18:13:11 2007 (469F4747)
CheckSum: 00006CA6
ImageSize: 0000A000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
xin các bác chỉ cho em cách giải quyết với

**windows_xp2** · 25-09-2008 08:50

Bạn thử repair hoặc cài lại windows đi nhé.
__________________

**tranmauhanh** · 25-09-2008 13:42

thường do bị ram, ram dỡ có cài lại win cũng vậy thôi.nên tét lại ram xem.Ngoài ra có thể do nguồn quá tệ.Nói chung lỗi này nhiều nguyên nhân lắm.tét từng cái một.