[Urgente] BSOD no XP

[DiogoC.]

Boas

Cada vez que ligo o meu PC pela primeira vez no dia aparece um BSOD alguns segundos depois de aparecer o desktop. Desligo a tomada, ligo outra vez o computador e o Windows inicia normalmente e aparece a mensagem: "O Windows recuperou de um erro grave".

Eis um screenshot do BSOD:



Peguei no ficheiro dump e procedi à "leitura" através do Debugging Tools For Windows. Apareceu-me o seguinte:

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


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sun Nov 22 11:56:14.375 2009 (GMT+0)
System Uptime: 0 days 0:02:10.953
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f06c6e11, 2, 8, f06c6e11}

Unable to load image atapi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atapi.sys
Unable to load image sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : atapi.sys ( atapi!IdeProcessCompletedRequest+664 )

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

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


READ_ADDRESS: f06c6e11

CURRENT_IRQL: 2

FAULTING_IP:
+4c3
f06c6e11 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 804f06ae to f06c6e11

FAILED_INSTRUCTION_ADDRESS:
+4c3
f06c6e11 ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80549b88 804f06ae 00000000 8216b008 8236da58 0xf06c6e11
80549bb8 f83c46fc 825e5ef8 8250f0e8 00000000 nt!MmCheckCachedPageState+0xea
80549be4 f83c4c8e 8216b008 825e5ef8 80549c5f atapi!IdeProcessCompletedRequest+0x664
80549c60 f8483894 8250f0a4 8250f030 00000000 atapi!IdePortCompletionDpc+0x204
80549c9c 82570a0a 82570008 f83c4a8a 80549cb0 sptd+0x11894
80549ca0 82570008 f83c4a8a 80549cb0 80541b9d 0x82570a0a
80549ca4 f83c4a89 80549cb0 80541b9d 8250f0a4 0x82570008
80549ca8 80549cb0 80541b9d 8250f0a4 8250f030 atapi!IdePortStartIo+0x225
80549cc0 00000000 806d99ba 00000008 00000000 nt!MiFreePoolPages+0x4c3


STACK_COMMAND: kb

FOLLOWUP_IP:
atapi!IdeProcessCompletedRequest+664
f83c46fc ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: atapi!IdeProcessCompletedRequest+664

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_atapi!IdeProcessCompletedRequest+664

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_atapi!IdeProcessCompletedRequest+664

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

Alguém me ajude por favor, é urgente.