RISOLTO Problema Bsod casuali e sempre diversi

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Salve,
avrei bisogno di aiuto su un problemino ma parto dall'inizio. Il mio pc ha un anno i primi 6 mesi non ho mai avuto un problema dopo ciò ho cominciato ad avere sempre più frequentemente dei BSOD ma ogni volta sempre diversi cioè alcuni di questi sono PAGE_FAULT_IN_NONPAGED_AREA,SYSTEM_SERVICE_EXCEPTION,DRIVER_IRQL_NOT_LESS_OR_EQUAL ho provato a fare dei test alla ram com memtest64 e in 2 ore di test ha trovato 0 errori inoltre qualche giorno fa ho anche fatto un'installazione clean di windows 10. Vi copio l'analisi dei file Dump da parte di WhoCrashed

On Thu 25/02/2021 22:21:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-7000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xFC (0xFFFFF8067B9A9300, 0x8000000177DE9929, 0xFFFFFC8D7B9AA1A0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/02/2021 22:21:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x68C70)
Bugcheck code: 0xFC (0xFFFFF8067B9A9300, 0x8000000177DE9929, 0xFFFFFC8D7B9AA1A0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/02/2021 21:58:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-17359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xE6 (0xF, 0x3, 0xFFFFDC0585AFCD90, 0x0)
Error: DRIVER_VERIFIER_DMA_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the bug check code for all Driver Verifier
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.



On Thu 25/02/2021 21:51:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-11671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x50 (0xFFFFC7022BE6BE98, 0x2, 0xFFFFF8063253BECE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/02/2021 16:57:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8012DE28378, 0xFFFFFA0EC8747B50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Thu 25/02/2021 16:30:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xD1 (0x0, 0x8, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

meangela

Utente Attivo
277
22
Problema di ram e alimentazione prova a mettere prestazioni elevate e aggiornare i driver da Windows update o li scarichi dai siti del tuo hardware
 

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
Salve,
avrei bisogno di aiuto su un problemino ma parto dall'inizio. Il mio pc ha un anno i primi 6 mesi non ho mai avuto un problema dopo ciò ho cominciato ad avere sempre più frequentemente dei BSOD ma ogni volta sempre diversi cioè alcuni di questi sono PAGE_FAULT_IN_NONPAGED_AREA,SYSTEM_SERVICE_EXCEPTION,DRIVER_IRQL_NOT_LESS_OR_EQUAL ho provato a fare dei test alla ram com memtest64 e in 2 ore di test ha trovato 0 errori inoltre qualche giorno fa ho anche fatto un'installazione clean di windows 10. Vi copio l'analisi dei file Dump da parte di WhoCrashed

On Thu 25/02/2021 22:21:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-7000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xFC (0xFFFFF8067B9A9300, 0x8000000177DE9929, 0xFFFFFC8D7B9AA1A0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/02/2021 22:21:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x68C70)
Bugcheck code: 0xFC (0xFFFFF8067B9A9300, 0x8000000177DE9929, 0xFFFFFC8D7B9AA1A0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/02/2021 21:58:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-17359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xE6 (0xF, 0x3, 0xFFFFDC0585AFCD90, 0x0)
Error: DRIVER_VERIFIER_DMA_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the bug check code for all Driver Verifier
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.



On Thu 25/02/2021 21:51:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-11671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x50 (0xFFFFC7022BE6BE98, 0x2, 0xFFFFF8063253BECE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/02/2021 16:57:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8012DE28378, 0xFFFFFA0EC8747B50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Thu 25/02/2021 16:30:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xD1 (0x0, 0x8, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Hai attivato xmp nel bios? I banchi di ram sono installati nel 2° e 4° slot a partire da sinistra??
 

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Comunque Ram e Alimentatore testati e non sembrano esser quelli,allego lo screen di memtest64.Driver tutti aggiornati facendo il check uno per uno. Si le slot ram sono nella seconda e quarta slot,per dire quelle rosse nella mia mobo non quelle nere,xmp lo avevo attivato ora sto provando avendolo disattivato e frequenza ram stock vediamo come va comunque in generale questo mi succede con carichi relativamente "pesanti" altrimenti il pc va che una meraviglia.
Screenshot (39).png
 

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
Comunque Ram e Alimentatore testati e non sembrano esser quelli,allego lo screen di memtest64.Driver tutti aggiornati facendo il check uno per uno. Si le slot ram sono nella seconda e quarta slot,per dire quelle rosse nella mia mobo non quelle nere,xmp lo avevo attivato ora sto provando avendolo disattivato e frequenza ram stock vediamo come va comunque in generale questo mi succede con carichi relativamente "pesanti" altrimenti il pc va che una meraviglia. Visualizza allegato 402193
No, xmp DEVE rimanere attivo altrimenti hai la ram a 2133mhz, non te ne sei accorto?

Devi aggiornare il bios all'ultima versione e poi riattiva xmp. I problemi che hai sono dovuti proprio dalla ram non correttamente impostata
 

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Bios aggiornato qualche giorno fa che è uscito dalla Beta preferivo aspettare,comunque so che la mia ram lavora a 2133 stock ma stavo cercando di testare se andava cosi va bene rimetto XMP e in caso di problemi pubblico altri Minidump?
 

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
Bios aggiornato qualche giorno fa che è uscito dalla Beta preferivo aspettare,comunque so che la mia ram lavora a 2133 stock ma stavo cercando di testare se andava cosi va bene rimetto XMP e in caso di problemi pubblico altri Minidump?
Aspetta non ho capito, hai aggiornato all'ultima versione del bios? La 7B86vHB?
 

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Aspetta non ho capito, hai aggiornato all'ultima versione del bios? La 7B86vHB?
Si.Comunque impostazioni mobo stock è attivo solo l' SVM e mi dava problemi anche prima di attivarlo.Guarda ho appena cambiato a XMP e che succede? questo:

On Fri 26/02/2021 11:17:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-6984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0xE3 (0xFFFFF8063BF23580, 0xFFFF82886D489080, 0xFFFF82886505DA10, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread tried to release a resource it did not own.
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.
 

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
Si.Comunque impostazioni mobo stock è attivo solo l' SVM e mi dava problemi anche prima di attivarlo.Guarda ho appena cambiato a XMP e che succede? questo:

On Fri 26/02/2021 11:17:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-6984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0xE3 (0xFFFFF8063BF23580, 0xFFFF82886D489080, 0xFFFF82886505DA10, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread tried to release a resource it did not own.
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.
Ok. Il memory controller della tua cpu è abbastanza scarso. Devi decloccare la ram. Quindi attiva xmp ed imposta 3600mhz. Poi controlla che nei timing venga impostato cl16
 

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Ok. Il memory controller della tua cpu è abbastanza scarso. Devi decloccare la ram. Quindi attiva xmp ed imposta 3600mhz. Poi controlla che nei timing venga impostato cl16
Fatto tengo nessun BSOD all'avvio. Comunque che intendi con controller della CPU?Nei primi sei mesi avevo attivato XMP come scritto sopra ed andava tutto bene
 

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
Fatto tengo nessun BSOD all'avvio. Comunque che intendi con controller della CPU?Nei primi sei mesi avevo attivato XMP come scritto sopra ed andava tutto bene
Il memory controller è integrato nelle cpu e va a fortuna avere un memory controller migliore o meno. Si traduce nel riuscire ad alzare o meno la frequenza della ram
 
  • Like
Reactions: sara93se

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Il memory controller è integrato nelle cpu e va a fortuna avere un memory controller migliore o meno. Si traduce nel riuscire ad alzare o meno la frequenza della ram
Capisco allora provo a risolvere cosi in caso di problemi cosa devo fare continuare a decloccare la ram?
 
  • Like
Reactions: BWD87

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
  • Like
Reactions: Perceval21

Perceval21

Nuovo Utente
69
6
CPU
Ryzen 5 3600X
Dissipatore
Scythe Fuma 2
Scheda Madre
MSI B450 GAMING PLUS MAX
HDD
Sabrent SSD Interno 1TB Rocket NVMe PCIe M.2 2280 + Seagate ST1000DM010 HDD Interno da 1TB
RAM
Viper Steel DDR4 3733 16GB
GPU
MSI GeForce RTX 2070 SUPER 8GB VENTUS OC
Monitor
AOC G2590PX
PSU
Rio Toro GP0650
Case
Noua Smash S1 Black Case ATX PC Gaming
Periferiche
Mouse:Logitech G402 Mouse Gaming Tastiera:KLIM Domination Cuffie:HyperX HX-HSCS-BK Cloud Stinger
OS
Windows 10
Nulla da fare stessa cosa,non so più cosa fare
Edit: potrebbe essere la pasta termica o la polvere dopo solo un anno?




On Fri 26/02/2021 16:46:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-7015-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0xD1 (0xFFFFF8070D2F65C0, 0x2, 0x8, 0xFFFFF8070D2F65C0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 26/02/2021 16:46:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81F9)
Bugcheck code: 0xD1 (0xFFFFF8070D2F65C0, 0x2, 0x8, 0xFFFFF8070D2F65C0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 26/02/2021 16:22:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-7625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80053DFDB57, 0xFFFFD585F1E4AD50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Fri 26/02/2021 16:20:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-6875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0xD1 (0x0, 0xC, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Ultima modifica:

BWD87

Moderatore
Staff Forum
Utente Èlite
34,362
20,538
CPU
Core i5 10600k @5,1GHz cache x49
Dissipatore
Corsair Hydro h100x (2x ml120pro white led push + 2x ml120 pull)
Scheda Madre
MSI Z490 Tomahawk
HDD
Kingston A2000 256GB (SO) + Crucial MX500 1TB (giochi) + Seagate Barracuda 1TB (storage vario)
RAM
32Gb Crucial Ballistix DDR4 3600MHz C16 @3600mhz 15-17-17-35
GPU
MSI GeForce GTX 1070Ti AERO + kraken g12/kraken x31 @2114core/4554vram + 2x sp120 pwm
Monitor
AOC AG271QX
PSU
Corsair TX550M
Case
Corsair Carbide 400R moddato
Periferiche
Ventole case: 3x silent wings 2 in, 2x sp140 led in, 1x sp140 led out
OS
Windows 10
Nulla da fare stessa cosa,non so più cosa fare
Edit: potrebbe essere la pasta termica o la polvere dopo solo un anno?




On Fri 26/02/2021 16:46:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-7015-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0xD1 (0xFFFFF8070D2F65C0, 0x2, 0x8, 0xFFFFF8070D2F65C0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 26/02/2021 16:46:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81F9)
Bugcheck code: 0xD1 (0xFFFFF8070D2F65C0, 0x2, 0x8, 0xFFFFF8070D2F65C0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 26/02/2021 16:22:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-7625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80053DFDB57, 0xFFFFD585F1E4AD50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Fri 26/02/2021 16:20:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-6875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C20)
Bugcheck code: 0xD1 (0x0, 0xC, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
La polvere e la pasta termica non centrano assolutamente nulla. Continua ad abbassare la frequenza della ram finchè non trovi quella stabile. Imposta per ora 3466mhz
 

Entra

oppure Accedi utilizzando

Hot: E3 2021, chi ti è piaciuto di più?

  • Ubisoft

    Voti: 6 20.7%
  • Gearbox

    Voti: 0 0.0%
  • Xbox & Bethesda

    Voti: 21 72.4%
  • Square Enix

    Voti: 0 0.0%
  • Capcom

    Voti: 0 0.0%
  • Nintendo

    Voti: 4 13.8%
  • Altro (Specificare)

    Voti: 1 3.4%