PROBLEMA Error structure corruption win 10

[black.soul]

L'errore si verifica( non vorrei dire stupidate ) quando uso qualche programma del tipo:


-makemkv
-mkvtoolnix
-Total Media Theatre 6

Questa è solo una mia opinione,ma i motivi potrebbero essere altri

 

[Viktor_]

Scarica WhoCrashed e posta il log

 

[black.soul]

[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dump directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 24/02/2016 13:11:55 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\022416-13234-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F59CFD277F8, 0xB3B72BE022540A21, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 24/02/2016 13:11:55 GMT your computer crashed[/B]
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F59CFD277F8, 0xB3B72BE022540A21, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 23/02/2016 19:21:19 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\022316-19062-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F59AB1266C5, 0xB3B72BDFFD93205E, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 23/02/2016 13:46:38 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\022316-13000-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F5960C00696, 0xB3B72BDFB34198AF, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 23/02/2016 12:50:06 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\022316-12109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F5A35AD075D, 0xB3B72BE0882DC0F6, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Mon 22/02/2016 16:57:36 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\022216-12062-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F5A5EBA0ACE, 0xB3B72BE0B13B9CF7, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Mon 22/02/2016 13:41:14 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\022216-14859-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F593C1AA5E3, 0xB3B72BDF8E9B5F8C, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Sat 13/02/2016 14:07:14 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\021316-13875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F591FD6B754, 0xB3B72BDF725770ED, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Fri 12/02/2016 13:34:00 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\021216-15718-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A01F59F639F767, 0xB3B72BE048BAB100, 0x1, 0x18)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI][SIZE=4][B][HR][/HR]Conclusion[/B][HR][/HR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000]9 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic [URL="http://www.resplendence.com/whocrashed_troubleshooting"]general suggestions for troubleshooting system crashes[/URL] 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. [/COLOR][/SIZE][/FONT]

Se ho capito qualcosa, l'errore riguarda un driver mancante;infatti sul pc ho un driver sconosciuto Sistema compatibile ACPI Microsoft

 driver del dispositivo specificato non sono stati installati. (Codice 28)

Impossibile trovare driver compatibili per il dispositivo specificato.




Per trovare un driver per questo dispositivo, fare clic su Aggiorna driver.

Ho provando ad aggiornare i driver con driver booster ma niente da fare

 

[Viktor_]

Total media theatre non é supportato da windows 10 e al 99% é la causa del tuo problema. Eliminalo e disinstalla manualmente il driver, sembra che una disinstallazione classica non basti.

 

[Viktor_]

PowerDVD 15 é un valido sostituto a total media theathe

 

[black.soul]

Total media theatre non é supportato da windows 10 e al 99% é la causa del tuo problema. Eliminalo e disinstalla manualmente il driver, sembra che una disinstallazione classica non basti.

Io i programmi li disinstallo con revo unistaller.....ho disinstallato il programma; vi farò sapere se il problema persiste

 

[Viktor_]

No, non penso che metterlo in compatibilità risolverà la cosa. Il log non è così preciso da poter capire esattamente quale programma causa il BSod in questo caso, dovresti postare il file .dmp. Ma direi che non c'è bisogno, già tu avevi dei sospetti, in più in altri forum si legge che TMT causa il BSoD su win10 quindi direi che al 99% il problema è quello. Altrimenti è la ram, ma è quasi impossibile.

 

[black.soul]

il pc è nuovo,non ha manco un mese di vita....cmq penso anch'io che sia quello il problema...hai una soluzione a questo?http://www.tomshw.it/forum/windows/564606-associazione-file-iso-windows-10-a.html#post5335335

 

[Viktor_]

il pc è nuovo,non ha manco un mese di vita....cmq penso anch'io che sia quello il problema...hai una soluzione a questo?http://www.tomshw.it/forum/windows/564606-associazione-file-iso-windows-10-a.html#post5335335

Ho risposto