Crash improvviso

[mrk1988]

Salve a tutti,

Premetto che ho cercato nel forum per vedere se c'era già un post che ricalcava il mio problema, ma non l'ho trovato. Se per caso mi fosse sfuggito vi prego di linkarmelo.

Ho un PC portartile Asus con schermo multi touch, equipaggiato con Windows 7 Home edition, che in maniera casuale va in blocco generando la classica schermata blu e generando il file DUMP. Quello che vi chiedo è:

Dove si trova il file dump generato?
Come posso fare a risalire tramite il file dump all'applicazione o al driver che mi hanno mandato in crasch il PC
è possibile analizzare il file dump da un altro PC?


In attesa di una vostra risposta vi faccio i miei più cordiali saluti

[Eress]

http://www.hwupgrade.it/forum/showthread.php?t=1955371

[mrk1988]

Grazie mille per avermi segnalato il link.

Eseguendo il procedimento descritto nella guida ottengo il seguente risultato:


Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Programmi\DUMP FILE\073112-20592-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03050670
Debug session time: Sun Jul 29 17:53:49.202 2012 (UTC + 2:00)
System Uptime: 0 days 0:24:32.200
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff8800589fc8b}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : NETw5s64.sys ( NETw5s64+fc8b )

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


Secondo voi è giusto? oppure ho sbagliato a scaricare i symbols per il mio PC? Cosa è il file NETw5s64.sys?

[Eress]

Problemi di simboli mal caricati, utilizza il tool alternativo segnalato nel post

[mrk1988]

Scusate se rispondo solo adesso, ma ho avuto dei grossi problemi con l'ADSL.

Il codice d'errore che mi da il PC è il seguente:
DRIVER_IRQL_NOT_LESS_OR_EQUAL stop 0x000000D1(0x0000000000000000,0x0000000000000002,0x0000000000000000,0xFFFFF88004025C8B)

cosa vuol dire? ho postato il codice sul supporto tecnico di Microsoft, come è scritto nella guida, ma non mi da alcun risultato.

[Blue_screen_of_death]

Vuol dire che hai qualche driver nel PC che fa i capricci...

Per capire di che driver si tratta devi caricare i simboli giusti nel windows debugging tool oppure in alternativa puoi usare il programmino blue screen view

[Eress]

C'è un problema con qualche driver, oppure hw. Fai anche un test alla ram, usa il pc con un solo banco di ram collegato per volta

[mrk1988]

Pero ora ho provato con a leggere il file dump con Blue screen of Death, e come risposta mi ha dato la seguete lista:

Nome del File Indirizzo nello Stack Dall'Indirizzo All'indirizzo Dimensione Time Stamp Time String Nome Prodotto Descrizione del File Versione del File Società Path Completo
NETw5s64.sys NETw5s64.sys+fc8b fffff880`058b9000 fffff880`05f66000 0x006ad000 0x4aafedb7 15/09/2009 21:40:39
ntoskrnl.exe ntoskrnl.exe+7e769 fffff800`02e05000 fffff800`033ed000 0x005e8000 0x4fa390f3 04/05/2012 10:18:59 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17835 (win7sp1_gdr.120503-2030) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
hal.dll fffff800`033ed000 fffff800`03436000 0x00049000 0x4ce7c669 20/11/2010 15:00:25
kdcom.dll fffff800`00ba3000 fffff800`00bad000 0x0000a000 0x4d4d8061 05/02/2011 18:52:49
mcupdate_GenuineIntel.dll fffff880`00c29000 fffff880`00c78000 0x0004f000 0x4ce7c737 20/11/2010 15:03:51
PSHED.dll fffff880`00c78000 fffff880`00c8c000 0x00014000 0x4a5be027 14/07/2009 03:32:23 Sistema operativo Microsoft® Windows® Driver errori hardware specifici di piattaforma 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll
CLFS.SYS fffff880`00c8c000 fffff880`00cea000 0x0005e000 0x4a5bc11d 14/07/2009 01:19:57
CI.dll fffff880`00cea000 fffff880`00daa000 0x000c0000 0x4ce7c944 20/11/2010 15:12:36
Wdf01000.sys fffff880`00e86000 fffff880`00f2a000 0x000a4000 0x4a5bc19f 14/07/2009 01:22:07
WDFLDR.SYS fffff880`00f2a000 fffff880`00f39000 0x0000f000 0x4a5bc11a 14/07/2009 01:19:54
ACPI.sys fffff880`00f39000 fffff880`00f90000 0x00057000 0x4ce79294 20/11/2010 11:19:16
WMILIB.SYS fffff880`00f90000 fffff880`00f99000 0x00009000 0x4a5bc117 14/07/2009 01:19:51
msisadrv.sys fffff880`00f99000 fffff880`00fa3000 0x0000a000 0x4a5bc0fe 14/07/2009 01:19:26
pci.sys fffff880`00fa3000 fffff880`00fd6000 0x00033000 0x4ce7928f 20/11/2010 11:19:11
vdrvroot.sys fffff880`00fd6000 fffff880`00fe3000 0x0000d000 0x4a5bcadb 14/07/2009 02:01:31
partmgr.sys fffff880`00fe3000 fffff880`00ff8000 0x00015000 0x4f641bc1 17/03/2012 07:06:09
compbatt.sys fffff880`00e00000 fffff880`00e09000 0x00009000 0x4a5bc3b6 14/07/2009 01:31:02
BATTC.SYS fffff880`00e09000 fffff880`00e15000 0x0000c000 0x4a5bc3b5 14/07/2009 01:31:01
volmgr.sys fffff880`00e15000 fffff880`00e2a000 0x00015000 0x4ce792a0 20/11/2010 11:19:28
volmgrx.sys fffff880`00e2a000 fffff880`00e86000 0x0005c000 0x4ce792eb 20/11/2010 11:20:43
mountmgr.sys fffff880`00daa000 fffff880`00dc4000 0x0001a000 0x4ce79299 20/11/2010 11:19:21
iaStor.sys fffff880`010c9000 fffff880`011e5000 0x0011c000 0x4ad4c3dc 13/10/2009 20:15:56
atapi.sys fffff880`011e5000 fffff880`011ee000 0x00009000 0x4a5bc113 14/07/2009 01:19:47
ataport.SYS fffff880`01000000 fffff880`0102a000 0x0002a000 0x4ce79293 20/11/2010 11:19:15
amdxata.sys fffff880`0102a000 fffff880`01035000 0x0000b000 0x4ba3a3ca 19/03/2010 18:18:18
fltmgr.sys fffff880`01035000 fffff880`01081000 0x0004c000 0x4ce7929c 20/11/2010 11:19:24
fileinfo.sys fffff880`01081000 fffff880`01095000 0x00014000 0x4a5bc481 14/07/2009 01:34:25
Ntfs.sys fffff880`01214000 fffff880`013b7000 0x001a3000 0x4d79997b 11/03/2011 05:39:39
msrpc.sys fffff880`01446000 fffff880`014a4000 0x0005e000 0x4ce79334 20/11/2010 11:21:56
ksecdd.sys fffff880`014a4000 fffff880`014bf000 0x0001b000 0x4fc97f6f 02/06/2012 04:50:23
cng.sys fffff880`014bf000 fffff880`01531000 0x00072000 0x4fc987bf 02/06/2012 05:25:51
pcw.sys fffff880`01531000 fffff880`01542000 0x00011000 0x4a5bc0ff 14/07/2009 01:19:27
Fs_Rec.sys fffff880`01542000 fffff880`0154c000 0x0000a000 0x4f4eefd2 01/03/2012 05:41:06
ndis.sys fffff880`01622000 fffff880`01715000 0x000f3000 0x4ce79392 20/11/2010 11:23:30
NETIO.SYS fffff880`01715000 fffff880`01775000 0x00060000 0x4ce79381 20/11/2010 11:23:13
ksecpkg.sys fffff880`01775000 fffff880`0179f000 0x0002a000 0x4fc9880f 02/06/2012 05:27:11
tcpip.sys fffff880`01834000 fffff880`01a37000 0x00203000 0x4f757012 30/03/2012 10:34:26
fwpkclnt.sys fffff880`01a37000 fffff880`01a81000 0x0004a000 0x4ce79321 20/11/2010 11:21:37
volsnap.sys fffff880`01a81000 fffff880`01acd000 0x0004c000 0x4ce792c8 20/11/2010 11:20:08
spldr.sys fffff880`01acd000 fffff880`01ad5000 0x00008000 0x4a0858bb 11/05/2009 18:56:27
rdyboost.sys fffff880`01ad5000 fffff880`01b0f000 0x0003a000 0x4ce7982e 20/11/2010 11:43:10
mup.sys fffff880`01b0f000 fffff880`01b21000 0x00012000 0x4a5bc201 14/07/2009 01:23:45
hwpolicy.sys fffff880`01b21000 fffff880`01b2a000 0x00009000 0x4ce7927e 20/11/2010 11:18:54
fvevol.sys fffff880`01b2a000 fffff880`01b64000 0x0003a000 0x4ce793b6 20/11/2010 11:24:06
disk.sys fffff880`01b64000 fffff880`01b7a000 0x00016000 0x4a5bc11d 14/07/2009 01:19:57
CLASSPNP.SYS fffff880`01b7a000 fffff880`01baa000 0x00030000 0x4ce7929b 20/11/2010 11:19:23
mwlPSDFilter.sys fffff880`02f99000 fffff880`02fa2000 0x00009000 0x4a24f9e2 02/06/2009 12:07:30
Null.SYS fffff880`02fa2000 fffff880`02fab000 0x00009000 0x4a5bc109 14/07/2009 01:19:37
Beep.SYS fffff880`02fab000 fffff880`02fb2000 0x00007000 0x4a5bca8d 14/07/2009 02:00:13
ehdrv.sys fffff880`02fb2000 fffff880`02fd7000 0x00025000 0x4d006956 09/12/2010 07:29:58
vga.sys fffff880`02fd7000 fffff880`02fe5000 0x0000e000 0x4a5bc587 14/07/2009 01:38:47
VIDEOPRT.SYS fffff880`02e00000 fffff880`02e25000 0x00025000 0x4a5bc58b 14/07/2009 01:38:51
watchdog.sys fffff880`02e25000 fffff880`02e35000 0x00010000 0x4a5bc53f 14/07/2009 01:37:35
RDPCDD.sys fffff880`02e35000 fffff880`02e3e000 0x00009000 0x4a5bce62 14/07/2009 02:16:34
rdpencdd.sys fffff880`02f6f000 fffff880`02f78000 0x00009000 0x4a5bce62 14/07/2009 02:16:34
rdprefmp.sys fffff880`02f78000 fffff880`02f81000 0x00009000 0x4a5bce63 14/07/2009 02:16:35
Msfs.SYS fffff880`02f81000 fffff880`02f8c000 0x0000b000 0x4a5bc113 14/07/2009 01:19:47
Npfs.SYS fffff880`02fe5000 fffff880`02ff6000 0x00011000 0x4a5bc114 14/07/2009 01:19:48
tdx.sys fffff880`01bb8000 fffff880`01bda000 0x00022000 0x4ce79332 20/11/2010 11:21:54
TDI.SYS fffff880`02f8c000 fffff880`02f99000 0x0000d000 0x4ce7933e 20/11/2010 11:22:06
afd.sys fffff880`0154c000 fffff880`015d5000 0x00089000 0x4efa9418 28/12/2011 05:59:20
netbt.sys fffff880`0179f000 fffff880`017e4000 0x00045000 0x4ce79386 20/11/2010 11:23:18
wfplwf.sys fffff880`02ff6000 fffff880`02fff000 0x00009000 0x4a5bccb6 14/07/2009 02:09:26
pacer.sys fffff880`01bda000 fffff880`01c00000 0x00026000 0x4ce7a862 20/11/2010 12:52:18
vwififlt.sys fffff880`01800000 fffff880`01816000 0x00016000 0x4a5bcc3a 14/07/2009 02:07:22
netbios.sys fffff880`01816000 fffff880`01825000 0x0000f000 0x4a5bccb6 14/07/2009 02:09:26
wanarp.sys fffff880`017e4000 fffff880`017ff000 0x0001b000 0x4ce7a874 20/11/2010 12:52:36
termdd.sys fffff880`01600000 fffff880`01614000 0x00014000 0x4ce7ab0c 20/11/2010 13:03:40
rdbss.sys fffff880`03ea8000 fffff880`03ef9000 0x00051000 0x4ce79497 20/11/2010 11:27:51
nsiproxy.sys fffff880`03ef9000 fffff880`03f05000 0x0000c000 0x4a5bc15e 14/07/2009 01:21:02
mwlPSDVDisk.sys fffff880`03f05000 fffff880`03f18000 0x00013000 0x4a24fbc1 02/06/2009 12:15:29
mwlPSDNServ.sys fffff880`03f18000 fffff880`03f20000 0x00008000 0x4a24f9eb 02/06/2009 12:07:39
mssmbios.sys fffff880`03f20000 fffff880`03f2b000 0x0000b000 0x4a5bc3be 14/07/2009 01:31:10
ElbyCDIO.sys fffff880`03f2b000 fffff880`03f37000 0x0000c000 0x4d0a9985 17/12/2010 00:58:13
discache.sys fffff880`03f37000 fffff880`03f46000 0x0000f000 0x4a5bc52e 14/07/2009 01:37:18
dfsc.sys fffff880`03f46000 fffff880`03f64000 0x0001e000 0x4ce79447 20/11/2010 11:26:31
blbdrive.sys fffff880`03f64000 fffff880`03f75000 0x00011000 0x4a5bc4df 14/07/2009 01:35:59
tunnel.sys fffff880`03f75000 fffff880`03f9b000 0x00026000 0x4ce7a846 20/11/2010 12:51:50
intelppm.sys fffff880`03f9b000 fffff880`03fb1000 0x00016000 0x4a5bc0fd 14/07/2009 01:19:25
CmBatt.sys fffff880`03fb1000 fffff880`03fb5500 0x00004500 0x4a5bc3b7 14/07/2009 01:31:03
igdkmd64.sys fffff880`04af4000 fffff880`05516e20 0x00a22e20 0x4d558b10 11/02/2011 21:16:32
dxgkrnl.sys fffff880`04a00000 fffff880`04af4000 0x000f4000 0x4ce799fa 20/11/2010 11:50:50
dxgmms1.sys fffff880`05517000 fffff880`0555d000 0x00046000 0x4ce799c1 20/11/2010 11:49:53
usbuhci.sys fffff880`0555d000 fffff880`0556a000 0x0000d000 0x4d8c0bff 25/03/2011 05:29:03
USBPORT.SYS fffff880`0556a000 fffff880`055c0000 0x00056000 0x4d8c0c08 25/03/2011 05:29:12
usbehci.sys fffff880`055c0000 fffff880`055d1000 0x00011000 0x4d8c0c00 25/03/2011 05:29:04
HDAudBus.sys fffff880`055d1000 fffff880`055f5000 0x00024000 0x4ce7a65e 20/11/2010 12:43:42
L1C62x64.sys fffff880`03fb6000 fffff880`03fc9000 0x00013000 0x4aa0a7fd 04/09/2009 07:39:09
vwifibus.sys fffff880`05f66000 fffff880`05f73000 0x0000d000 0x4a5bcc39 14/07/2009 02:07:21
i8042prt.sys fffff880`05f73000 fffff880`05f91000 0x0001e000 0x4a5bc11d 14/07/2009 01:19:57
DKbFltr.sys fffff880`05f91000 fffff880`05f9d000 0x0000c000 0x49caf35e 26/03/2009 05:15:42 Dritek 64-bit PS/2 Keyboard Filter Driver Dritek 64-bit PS/2 Keyboard Filter Driver 2, 1, 1, 218 Dritek System Inc. C:\Windows\system32\drivers\DKbFltr.sys
kbdclass.sys fffff880`05f9d000 fffff880`05fac000 0x0000f000 0x4a5bc116 14/07/2009 01:19:50
SynTP.sys fffff880`05fac000 fffff880`05ff9000 0x0004d000 0x4ab2f0d1 18/09/2009 04:30:41
USBD.SYS fffff880`05ff9000 fffff880`05ffaf00 0x00001f00 0x4d8c0bfb 25/03/2011 05:28:59
mouclass.sys fffff880`05800000 fffff880`0580f000 0x0000f000 0x4a5bc116 14/07/2009 01:19:50
STHall.sys fffff880`0580f000 fffff880`05818000 0x00009000 0x4a8c60f0 19/08/2009 22:30:40
wmiacpi.sys fffff880`05818000 fffff880`05821000 0x00009000 0x4a5bc3b6 14/07/2009 01:31:02
CompositeBus.sys fffff880`05821000 fffff880`05831000 0x00010000 0x4ce7a3ed 20/11/2010 12:33:17
mvvideodemo.sys fffff880`05831000 fffff880`05839000 0x00008000 0x4d9cc282 06/04/2011 21:44:02
HWDrawing.sys fffff880`05839000 fffff880`0583b080 0x00002080 0x46081c2b 26/03/2007 21:16:59
HIDCLASS.SYS fffff880`0583c000 fffff880`05855000 0x00019000 0x4ce7a665 20/11/2010 12:43:49
HIDPARSE.SYS fffff880`05855000 fffff880`0585d080 0x00008080 0x4a5bcbf9 14/07/2009 02:06:17
vcsvad.sys fffff880`0585e000 fffff880`05868000 0x0000a000 0x491fed16 16/11/2008 11:51:18
portcls.sys fffff880`05868000 fffff880`058a5000 0x0003d000 0x4a5bcc03 14/07/2009 02:06:27
drmk.sys fffff880`03fc9000 fffff880`03feb000 0x00022000 0x4a5bd8e5 14/07/2009 03:01:25
ks.sys fffff880`03e00000 fffff880`03e43000 0x00043000 0x4ce7a3f3 20/11/2010 12:33:23
ksthunk.sys fffff880`058a5000 fffff880`058aa200 0x00005200 0x4a5bca93 14/07/2009 02:00:19
AgileVpn.sys fffff880`03e43000 fffff880`03e59000 0x00016000 0x4a5bccf0 14/07/2009 02:10:24
rasl2tp.sys fffff880`03e59000 fffff880`03e7d000 0x00024000 0x4ce7a872 20/11/2010 12:52:34
ndistapi.sys fffff880`058ab000 fffff880`058b7000 0x0000c000 0x4a5bccd8 14/07/2009 02:10:00
ndiswan.sys fffff880`01400000 fffff880`0142f000 0x0002f000 0x4ce7a870 20/11/2010 12:52:32
raspppoe.sys fffff880`03e7d000 fffff880`03e98000 0x0001b000 0x4a5bcce9 14/07/2009 02:10:17
raspptp.sys fffff880`015d5000 fffff880`015f6000 0x00021000 0x4ce7a86f 20/11/2010 12:52:31
rassstp.sys fffff880`013b7000 fffff880`013d1000 0x0001a000 0x4a5bccf1 14/07/2009 02:10:25
VClone.sys fffff880`03e98000 fffff880`03ea7000 0x0000f000 0x4d31c970 15/01/2011 18:21:04
SCSIPORT.SYS fffff880`013d1000 fffff880`01400000 0x0002f000 0x4ce7a419 20/11/2010 12:34:01
swenum.sys fffff880`058b7000 fffff880`058b8480 0x00001480 0x4a5bca92 14/07/2009 02:00:18
vdbus.sys fffff880`03ca6000 fffff880`03d50000 0x000aa000 0x4ea640e0 25/10/2011 06:53:52
umbus.sys fffff880`03d50000 fffff880`03d62000 0x00012000 0x4ce7a695 20/11/2010 12:44:37
bpenum.sys fffff880`03d62000 fffff880`03d99000 0x00037000 0x4a71382e 30/07/2009 08:05:34
usbhub.sys fffff880`03d99000 fffff880`03df3000 0x0005a000 0x4d8c0c15 25/03/2011 05:29:25
mouhid.sys fffff880`03df3000 fffff880`03e00000 0x0000d000 0x4a5bca94 14/07/2009 02:00:20
NDProxy.SYS fffff880`03c00000 fffff880`03c15000 0x00015000 0x4ce7a864 20/11/2010 12:52:20
RTKVHD64.sys fffff880`07a11000 fffff880`07c39f80 0x00228f80 0x4b824db0 22/02/2010 11:26:08
IntcHdmi.sys fffff880`07c3a000 fffff880`07c61000 0x00027000 0x4a5745e6 10/07/2009 15:45:10
UBHelper.sys fffff880`07c61000 fffff880`07c69000 0x00008000 0x49f57153 27/04/2009 10:48:19
cdrom.sys fffff880`07c69000 fffff880`07c93000 0x0002a000 0x4ce79298 20/11/2010 11:19:20
NTIDrvr.sys fffff880`07c93000 fffff880`07c9b000 0x00008000 0x49c9a073 25/03/2009 05:09:39
crashdmp.sys fffff880`07c9b000 fffff880`07ca9000 0x0000e000 0x4a5bcabd 14/07/2009 02:01:01
dump_iaStor.sys fffff880`07ca9000 fffff880`07dc5000 0x0011c000 0x4ad4c3dc 13/10/2009 20:15:56
dump_dumpfve.sys fffff880`07dc5000 fffff880`07dd8000 0x00013000 0x4a5bc18f 14/07/2009 01:21:51
usbccgp.sys fffff880`07dd8000 fffff880`07df5000 0x0001d000 0x4d8c0c0a 25/03/2011 05:29:14
win32k.sys fffff960`000d0000 fffff960`003e5000 0x00315000 0x00000000
Dxapi.sys fffff880`07a00000 fffff880`07a0c000 0x0000c000 0x4a5bc574 14/07/2009 01:38:28
snp2uvc.sys fffff880`0221a000 fffff880`023d1b80 0x001b7b80 0x4aa8d533 10/09/2009 12:30:11
STREAM.SYS fffff880`023d2000 fffff880`023e2d00 0x00010d00 0x4a5bcbfa 14/07/2009 02:06:18
sncduvc.SYS fffff880`023e3000 fffff880`023eba80 0x00008a80 0x495894f2 29/12/2008 11:14:26
monitor.sys fffff880`023ec000 fffff880`023fa000 0x0000e000 0x4a5bc58c 14/07/2009 01:38:52
TSDDD.dll fffff960`00410000 fffff960`0041a000 0x0000a000 0x00000000
hidusb.sys fffff880`02200000 fffff880`0220e000 0x0000e000 0x4ce7a665 20/11/2010 12:43:49
cdd.dll fffff960`00760000 fffff960`00787000 0x00027000 0x00000000
luafv.sys fffff880`03c15000 fffff880`03c38000 0x00023000 0x4a5bc295 14/07/2009 01:26:13
eamonm.sys fffff880`02e3e000 fffff880`02f17000 0x000d9000 0x4d006930 09/12/2010 07:29:20
WudfPf.sys fffff880`03c38000 fffff880`03c59000 0x00021000 0x4ce7a624 20/11/2010 12:42:44
lltdio.sys fffff880`03c59000 fffff880`03c6e000 0x00015000 0x4a5bcc92 14/07/2009 02:08:50
nwifi.sys fffff880`02f17000 fffff880`02f6a000 0x00053000 0x4a5bcc3b 14/07/2009 02:07:23
ndisuio.sys fffff880`03c6e000 fffff880`03c81000 0x00013000 0x4ce7a7e0 20/11/2010 12:50:08
rspndr.sys fffff880`03c81000 fffff880`03c99000 0x00018000 0x4a5bcc92 14/07/2009 02:08:50
HTTP.sys fffff880`02a51000 fffff880`02b1a000 0x000c9000 0x4ce793ce 20/11/2010 11:24:30
bowser.sys fffff880`02b1a000 fffff880`02b38000 0x0001e000 0x4d649328 23/02/2011 06:55:04
mpsdrv.sys fffff880`02b38000 fffff880`02b50000 0x00018000 0x4a5bcc79 14/07/2009 02:08:25
mrxsmb.sys fffff880`02b50000 fffff880`02b7d000 0x0002d000 0x4db78226 27/04/2011 04:40:38
mrxsmb10.sys fffff880`02b7d000 fffff880`02bcb000 0x0004e000 0x4e17c104 09/07/2011 04:46:28
mrxsmb20.sys fffff880`02bcb000 fffff880`02bef000 0x00024000 0x4db781e9 27/04/2011 04:39:37
epfwwfpr.sys fffff880`02a00000 fffff880`02a21000 0x00021000 0x4d006871 09/12/2010 07:26:09
vwifimp.sys fffff880`02a21000 fffff880`02a2b000 0x0000a000 0x4a5bcc40 14/07/2009 02:07:28
mvCmdemo.SYS fffff880`02a2b000 fffff880`02a33000 0x00008000 0x4d9cc283 06/04/2011 21:44:03
peauth.sys fffff880`07eaf000 fffff880`07f55000 0x000a6000 0x4a5bd8df 14/07/2009 03:01:19
secdrv.SYS fffff880`07f55000 fffff880`07f60000 0x0000b000 0x4508052e 13/09/2006 15:18:38
srvnet.sys fffff880`07f60000 fffff880`07f91000 0x00031000 0x4dba2aff 29/04/2011 05:05:35
tcpipreg.sys fffff880`07f91000 fffff880`07fa3000 0x00012000 0x4ce7a844 20/11/2010 12:51:48
srv2.sys fffff880`07e00000 fffff880`07e69000 0x00069000 0x4dba2b0a 29/04/2011 05:05:46
srv.sys fffff880`086b2000 fffff880`0874a000 0x00098000 0x4dba2b1e 29/04/2011 05:06:06
asyncmac.sys fffff880`0874a000 fffff880`08755000 0x0000b000 0x4a5bcce5 14/07/2009 02:10:13

Cosa vuol dire, che tutti questi drive sono incriminati? cmq ora provo anche a fare un test delle RAM

[Blue_screen_of_death]

no, il driver incriminato dovrebbe essere il primo , quindi netw5s64.sys

Questo è un driver Wifi , quindi per cominciare aggiorna i driver della scheda wireless

[mrk1988]

Grazie per il consiglio, provo subito ad aggiornare il driver della scheda di rete. E poi ho appena fatto un test delle RAM con MemTest, che non ha trovato alcun errore.

[mrk1988]

:cincin:Perfetto, Grazie per i vostri consigli, ho aggiornato i driver della scheda wifi e per adesso non mi si è più crasciato