GSV

Ik heb eindelijk mijn laptop terug van de verkoper, ze hebben hem moeten opzenden naar HP, daar hebben ze een nieuw moederbord ingestoken, dus normaal is het opgelost dankuwel voor jullie raad

sfcdetails.txt

Dankuwel, deze namiddag ga ik naar de verkoper, ik hou jullie in de gaten over het vervolg

Sorry voor het late antwoord maar ik heb de laatste tijd niet zo veel tijd gehad ja, ik zal zo snel mogelijk naar de verkoper gaan en hem laten nakijken, ook nog iets, deze laptop was een toonzaalmodel, dus niet helemaal nieuw. en ik heb nog eens met whocrashed gekeken en bijna iedere crash dump komt door: ntoskrl.exe? een driver ? ik ken er niet zo veel van maar kan het misschien ook een driver probleem zijn en misschien moet ik dan laatste update drivers installeren ofzo?

harde schijf 120 graden?? kan dat ?

http://speccy.piriform.com/results/goKeSTvbf5bQakVfEnLhTQt hier nog een logje

ik heb sinds 5 Oktober geen problemen meer gehad, anders had ik het bijna iedere dag, zeker zijn ben ik natuurlijk nog niet maar voorlopig is het in orde.

Zal ik doen, maar ik heb het al een tijdje niet meer gehad, als ik het nog eens heb ga ik naar de verkoper

dat zal ik misschien best eens doen ja. Een vriend van mij heeft heel de zelfste laptop en hij zegt ook dat zijn laptop heel warm word.. dus misschien hebben die soort een minder goed koelsysteem ofzo?..

Mijn laptop word inderdaad soms zeer warm, maar ik heb al horen zeggen dat veel HP laptops daar last van hebben? Ja, ik heb hem van augustus, dus een vrij nieuwe laptop

http://speccy.piriform.com/results/wPQe0SsB1QtpezIzRKapNbl Dit zijn de resultaten.

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!