Näe då inget att oroa sig över. om det inte börja hända oftare... datorer har en förmåga att bete sig underligt 
kan bero på att den blivit för varm om du hade den i knäet, ex kan en fläkt ha blivit igen täppt.
kör på och återkom om det börjar bli mer en regel än ett undantag att den gör så.
kan bero på att den blivit för varm om du hade den i knäet, ex kan en fläkt ha blivit igen täppt.
kör på och återkom om det börjar bli mer en regel än ett undantag att den gör så.
Citat:
Näe då inget att oroa sig över. om det inte börja hända oftare... datorer har en förmåga att bete sig underligt
kan bero på att den blivit för varm om du hade den i knäet, ex kan en fläkt ha blivit igen täppt.
kör på och återkom om det börjar bli mer en regel än ett undantag att den gör så.
kan bero på att den blivit för varm om du hade den i knäet, ex kan en fläkt ha blivit igen täppt.
kör på och återkom om det börjar bli mer en regel än ett undantag att den gör så.
Ja, jag brukar faktiskt ligga raklång med benen under datorn, så det kan nog ha varit fläkten som täppts igen. Tack så mycket för dina insikter.
Citat:
Skälet till craschen finns att finna i Windows loggar men de är inte så utförligt informativa så ladda ner det här http://www.resplendence.com/whocrashed istället och få reda på den direkta , oftast , orsaken . Sedan kan du vidta åtgärder enligt det beskedet vilket ofta brukar handla om uppdatering av en drivrutin .
Jag får köra det där programmet nästa gång den kraschar. Nu får jag bara meddelanden om krascher som mig veterligen inte har kraschat.
Citat:
Du körde alltså "who crasched" och scrollade ner till slutet på rapport sidan där det står en sammanfattning .
Om du inte har agerat annorlunda nu jämfört med förut så talar det emot fläkten , eller för en massa damm
. Men du fattar nog innebörden av vad jag menar .
__________________
Senast redigerad av 1FF 2015-02-20 kl. 21:50.
Senast redigerad av 1FF 2015-02-20 kl. 21:50.
Citat:
Jag körde en analys med (det nyinstallerade [om det gör någon skillnad]) WhoCrashed. Nog för att jag inte har bekantat mig väl med programmet ifråga, men det enda jag får i rapporten är följande:
Citat:
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: XXX
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: 20268 , LENOVO, Cherry 3A Touch
CPU: GenuineIntel Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4001652736 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 2015-01-29 16:15:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012915-23843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0014E4DB680, 0xFFFFD00180B9A960, 0xFFFFE00157D90B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Thu 2015-01-29 16:15:43 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, 0xFFFFE0014E4DB680, 0xFFFFD00180B9A960, 0xFFFFE00157D90B80)
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 Thu 2015-01-29 14:14:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012915-22390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0010AAD5060, 0xFFFFF8033275D960, 0xFFFFE0011EF06010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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
--------------------------------------------------------------------------------
3 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 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.
Welcome to WhoCrashed (HOME EDITION) v 5.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: XXX
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: 20268 , LENOVO, Cherry 3A Touch
CPU: GenuineIntel Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4001652736 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 2015-01-29 16:15:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012915-23843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0014E4DB680, 0xFFFFD00180B9A960, 0xFFFFE00157D90B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Thu 2015-01-29 16:15:43 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, 0xFFFFE0014E4DB680, 0xFFFFD00180B9A960, 0xFFFFE00157D90B80)
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 Thu 2015-01-29 14:14:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012915-22390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0010AAD5060, 0xFFFFF8033275D960, 0xFFFFE0011EF06010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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
--------------------------------------------------------------------------------
3 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 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.
Edit: Jag har inte haft några problem sedan igår (inatt, under detta dygn). Datorer, och hela universum, må bygga på logik, men ter sig inte saker vara fullständigt slumpmässiga ibland?
__________________
Senast redigerad av BreehcNicdoll 2015-02-20 kl. 22:35.
Senast redigerad av BreehcNicdoll 2015-02-20 kl. 22:35.
.
Skapa ett konto eller logga in för att kommentera
Du måste vara medlem för att kunna kommentera
