Mon PC plante avec un joli BSOD de mani�re al�atoire.
droopy191 a �crit :
> milsabords wrote:
>> Pas un log, un minidump.
> Je regarde ce que ca donne et je reviens vers vous.
>
Voici ce que ca donne
J'ai l'impression que le probl�me vient de hptpro.sys
ca correspond � une carte Rocket raid 133 HPT372
Merci pour vos lumi�res
*************************************
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINXP\Minidump\Mini100108-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, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Oct 1 21:55:30.265 2008 (GMT-4)
System Uptime: 0 days 1:33:50.963
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {8a46d2a8, 2, 1, 80535af9}
*** WARNING: Unable to verify timestamp for hptpro.sys
*** ERROR: Module load completed but symbols could not be loaded for
hptpro.sys
Probably caused by : hptpro.sys ( hptpro+31d )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8a46d2a8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only
on chips which support this level of status)
Arg4: 80535af9, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 8a46d2a8
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExDeleteResourceLite+1d
80535af9 890f mov dword ptr [edi],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from b9d496af to 80535af9
STACK_TEXT:
ba517a4c b9d496af 884f9008 ba517aa8 ba517a80 nt!ExDeleteResourceLite+0x1d
ba517a5c b9d82242 884f9008 8828e9b0 e2ca8d20 Ntfs!NtfsFreeEresource+0x6b
ba517a80 b9d49587 884a5ef0 ba517aa8 ba517ab3 Ntfs!NtfsDeleteFcb+0x4e
ba517acc b9d6ae7c 884a5ef0 8828e850 e4be3cc8 Ntfs!NtfsTeardownFromLcb+0x1fd
ba517b24 b9d457a4 884a5ef0 e4be3d90 e4be3f28
Ntfs!NtfsTeardownStructures+0x125
ba517b50 b9d686b5 884a5ef0 01be3d90 e4be3f28
Ntfs!NtfsDecrementCloseCounts+0x9e
ba517bd4 b9d68454 884a5ef0 e4be3d90 e4be3cc8 Ntfs!NtfsCommonClose+0x398
ba517c74 804ef18f 8828e770 884e6008 893df210 Ntfs!NtfsFsdClose+0x21f
ba517c84 b9de7459 ba517ce8 804ef18f 8835f1c0 nt!IopfCallDriver+0x31
ba517c8c 804ef18f 8835f1c0 884e6008 89408780 sr!SrPassThrough+0x31
ba517c9c ba4bc31d ba4bc498 8809b168 884e6008 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be
wrong.
ba517ce8 804ef18f 88222c70 884e6008 884e6008 hptpro+0x31d
ba517cf8 80583af8 87bb33b8 00000000 00000000 nt!IopfCallDriver+0x31
ba517d30 805bb466 00bb33d0 00000000 87bb33b8 nt!IopDeleteFile+0x132
ba517d4c 805266ca 87bb33d0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xe0
ba517d64 8050a88a 806e6aa8 87becb08 80561db4 nt!ObfDereferenceObject+0x4c
ba517d8c 8050c0c9 e3f011b0 00000000 89e37b98 nt!MiSegmentDelete+0xec
ba517dac 805cff64 00000000 00000000 00000000
nt!MiDereferenceSegmentThread+0xa7
ba517ddc 805460de 8050c022 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
hptpro+31d
ba4bc31d ?? ???
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: hptpro+31d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hptpro
IMAGE_NAME: hptpro.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3e34dbf8
FAILURE_BUCKET_ID: 0xA_W_hptpro+31d
BUCKET_ID: 0xA_W_hptpro+31d
Followup: MachineOwner
---------
1: kd> lmvm hptpro
start end module name
ba4bc000 ba4be240 hptpro T (no symbols)
Loaded symbol image file: hptpro.sys
Image path: hptpro.sys
Image name: hptpro.sys
Timestamp: Mon Jan 27 02:12:56 2003 (3E34DBF8)
CheckSum: 00009A30
ImageSize: 00002240
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
--
DR
"Droopy191" <droopy191+ng...@free.fr.invalid> a �crit dans le
message de groupe de discussion : 48e4314f$0$15461$426a...@news.free.fr...
> X-Post: fr.comp.sys.pc;fr.comp.os.ms-windows
> Follow-up: fr.comp.os.ms-windows
>
> Mon PC plante avec un joli BSOD de mani�re al�atoire.
>
> droopy191 a �crit :
>> milsabords wrote:
>>> Pas un log, un minidump.
>
>> Je regarde ce que ca donne et je reviens vers vous.
>>
>
>
> Voici ce que ca donne
>
> J'ai l'impression que le probl�me vient de hptpro.sys
> ca correspond � une carte Rocket raid 133 HPT372
>
> Merci pour vos lumi�res
>
>
Vois sur le site du fabricant (Highpoint Technologies) s'il existe une
version du pilote plus r�cente. Voir aussi s'il existe un forum
d'utilisateurs o� ce pb a pu �tre signal�.
Une recherche Google sur hptpro.sys donne + de 3000 r�ponses.
Merci de confirmer ma lecture.
Le pilote est dej� le dernier � jour.
J'ai rien trouv� de correspondant sur google.
Si le pb persiste, je crois que je vais simplement virer la carte qui
est encore la pour g�rer le passif de 2 disques IDE bien bruyants.
--
DR
Tu peut aussi essayer:
- remettre une version N-1
- voir si t'en trouve un via WindowsUpdate
--
@+
Ascadix
adresse @mail valide, mais ajoutez "sesame" dans l'objet pour que �a
arrive.