Ga naar inhoud

Crash dump probleem

GSV

Door GSV
in Archief Windows Algemeen

 Delen

Aanbevolen berichten

GSV Groentje

GSV

Geplaatst:
Geplaatst:

Hallo, ik heb sinds kort veel te veel crash-dumps, soms heb ik het 3x per dag.

ik heb een gecheckt met whocrashed en dit zijn de resultaten:

On Fri 5/10/2012 15:37:31 GMT your computer crashed

crash dump file: C:\Windows\Minidump\100512-40887-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E8148A, 0xFFFFF8800B23C1D0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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 which cannot be identified at this time.

On Fri 5/10/2012 15:37:31 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: 0x3B (0xC0000005, 0xFFFFF80002E8148A, 0xFFFFF8800B23C1D0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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 which cannot be identified at this time.

On Fri 5/10/2012 11:56:55 GMT your computer crashed

crash dump file: C:\Windows\Minidump\100512-36363-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x50 (0xFFFFF800020B80B0, 0x0, 0xFFFFF8000316D711, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Thu 4/10/2012 20:32:56 GMT your computer crashed

crash dump file: C:\Windows\Minidump\100412-23587-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)

Error: CLOCK_WATCHDOG_TIMEOUT

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 3/10/2012 19:50:11 GMT your computer crashed

crash dump file: C:\Windows\Minidump\100312-22027-01.dmp

This was probably caused by the following module: atikmdag.sys (atikmdag+0x3DF56E)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004C0056E, 0xFFFFF8800EA52780, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\drivers\atikmdag.sys

product: ATI Radeon Family

company: ATI Technologies Inc.

description: ATI Radeon Kernel Mode Driver

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).

Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION

On Tue 2/10/2012 18:19:47 GMT your computer crashed

crash dump file: C:\Windows\Minidump\100212-40529-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF1, 0x0, 0xFFFFF80003012DD3, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 26/09/2012 18:18:27 GMT your computer crashed

crash dump file: C:\Windows\Minidump\092612-28626-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)

Error: CLOCK_WATCHDOG_TIMEOUT

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 24/09/2012 17:07:13 GMT your computer crashed

crash dump file: C:\Windows\Minidump\092412-45037-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF30, 0x0, 0xFFFFF880012CA75D, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Thu 20/09/2012 20:02:06 GMT your computer crashed

crash dump file: C:\Windows\Minidump\092012-25412-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)

Error: CLOCK_WATCHDOG_TIMEOUT

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 4/09/2012 18:00:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\090412-24648-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)

Error: CLOCK_WATCHDOG_TIMEOUT

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Weet iemand wat ik zou moeten doen om dit te voorkomen, het is echt irritant iedere keer dat je met iets bezig bent sluit windows zich af.

Dankuwel!

Link naar reactie
Delen op andere sites
  • Reacties 21
  • Aangemaakt
  • Laatste reactie

Beste reacties in dit topic

Populaire dagen

Beste reacties in dit topic

Populaire dagen

Geplaatste afbeeldingen

kweezie wabbit Grootmeester

kweezie wabbit

Geplaatst:
Geplaatst:

Kan je het volgende eens uitvoeren zodat we zien met welke hardware we te maken hebben?

Download en installeer Speccy.

Tijdens de installatie heb je nu de mogelijkheid om Nederlands als taal te selecteren.

speccy.png

Als je niet wil dat Google Chrome op je pc als standaard webbrowser wordt geïnstalleerd, moet je de 2 vinkjes wegdoen !!!

Start nu het programma en er zal een overzicht gemaakt worden van je hardware.

Als dit gereed is selecteer je bovenaan " Bestand - Publiceer Snapshot " en vervolgens bevestig je die keuze met " Ja ".

In het venster dat nu opent krijg je een link te zien, kopieer nu die link en plak die in je volgende bericht.

Wil je in woord en beeld zien hoe je een logje van Speccy maakt en plaatst kun je dat Hier lezen.

Ook Dit (KLIK) filmpje laat zien hoe je een Speccy-logje kan plakken in je antwoord.

Na het plaatsen van je logje wordt dit door een expert nagekeken.

Is je systeem overklokt?

Link naar reactie
Delen op andere sites
kweezie wabbit Grootmeester

kweezie wabbit

Geplaatst:
Geplaatst:

Volgens mij zit je met een koelprobleem.

De processor is 45° alhoewel hij maar op halve snelheid draait (800 MHz ipv 1900)

Moederbord wordt ook 44°

Het grootste probleem is echter de harde schijf die 65° wordt terwijl die eigenlijk maximum 45 à 50° mag worden.

Te hoge temperaturen van een PC / laptop worden meestal veroorzaakt door een te hoog stofgehalte.

Om dit op een veilige manier te verwijderen verwijzen we graag naar deze zeer duidelijke uitleg.

Neem de tips grondig door en doe het nodige om je systeem stofvrij te (laten) maken…nadien kan je ons dan de nieuwe resultaten van Speccy bezorgen.

Ik zie dat windows pas in augustus werd geinstalleerd.

Is het een nieuwe laptop of heb je toen zelf windows opnieuw geinstalleerd?

Indien het een nieuwe laptop is, ga je best terug naar de verkoper om het onder garantie te laten nakijken en herstellen.

Link naar reactie
Delen op andere sites
Gast
Dit topic is nu gesloten voor nieuwe reacties.
 Delen
Ga naar topic overzicht
Logo

OVER ONS

PC Helpforum helpt GRATIS computergebruikers sinds juli 2006. Ons team geeft via het forum professioneel antwoord op uw vragen en probeert uw pc problemen zo snel mogelijk op te lossen. Word lid vandaag, plaats je vraag online en het PC Helpforum-team helpt u graag verder!

SITEMAP

×
×
  • Nieuwe aanmaken...

Belangrijke informatie

We hebben cookies geplaatst op je toestel om deze website voor jou beter te kunnen maken. Je kunt de cookie instellingen aanpassen, anders gaan we er van uit dat het goed is om verder te gaan.