Problema kernel-power

kimidan88 · 30 Maggio 2014

Ciao a tutti,
da venerdi (giorno in cui mi è arrivato il pc) che è il seguente:
case: zalman z11 plus
alimentatore: corsair cx 750
scheda madre: msi a88x-g45-gaming
processore: amd a10-7850k
memoria : kit gamer series AMD radeon memory 8 gb (2x4 gb)
scheda video: AMD radeon r9 290x

ho installato i driver piu' recenti ati,
ma quando gioco a battlefield 4 o assassin creed black flag dopo 10 min o pure meno crasha...e il piu' delle volte da schermata blu..con errore dxgmms1.sys !!!!
in visualizzatore eventi l errore è kernel-power id 41
ho cercato su internet e dicono che è relativo alla scheda video,i drivers...ma sono stati aggiornati con i piu' recenti..
ho anche aggiornato il bios della scheda madre,
fatto il test delle memorie, ma l errore si presenta sempre...
secondo voi (mi sta venendo in mente quest idea) puo' essere l alimentatore che non c è la fa'???

grazie per le risposte
spero di risolvere il problema
daniele

Ariete_ · 30 Maggio 2014

Hai installato i 14.6 beta per caso?

kimidan88 · 30 Maggio 2014

Ariete_ ha detto:
Hai installato i 14.6 beta per caso?

Si si e anche con quelli stesso problema...
Però ho Windows 7 normale..senza il service pack 1..puo essere questo il problema?

Ariete_ · 30 Maggio 2014

Te lo da anche con i 14.4? Hai fatto overclock? il problema è cominciato in un momento preciso?

kimidan88 · 31 Maggio 2014

Si si.no.nessun o.c.
No in un momento preciso, pensavo che fosse tutto ok e invece una volta giocato si è presentato il problema

- - - Updated - - -

questa la segnalazione

Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7601.2.1.0.256.1
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88007550A53
BCP3: FFFFF880085FC598
BCP4: FFFFF880085FBDF0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

c è qualcuno che sa la soluzione al problema?
le sto provando tutte...ma senza risultato

Ariete_ · 31 Maggio 2014

scarica whocrashed fai l'analisi e posta il log.

kimidan88 · 1 Giugno 2014

[TD="width: 15"] - [/TD]
[TD="width: 130"] System [/TD]

[TD="width: 15"] -

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

[TD="width: 130"] Provider [/TD]

Microsoft-Windows-Kernel-EventTracing

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 12"][/TD]
[TD="width: 105"][ Name ] [/TD]

{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 12"][/TD]
[TD="width: 105"][ Guid ] [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

3

[TD="width: 130"] EventID [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

0

[TD="width: 130"] Version [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

2

[TD="width: 130"] Level [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

2

[TD="width: 130"] Task [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

14

[TD="width: 130"] Opcode [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

0x8000000000000010

[TD="width: 130"] Keywords [/TD]

[/TD]

[TD="width: 15"] -

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

[TD="width: 130"] TimeCreated [/TD]

2014-05-30T12:17:39.675498900Z

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 12"][/TD]
[TD="width: 105"][ SystemTime ] [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

2

[TD="width: 130"] EventRecordID [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

Correlation

[/TD]

[TD="width: 15"] -

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

[TD="width: 130"] Execution [/TD]

4

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 12"][/TD]
[TD="width: 105"][ ProcessID ] [/TD]

172

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 12"][/TD]
[TD="width: 105"][ ThreadID ] [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

Microsoft-Windows-Kernel-EventTracing/Admin

[TD="width: 130"] Channel [/TD]

[/TD]

[TD="width: 15"]

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

Kimi-PC

[TD="width: 130"] Computer [/TD]

[/TD]

[TD="width: 15"] -

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]

[TD="width: 130"] Security [/TD]

S-1-5-18

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 12"][/TD]
[TD="width: 105"][ UserID ] [/TD]

[/TD]

[TD="width: 15"] - [/TD]
[TD="width: 130"] EventData [/TD]

ReadyBoot

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 130"] SessionName [/TD]

C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 130"] FileName [/TD]

3221225864

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 130"] ErrorCode [/TD]

0

[TD="width: 15"][/TD]
[TD="width: 15"][/TD]
[TD="width: 130"] LoggingMode [/TD]

Ariete_ · 1 Giugno 2014

Non è questo. Devi cliccare su 'analyze' e poi devi andare sulla tab dump file. Posta quello che sta scritto li.

kimidan88 · 1 Giugno 2014

Crash dump file: C:\Windows\Minidump\010111-20170-01.dmp
Date/time: 01/01/2011 01:15:08 GMT
Uptime: 01:05:29
Machine: KIMI-PC
Bug check name: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check code: 0x1000007E
Bug check parm 1: 0xFFFFFFFFC0000005
Bug check parm 2: 0xFFFFF880073D5CF7
Bug check parm 3: 0xFFFFF880021B2568
Bug check parm 4: 0xFFFFF880021B1DC0
Probably caused by: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT]
Driver description: [FONT=Segoe UI, Arial]DirectX Graphics MMS[/FONT]
Driver product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
Driver company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
OS build: Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

ciao
scusa avevo sbagliato xD

- - - Updated - - -

ho smontato la scheda video r9 290x
stamattina e mi ha dato un altro errore:

Crash dump file: C:\Windows\memory.dmp
Date/time: 01/06/2014 05:39:52 GMT
Uptime: 00:33:31
Machine: KIMI-PC
Bug check name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check code: 0x50
Bug check parm 1: 0xFFFFFA800197DD80
Bug check parm 2: 0x0
Bug check parm 3: 0xFFFFF880073B7FD6
Bug check parm 4: 0x2
Probably caused by: [FONT=Segoe UI, Arial]Unknown[/FONT]
Driver description: [FONT=Segoe UI, Arial][/FONT]
Driver product: [FONT=Segoe UI, Arial][/FONT]
Driver company: [FONT=Segoe UI, Arial][/FONT]
OS build: Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Architecture: x86 (32 bit)
CPU count: 4
Page size: 4096

Ariete_ · 1 Giugno 2014

nemmeno questo va bene. Mi sono sbagliato io. devi scorrere in basso la tab report fino ad arrivare a "Crash Dump Analysis" posta le scritte di questa sezione

kimidan88 · 1 Giugno 2014

scusami,intendi dire questa:
Bug check description:
This indicates that a system thread generated an exception which the error handler did not catch.

Comments:
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.

- - - Updated - - -

Bug check description:
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Comments:
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.

Ariete_ · 1 Giugno 2014

no.

E' una cosa tipo questa

[FONT=Segoe UI, Arial]On Thu 29/05/2014 08:33:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052914-14508-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal+0x1D1AE)
Bugcheck code: 0xA (0xFFFFF8800B651FF8, 0x2, 0x1, 0xFFFFF800036311AE)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
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 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]

kimidan88 · 2 Giugno 2014

ciao ,
ho testato di nuovo le ram con il memtest 86+ e non ha dato errori,
ho fatto una prova con delle ram Corsair 1333mhz 8gb (2x4 gb) e non ha dato nessun problema.
ho giocato a battlefield 4 tranquillamente e il problema non si è presentato.
ho rimesso le ram AMD ed invece dopo 20min circa il problema è apparso...
puo' essere che le ram siano danneggiate?o non pienamente funzionanti?
perche' il problema mi si presenta solo con loro...
grazie a tutti per le risposte

Ariete_ · 2 Giugno 2014

Voglio vedere perchè hai blu screen e se non posti quello che ho detto non so come fare.

- - - Updated - - -

Forse non hai capito come si fa.. Allora, apri whocrashed e clicca su Analyze. Poi scorri in basso con la rotellina del mouse fino a quando non incontri il paragrafo Crash Dump Analysis.

Fai copia e incolla di quello che sta scritto sotto di questo (fino a Conclusion).

kimidan88 · 2 Giugno 2014

Ariete_ ha detto:
Voglio vedere perchè hai blu screen e se non posti quello che ho detto non so come fare.

- - - Updated - - -

Forse non hai capito come si fa.. Allora, apri whocrashed e clicca su Analyze. Poi scorri in basso con la rotellina del mouse fino a quando non incontri il paragrafo Crash Dump Analysis.

Fai copia e incolla di quello che sta scritto sotto di questo (fino a Conclusion).

ciao
scusami ,ti chiedo scusa...sbagliavo perche' entravo sul file dump...
ecco

[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 02/06/2014 09:33:21 your computer crashed
crash dump file: C:\Windows\Minidump\060214-18657-01.dmp
uptime: 00:22:58
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x398)
Bugcheck code: 0x50 (0xFFFFFA8002925340, 0x0, 0xFFFFF880075D640C, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 Mon 02/06/2014 09:33:21 your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:22:58
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x398)
Bugcheck code: 0x50 (0xFFFFFA8002925340, 0x0, 0xFFFFF880075D640C, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 Sun 01/06/2014 12:22:18 your computer crashed
crash dump file: C:\Windows\Minidump\060114-24679-01.dmp
uptime: 00:31:55
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x30C, 0x2, 0x8, 0x30C)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sat 31/05/2014 15:03:30 your computer crashed
crash dump file: C:\Windows\Minidump\053114-12558-01.dmp
uptime: 00:15:37
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880069CCCF7, 0xFFFFF880021F6568, 0xFFFFF880021F5DC0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 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 Sat 31/05/2014 13:29:00 your computer crashed
crash dump file: C:\Windows\Minidump\053114-12870-01.dmp
uptime: 01:24:26
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xC4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800757DD90, 0xFFFFF880085A9568, 0xFFFFF880085A8DC0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 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 Sat 31/05/2014 11:59:21 your computer crashed
crash dump file: C:\Windows\Minidump\053114-13603-01.dmp
uptime: 00:16:43
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xFBF)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007550A53, 0xFFFFF880085FC598, 0xFFFFF880085FBDF0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 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 Sat 31/05/2014 11:40:42 your computer crashed
crash dump file: C:\Windows\Minidump\053114-12308-01.dmp
uptime: 00:18:41
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xC4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007561D90, 0xFFFFF880020EB568, 0xFFFFF880020EADC0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 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 Sat 01/01/2011 02:15:08 your computer crashed
crash dump file: C:\Windows\Minidump\010111-20170-01.dmp
uptime: 01:05:29
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880073D5CF7, 0xFFFFF880021B2568, 0xFFFFF880021B1DC0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 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]8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

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 actually 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]

Problema kernel-power

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente

Ariete_

kimidan88

Nuovo Utente