PC valt uit en start na 10 seconden opnieuw op

Status
Niet open voor verdere reacties.

noliko

Gebruiker
Lid geworden
15 jul 2012
Berichten
194
PC valt uit en start na 10 seconden opnieuw op . De eerste keer toen ik met het programma Pinnacle Studio 18 bezig was en de andere keer toen ik gewoon een site van een reisorganisator bezocht . Navraag leert mij dat dit wel eens aan de voeding te wijten is en daarom zou ik deze willen vervangen .
Ik weet niet waar ik op moet letten bij die aankoop . Mijn PC is 6 jaar oud heeft een Intel Corei5 750 2.67 GHz processor . Moeten er nog gegevens bekend zijn .
 
Heb je de windows logboeken al geraadpleegd rond het moment van uitvallen?
Het hoeft niet perse je voeding te zijn.
 
Je kunt toch gewoon op de sticker kijken die aan de zijkant op je voeding zit..?
Daarop moet in elk geval het vermogen vermeld zijn.
Dan kijk je hier naar een nieuwe van minimaal hetzelfde of een iets hoger vermogen ( + 50 - 60 watt )..

Maar het is, zoals hier boven opgemerkt, eerst zaak vast te stellen of het probleem wel in de voeding zit.
Kan ook heel goed een warmte-probleem zijn om maar eens wat te noemen.
 
Laatst bewerkt:
Hoe of waar kan ik die Windows logboeken raadplegen ?
 
Ik ben in die logboeken geraakt maar ik zal ,wanneer het probleem zich weer voor doet ,onmiddellijk dat logboek raadplegen .
Ga ik dan de oorzaak van het uitvallen van mijn PC dan kunnen zien ?
 
Je zou in de logboeken foutmeldingen moeten kunnen zien met daarbij een betekenis / verklaring zoals op onderstaande afbeelding:
logboek.jpg
 
Vandaag voor de derde maal PC terug uitgevallen en na enkele seconden terug opgestart . Maar voor dat hij uitviel wilde ik mijn post contoleren en die was verdwenen . Toen viel de PC uit en na het terug heropstarten was alles verdwenen . Mijn bureaublad zag er uit precies zo als na de installatie van Windows 10 . Mijn apps die ik er op had geplaatst , alles weg . Ik heb toen en systeemherstel gedaan van enkele dagen terug en nu is alles weer normaal .
Ik ben ook naar mijn logboeken gaan kijken en daar stonden 3 rode uitroepingstekens in een cirkel die vermelde Fout Windows Update Client en Fout Windows Distributed Com.
Ook was er nog een uitroepingsteken in een driehoek waar langs stond Waarschuwing Tcpip .
 
Lees nergens of de PC aan de binnenzijde stofvrij is, m.n. de koelblokken en ventilatoren van de CPU en eventueel grafische kaart.

Zet de weblink van Speccy eens hier neer, zie m'n sig.

En geeft deze tool wat weer?
http://www.resplendence.com/whocrashed

De info van systeem logboeken zegt maar weinig helaas.
 
Beste mensen ,
Ik zal mijn PC eens binnen brengen bij de PC boer want zo een PC freak ben ik nu ook weer niet . Het enige wat ik nu nog heb gedaan is Windows Defender uitgeschakeld omdat ik hier met Norton Security zit te werken als antivirus programma . Misschien dat deze in conflict liggen met elkander .
Die tool , moet ik daar iets voor downloaden want dat vind ik niet op die site .
 
Hier zijn al de gegevens :
System Information (local)
--------------------------------------------------------------------------------

Computer name: THEO-PC
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: P55-UD3, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4290236416 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 8/04/2016 11:00:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040816-8343-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001BDDE6270, 0xFFFFF80062F55AD0, 0xFFFFE001C5CF0C10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 8/04/2016 11:00:12 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001BDDE6270, 0xFFFFF80062F55AD0, 0xFFFFE001C5CF0C10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 8/04/2016 10:15:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040816-8640-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00039BE9060, 0xFFFFF80275355AD0, 0xFFFFE00040B25010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 30/03/2016 18:03:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033016-8500-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000DD244270, 0xFFFFF801DE555AD0, 0xFFFFE000E4631C10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 30/03/2016 14:11:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033016-8328-01.dmp
This was probably caused by the following module: ex64.sys (EX64+0xF6B0E)
Bugcheck code: 0x9F (0x3, 0xFFFFE00118EC3270, 0xFFFFF8031BD5CCE0, 0xFFFFE0011765BC10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Program Files (x86)\Norton Security\Norton Security\NortonData\22.6.0.142\Definitions\VirusDefs\20160407.040\EX64.SYS
product: Symantec Antivirus Engine
company: Symantec Corporation
description: AV Engine
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: ex64.sys (AV Engine, Symantec Corporation).
Google query: Symantec Corporation DRIVER_POWER_STATE_FAILURE



On Wed 30/03/2016 14:03:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033016-8296-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0006ED7C270, 0xFFFFF80345755AD0, 0xFFFFE000777B8C10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 30/03/2016 13:54:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033016-8281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001A7DE5270, 0xFFFFF80093355AD0, 0xFFFFE001AE7C0010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 30/03/2016 13:43:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033016-8234-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0004AEE2270, 0xFFFFF803B8F55AD0, 0xFFFFE00048B5AAA0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 30/03/2016 13:35:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033016-8609-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0001055E060, 0xFFFFF8010D555AD0, 0xFFFFE0000ECEBC10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 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:

ex64.sys (AV Engine, Symantec Corporation)

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.
 
Ik zal deze laatste tut eens proberen maar zo als eerder aangehaald . Ik ben geen computertechneut .
 
Status
Niet open voor verdere reacties.
Steun Ons

Nieuwste berichten

Terug
Bovenaan Onderaan