PROBLEMA page fault in non paged area

Pubblicità
Stato
Discussione chiusa ad ulteriori risposte.
Allora, riguardo ai driver non significa nulla il punto interrogativo giallo perché Windows dispone di driver base che ti fa funzionare il OS. Dovresti provare un software tipo Driver navigator per vedere come sei messo. Poi se nel bios hai provato il profilo xmp per la ram, stai certo che ha impostato correttamente anche i tempi. Comunque ti consiglio di fare un reset bios per vedere se il problema persiste.

Problema apparentemente risolto. Prima ho usato driver navigator per vedere cosa mancava :
-alcuni driver intel ( anche se l' utility della intel mi diceva che erano tutti giusti )
-driver realtek

Ho aggiornato i driver realtek , poi sono andato nel bios e ho impostato tutte le frequenze in auto .

Oggi ho fatto diverse sessioni di gioco di BF3 , MGS1 e ho provato a vedere se mi funzionava bioshock. nessuno di questi giochi mi ha dato problemi (cosa che prima facevano , con crash , BSOD , e bioshock addirittura non partiva ) .

Ringrazio tutti per il supporto , soprattutto CristianB che mi ha guidato :,) . Spero non si presentino più problemi.

- - - Updated - - -
 
Problema apparentemente risolto. Prima ho usato driver navigator per vedere cosa mancava :
-alcuni driver intel ( anche se l' utility della intel mi diceva che erano tutti giusti )
-driver realtek

Ho aggiornato i driver realtek , poi sono andato nel bios e ho impostato tutte le frequenze in auto .

Oggi ho fatto diverse sessioni di gioco di BF3 , MGS1 e ho provato a vedere se mi funzionava bioshock. nessuno di questi giochi mi ha dato problemi (cosa che prima facevano , con crash , BSOD , e bioshock addirittura non partiva ) .

Ringrazio tutti per il supporto , soprattutto CristianB che mi ha guidato :,) . Spero non si presentino più problemi.



Ok perfetto, mi fa piacere per te.
 
il problema è tornato , prima era qualcosa di sporadico , ma oggi mi è crashato circa 8 volte dopo un po di ore che giocavo a minecraft ; . Vedendo la situazione ho reinstallato tutti i driver che mi diceva il sito di asrock e poi ho scaricato driver easy e ho scaricato pure quelli che mi diceva mancavano .

L' unica cosa strana è che mi segnala che mancano i driver realtek , quando avevo installato quelli( sempre realtek ) che mi proponeva il sito della asrock, più volte. Ho windows 8.1 pro N crackato

Qui vi riporto tutti gli errori di whocrashed:

[FONT=Segoe UI, Arial]On Tue 29/12/2015 18:32:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-3875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF802D36606E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 18:32:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF802D36606E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 18:25:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-4109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]srvnet.sys[/FONT] (0xFFFFF801C0E739B7)
Bugcheck code: 0x50 (0xFFFFD000FA33F6B0, 0x1, 0xFFFFF801C0E739B7, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\srvnet.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Server Network driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 17:20:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-4031-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x125C2A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803F9B2EC2A, 0xFFFFD000216F73E8, 0xFFFFD000216F6BF0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 17:08:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-4171-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF803914676E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 16:59:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-3953-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF803FD05C6E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 16:28:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-3953-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x125C2A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801D432FC2A, 0xFFFFD001670F73E8, 0xFFFFD001670F6BF0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 28/12/2015 19:02:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-3875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD000C769F5D8, 0xFFFFD000C769EDE0, 0xFFFFF8004B74A6C8)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 28/12/2015 16:49:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-4531-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFC0884B8, 0x400000000000, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 22/12/2015 19:40:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122215-3562-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
 
Allora per i driver Realtek, dal sito Asrock non penso ci siano gli ultimissimi aggiornamenti, perciò il software li identifica, ma questo non è un problema. Io ti consiglio se non l'hai ancora fatto, di fare un reset Bios poi provare a vedere, altrimenti formatta così pulisci tutto, perché ho l'impressione che il sistema sia corrotto.
 
ah , mi son dimenticato di aggiungere che ho sempre windows in modalità test . Può indicare qualcosa di rilevante o è solo dovuto a certi driver?
 
il problema è tornato , prima era qualcosa di sporadico , ma oggi mi è crashato circa 8 volte dopo un po di ore che giocavo a minecraft ; . Vedendo la situazione ho reinstallato tutti i driver che mi diceva il sito di asrock e poi ho scaricato driver easy e ho scaricato pure quelli che mi diceva mancavano .

L' unica cosa strana è che mi segnala che mancano i driver realtek , quando avevo installato quelli( sempre realtek ) che mi proponeva il sito della asrock, più volte. Ho windows 8.1 pro N crackato

Qui vi riporto tutti gli errori di whocrashed:

[FONT=Segoe UI, Arial]On Tue 29/12/2015 18:32:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-3875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF802D36606E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 18:32:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF802D36606E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 18:25:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-4109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]srvnet.sys[/FONT] (0xFFFFF801C0E739B7)
Bugcheck code: 0x50 (0xFFFFD000FA33F6B0, 0x1, 0xFFFFF801C0E739B7, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\srvnet.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Server Network driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 17:20:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-4031-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x125C2A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803F9B2EC2A, 0xFFFFD000216F73E8, 0xFFFFD000216F6BF0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 17:08:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-4171-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF803914676E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 16:59:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-3953-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFB0, 0x2, 0x1, 0xFFFFF803FD05C6E2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/12/2015 16:28:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-3953-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x125C2A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801D432FC2A, 0xFFFFD001670F73E8, 0xFFFFD001670F6BF0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 28/12/2015 19:02:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-3875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD000C769F5D8, 0xFFFFD000C769EDE0, 0xFFFFF8004B74A6C8)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 28/12/2015 16:49:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-4531-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFC0884B8, 0x400000000000, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 22/12/2015 19:40:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122215-3562-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E8A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]
non diamo supporto a sistemi operativi craccati arrangiati!!!
 
Stato
Discussione chiusa ad ulteriori risposte.
Pubblicità
Pubblicità
Indietro
Top