PROBLEMA continui bloccaggi e riavvii

[pacomarco]

ciao ragazzi ho un problema con il mio pc.
da qualche tempo non funziona piu come dovrebbe, mi spiego meglio.
il pc funzione anche 10 ore di fila senza il minimo problema utilizzando internet, riproducendo film, excel, ecc.
quando avvio dei giochi invece, in particolare assetto corsa, il pc dopo poco (tempo di scegliere auto, pista e farlo caricare) si blocca producendo un rumore "tipo allegro chilurgo quando si sbagliava":cav: dopo pochi secondi il pc si riavvia ma non parte mai veramente, ovvero si ferma subito dopo la scritta "asrock"... spegnendo e riaccendento tutto torna normale... una volta su 10-12 volte che ho provato mi è uscito un blue screen "memory menagement"...
premetto che ho appena reistallato windows 10 (dava gia problemi prima quindi ho formattato e sono ripartito da 0) e che sia win10 che assetto corsa sono stati comprati regolarmente... ho gia effettuato un memtest e le ram stanno bene...
posto la mia configurazione:
ASRock h170m pro4s
i5-6500
corsair vengeance lpx ddr4 2133Mhz 8GB
gigabyte g1 gaming gtx 970
xfx ts650

confido nella sapienza del forum ... :asd::asd:

 

[il velo di Maya]

CIao :)

Le temperature delle Cpu e della scheda video come sono?

 

[pacomarco]

ciao, le temperature mentre gioco non so come guardarle, normalmente la cpu sta sui 43°...
come faccio a controllarla mentre gioco? grazie

- - - Updated - - -

nel visualizzatore di errori esce kermel power 41...

 

[sognatore761]

Prova a scaricare whocrashed e vedi se ti trova qualcosa, poi posta i risultati. Cmq sembrerebbe un problema di driver o temperature come ipotizzato da @Cibachrome

 

[pacomarco]

Prova a scaricare whocrashed e vedi se ti trova qualcosa, poi posta i risultati. Cmq sembrerebbe un problema di driver o temperature come ipotizzato da @Cibachrome

ciao , sto scrivendo da un altro pc perche dopo essersi spento non parte più :cry:
nel caso riuscissi a farlo ripartire come faccio a misurare la temperatura mentre gioco?
grazie

 

[sognatore761]

Usa hwmonitor per le temperature. Se proprio non si accende penso ti sia partito l'alimentatore

 

[pacomarco]

Usa hwmonitor per le temperature. Se proprio non si accende penso ti sia partito l'alimentatore

alimentatore testato e funzionante... scheda madre?:cry:

 

[sognatore761]

Ma che problemi ti da? Accendi il pc e cosa succede? Non parte più l'avevo interpretato come non si accende

 

[pacomarco]

esatto non si accende ne una spia ne nulla

 

[Kelion]

alimentatore testato e funzionante... scheda madre?:cry:

E come fai a dire alimentatore testato e funzionante se non si accende... ???

 

[pacomarco]

E come fai a dire alimentatore testato e funzionante se non si accende... ???

L'ho testato con un tester e la "corrente" in ogni Pin e giusta quindi credo sia apposto. ..o sbaglio?

 

[Kelion]

Hai cortocircuitato a massa il pin con filo verde per accenderlo senza scheda madre?

- - - Updated - - -

Hai verificato queste tensioni? Visualizza allegato 207388

 

[pacomarco]

esatto, ora il pc è ripartiro ma non va oltre il bios... ho formattato e sto reistallando win10... entro sera dovrei essere pronto per provare le temperature e whocrashed

- - - Updated - - -

Prova a scaricare whocrashed e vedi se ti trova qualcosa, poi posta i risultati. Cmq sembrerebbe un problema di driver o temperature come ipotizzato da @Cibachrome

risultati di whocrashed:
[FONT=Segoe UI, Arial]On Wed 08/06/2016 17:42:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-16109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!TdrBugcheckOnTimeout+0x99)
Bugcheck code: 0x116 (0xFFFFFFFF87AA8250, 0xFFFFFFFF919F8FF4, 0xFFFFFFFFC000009A, 0x4)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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]

- - - Updated - - -

CIao :)

Le temperature delle Cpu e della scheda video come sono?

31°

 

[sognatore761]

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx

Copio e incollo
[h=2]Resolution[/h] The GPU is taking more time than permitted to display graphics to your monitor. This behavior can occur for one or more of the following reasons:

• You may need to install the latest updates for your display driver, so that it properly supports the TDR process.
• Hardware issues that impact the ability of the video card to operate properly, including:
  • Over-clocked components, such as the motherboard
  • Incorrect component compatibility and settings (especially memory configuration and timings)
  • Insufficient system cooling
  • Insufficient system power
  • Defective parts (memory modules, motherboards, etc.)

- - - Updated - - -

I driver della scheda video li hai scaricati dal sito nvidia?

 

[pacomarco]

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx

Copio e incollo
Resolution

The GPU is taking more time than permitted to display graphics to your monitor. This behavior can occur for one or more of the following reasons:

• You may need to install the latest updates for your display driver, so that it properly supports the TDR process.
• Hardware issues that impact the ability of the video card to operate properly, including:
  • Over-clocked components, such as the motherboard
  • Incorrect component compatibility and settings (especially memory configuration and timings)
  • Insufficient system cooling
  • Insufficient system power
  • Defective parts (memory modules, motherboards, etc.)

- - - Updated - - -

I driver della scheda video li hai scaricati dal sito nvidia?

si ho istallato quelli dal disco poi ho scaricato l'ultima versione dal sito

- - - Updated - - -

[FONT=Segoe UI, Arial]Crash Dump Analysis

---

[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\WINDOWS\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Wed 08/06/2016 21:51:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-7484-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32kfull.sys[/FONT] (win32kfull!NtGdiCreateDIBSection+0x1279DD)
Bugcheck code: 0x1A (0x41792, 0xFFFFFFFFC00A35D8, 0x1000, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\WINDOWS\system32\win32kfull.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Full/Desktop Win32k Kernel Driver
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 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 Wed 08/06/2016 21:51:55 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32kfull.sys[/FONT] (win32kfull!NtGdiCreateDIBSection+0x1279DD)
Bugcheck code: 0x1A (0x41792, 0xFFFFFFFFC00A35D8, 0x1000, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\WINDOWS\system32\win32kfull.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Full/Desktop Win32k Kernel Driver
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 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 Wed 08/06/2016 21:49:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-10671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrpamp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC000021A (0xFFFFFFFF834F65C8, 0xFFFFFFFFC0000020, 0x0, 0x20000)
Error: [FONT=Segoe UI, Arial]STATUS_SYSTEM_PROCESS_TERMINATED[/FONT]
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: [FONT=Segoe UI, Arial]ntkrpamp.exe STATUS_SYSTEM_PROCESS_TERMINATED[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Wed 08/06/2016 17:42:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-16109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!TdrBugcheckOnTimeout+0x99)
Bugcheck code: 0x116 (0xFFFFFFFF87AA8250, 0xFFFFFFFF919F8FF4, 0xFFFFFFFFC000009A, 0x4)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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]

---

Conclusion

---

[/FONT]
[FONT=Segoe UI, Arial]4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]ntkrpamp.exe [/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


[/FONT]

- - - Updated - - -

dopo aver installato 1 a 1 tutti i driver della asrock e quelli nvidia.
stesso errore ma cambia il dump

[FONT=Segoe UI, Arial]On Thu 09/06/2016 11:46:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060916-9218-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrpamp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB28, 0xD0B0FC0, 0xFFFFFFFFBBF84000)
Error: [FONT=Segoe UI, Arial]FAULTY_HARDWARE_CORRUPTED_PAGE[/FONT]
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: [FONT=Segoe UI, Arial]ntkrpamp.exe FAULTY_HARDWARE_CORRUPTED_PAGE[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 09/06/2016 11:46:28 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrpamp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB28, 0xD0B0FC0, 0xFFFFFFFFBBF84000)
Error: [FONT=Segoe UI, Arial]FAULTY_HARDWARE_CORRUPTED_PAGE[/FONT]
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: [FONT=Segoe UI, Arial]ntkrpamp.exe FAULTY_HARDWARE_CORRUPTED_PAGE[/FONT]
[/FONT]