Ciao,
ieri sera, dopo aver formattato regolarmente, ho installato tutti i programmi necessari.
Per un po tutto ok, salvo che, all'improvviso mi compare una schermata blu di windows, che ho analizzato con il windows debugger e riporta ciò (stavo copiando sul mio pc una cartella di file abbastanza grande):
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Thu May 20 22:40:31.656 2010 (UTC + 2:00)
System Uptime: 0 days 0:13:49.228
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, fff08, 7, 0}
Probably caused by : memory_corruption ( nt!MiDeletePte+3e8 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 000fff08, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 805253ca to 805339ae
STACK_TEXT:
a6024b44 805253ca 0000004e 00000099 000fff08 nt!KeBugCheckEx+0x1b
a6024b84 804ec10e c0005040 01410000 00000000 nt!MiDeletePte+0x3e8
a6024c48 804f2d65 e1750e10 01410fff 00000000 nt!MiDeleteVirtualAddresses+0x162
a6024cf4 8057372e 85b9a538 85e66668 a6024d64 nt!MiRemoveMappedView+0x212
a6024d38 805737da 85aa91b0 85b8e3c0 00000000 nt!MiUnmapViewOfSection+0x12b
a6024d54 804df06b ffffffff 85b9a538 02b5e750 nt!NtUnmapViewOfSection+0x54
a6024d54 7c91eb94 ffffffff 85b9a538 02b5e750 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
02b5e750 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeletePte+3e8
805253ca e95e6bfdff jmp nt!MiDeletePte+0x400 (804fbf2d)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiDeletePte+3e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41108004
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+3e8
BUCKET_ID: 0x4E_99_nt!MiDeletePte+3e8
Followup: MachineOwner
---------
All'inizio sembrava che il problema fosse un caso isolato, e che il tutto derivasse da explorer.exe oppure ntoskrnl.exe: infatti alla prima anlisi del file dump senza i simboli scaricati da microsoft l'analisi riportava alla fine questa scritta "Probably caused by : ntoskrnl.exe ( nt+5c9ae )", ma appena scaricato tutto il problema sembrava derivare da explorer.exe (come si nota dall'analisi del file dump).
Il problema della schermata blu si è verificato nuovamente oggi 2 volte: la prima mentre ricopiavo quella maledetta cartella, allora ho pensato si potesse trattare dei driver della scheda video, una ati radeon 9550 serie x1050 da 256mb, in quanto al momento dell'installazione una schermata mi avvisava della probabile incompatibilità con il mio s.o. :la versione dei driver precedenti era catalyst 10.2, allora ho messo su la versione 7.8 (con relativo net. framework di windows 2.0 per il catalyst control center), dopodichè ho riprovato a copiare le cartelle ed effettivamente nessun problema, ma durante l'installazione ne è comparsa un'altra!
All'analisi con il debugger di questi 2 ultimi crash non risulta alcuna causa, questa è ciò che riporta l'analisi del file dump:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052110-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Fri May 21 19:39:57.484 2010 (UTC + 2:00)
System Uptime: 0 days 1:25:49.061
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {4, 2, 0, 804e6d3f}
Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+15c )
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
Risulta un "driver fault" ma ora a differenza di ieri non risulta alcuna file specifico.
Le schermate blu riportavano di pnf_list_corrupt 0x0000000A (le destinazioni si posso vedere dall'analisi del dump) e irql_not_less_or_equal 0x0000004e, ma da cosa diavolo derivano?
Non credo proprio si tratti di ram come ho letto in vari forum, sembra più un problema hardware/driver in conflitto.
Questo sono le caratteristiche del mio pc:
Scheda Madre : Non specificato SiS-648FX
Chipset : SiS 648FX
Processore : Intel Pentium 4 @ 2800 MHz
Memoria Fisica : 1024 MB (2 x 512 DDR-SDRAM )
Scheda Video : ATI Radeon 9550 / X1050 Series
Hard Disk : Maxtor (164 GB)
DVD-Rom Drive : HL-DT-ST DVD-RAM GSA-H58N
DVD-Rom Drive : HL-DT-ST DVD-ROM GDR8163B
Scheda di rete : SiS900 10/100 Ethernet Adapter
Sistema Operativo : Microsoft Windows XP Professional 5.01.2600 Service Pack 2
DirectX : Versione 9.0c
La scheda madre, PC Wizard non me la riconosce e sinceramente non so neanche quale sia, so solo che nel disco dei driver è presente come driver audio realtek 97 e nulla più.
Ho dato anche un'occhiata a questa discussione ma non mi è srevita a molto:
http://www.digital-forum.it/showthread.php?t=67237&page=2
Se ho dimenticato qualcosa che possa servire scrivetelo pure.
Vi ringrazio in anticipo.
Buona serata a tutti.
ieri sera, dopo aver formattato regolarmente, ho installato tutti i programmi necessari.
Per un po tutto ok, salvo che, all'improvviso mi compare una schermata blu di windows, che ho analizzato con il windows debugger e riporta ciò (stavo copiando sul mio pc una cartella di file abbastanza grande):
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Thu May 20 22:40:31.656 2010 (UTC + 2:00)
System Uptime: 0 days 0:13:49.228
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, fff08, 7, 0}
Probably caused by : memory_corruption ( nt!MiDeletePte+3e8 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 000fff08, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 805253ca to 805339ae
STACK_TEXT:
a6024b44 805253ca 0000004e 00000099 000fff08 nt!KeBugCheckEx+0x1b
a6024b84 804ec10e c0005040 01410000 00000000 nt!MiDeletePte+0x3e8
a6024c48 804f2d65 e1750e10 01410fff 00000000 nt!MiDeleteVirtualAddresses+0x162
a6024cf4 8057372e 85b9a538 85e66668 a6024d64 nt!MiRemoveMappedView+0x212
a6024d38 805737da 85aa91b0 85b8e3c0 00000000 nt!MiUnmapViewOfSection+0x12b
a6024d54 804df06b ffffffff 85b9a538 02b5e750 nt!NtUnmapViewOfSection+0x54
a6024d54 7c91eb94 ffffffff 85b9a538 02b5e750 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
02b5e750 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeletePte+3e8
805253ca e95e6bfdff jmp nt!MiDeletePte+0x400 (804fbf2d)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiDeletePte+3e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41108004
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+3e8
BUCKET_ID: 0x4E_99_nt!MiDeletePte+3e8
Followup: MachineOwner
---------
All'inizio sembrava che il problema fosse un caso isolato, e che il tutto derivasse da explorer.exe oppure ntoskrnl.exe: infatti alla prima anlisi del file dump senza i simboli scaricati da microsoft l'analisi riportava alla fine questa scritta "Probably caused by : ntoskrnl.exe ( nt+5c9ae )", ma appena scaricato tutto il problema sembrava derivare da explorer.exe (come si nota dall'analisi del file dump).
Il problema della schermata blu si è verificato nuovamente oggi 2 volte: la prima mentre ricopiavo quella maledetta cartella, allora ho pensato si potesse trattare dei driver della scheda video, una ati radeon 9550 serie x1050 da 256mb, in quanto al momento dell'installazione una schermata mi avvisava della probabile incompatibilità con il mio s.o. :la versione dei driver precedenti era catalyst 10.2, allora ho messo su la versione 7.8 (con relativo net. framework di windows 2.0 per il catalyst control center), dopodichè ho riprovato a copiare le cartelle ed effettivamente nessun problema, ma durante l'installazione ne è comparsa un'altra!
All'analisi con il debugger di questi 2 ultimi crash non risulta alcuna causa, questa è ciò che riporta l'analisi del file dump:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052110-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Fri May 21 19:39:57.484 2010 (UTC + 2:00)
System Uptime: 0 days 1:25:49.061
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {4, 2, 0, 804e6d3f}
Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+15c )
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804e6d3f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f58c4474 -- (.trap 0xfffffffff58c4474)
ErrCode = 00000000
eax=01171000 ebx=00001000 ecx=00001000 edx=fffff000 esi=01170000 edi=01171000
eip=80565fbc esp=f58c44e8 ebp=f58c44f0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ProbeForWrite+0x39:
80565fbc 8a06 mov al,byte ptr [esi] ds:0023:01170000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e6d3f to 804e2158
STACK_TEXT:
f58c4394 804e6d3f badb0d00 81053000 00000000 nt!KiTrap0E+0x233
f58c4424 80500ac1 01170000 01170000 f58c44f0 nt!MiRemovePageByColor+0x6a
f58c445c 804e1ff1 00000000 01170000 01000000 nt!MmAccessFault+0xa4c
f58c445c 80565fbc 00000000 01170000 01000000 nt!KiTrap0E+0xcc
f58c44f0 805694c8 01170000 00001000 00000001 nt!ProbeForWrite+0x39
f58c4558 8056974e 01170000 00001000 00000004 nt!MiSecureVirtualMemory+0x228
f58c4570 bf82d521 01170000 00001000 00000004 nt!MmSecureVirtualMemory+0x15
f58c45d8 804df06b 410108f2 00000000 00000000 win32k!NtGdiCreateDIBSection+0x15c
f58c45d8 7c91eb94 410108f2 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
011ef780 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtGdiCreateDIBSection+15c
bf82d521 8945c8 mov dword ptr [ebp-38h],eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: win32k!NtGdiCreateDIBSection+15c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a
FAILURE_BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
BUCKET_ID: 0xA_win32k!NtGdiCreateDIBSection+15c
Followup: MachineOwner
---------
Risulta un "driver fault" ma ora a differenza di ieri non risulta alcuna file specifico.
Le schermate blu riportavano di pnf_list_corrupt 0x0000000A (le destinazioni si posso vedere dall'analisi del dump) e irql_not_less_or_equal 0x0000004e, ma da cosa diavolo derivano?
Non credo proprio si tratti di ram come ho letto in vari forum, sembra più un problema hardware/driver in conflitto.
Questo sono le caratteristiche del mio pc:
Scheda Madre : Non specificato SiS-648FX
Chipset : SiS 648FX
Processore : Intel Pentium 4 @ 2800 MHz
Memoria Fisica : 1024 MB (2 x 512 DDR-SDRAM )
Scheda Video : ATI Radeon 9550 / X1050 Series
Hard Disk : Maxtor (164 GB)
DVD-Rom Drive : HL-DT-ST DVD-RAM GSA-H58N
DVD-Rom Drive : HL-DT-ST DVD-ROM GDR8163B
Scheda di rete : SiS900 10/100 Ethernet Adapter
Sistema Operativo : Microsoft Windows XP Professional 5.01.2600 Service Pack 2
DirectX : Versione 9.0c
La scheda madre, PC Wizard non me la riconosce e sinceramente non so neanche quale sia, so solo che nel disco dei driver è presente come driver audio realtek 97 e nulla più.
Ho dato anche un'occhiata a questa discussione ma non mi è srevita a molto:
http://www.digital-forum.it/showthread.php?t=67237&page=2
Se ho dimenticato qualcosa che possa servire scrivetelo pure.
Vi ringrazio in anticipo.
Buona serata a tutti.
Nel caso riscontrassi ancora problemi fai quello che ti ho detto in precedenza; se tutto filasse liscio invece reinstalla tutti i driver che hai nel cd della scheda madre (se possibile aggiorna anche il bios di quest' ultima) e tutti i driver delle periferiche che hai collegate, aggiorna le direct x alla versione più recente "supportata" dal tuo So (9.0 c) e come detto aggiorna al service pack 3 di Windows...lascia perdere quello che leggi in rete...Windows a breve cesserà il supporto al SP2 di Xp, e cosa ancor più grave il Service Pack 2 è facilmente "vulnerabile" a possibili "infiltrazioni"...uno degli ultimi "virus" con cui ho avuto a che fare si "annidava" addiritura tra gli "aggiornamenti" di Windows, o meglio faceva credere quello...