bluescreen windows7

[anoniem]

Wie zou me willen helpen? Ik krijg steeds bluescreens op windows 7, en netbook. Ook de melding dat de bootsector niet is te vinden. Na een schone installatie van het systeem, via externe schijf, draait het systeem wel, maar geeft meerdere keren per dag toch blue screens. Zou het de harde schijf kunnen zijn? alvast bedankt. gr jeroen

[anoniem]

dat wordt giswerk...., geef eens aan welke foutboodschappen er op die blue screens staan

[anoniem]

Ik houdt het in de gaten, en zodra ik wat heb regaeer ik weer. ( hij draait nu al weer uren zonder problemen , vreemd ). Alvast bedankt voor je reactie, en ik kom hier terug. groeten, Jeroen

[anoniem]

Download het programma Whocrashed. Als je dan weer een bsod krijgt kun je makkelijk achterhalen wat de oorzaak is. Zie: http://computertotaal.nl/software/22990-whocrashed-3-02.html vr.gr

[anoniem]

Ik ga het meteen even downloaden. bedankt weer! gr jeroen

[anoniem]

Dat gaat snel, ik plak de tekst even hierbij. Welcome to WhoCrashed (HOME EDITION) v 4.01 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 also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features. Click here for more information on the professional edition. Click here to buy the the professional edition of WhoCrashed. System Information (local) computer name: HPMINI windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Atom(TM) CPU N270 @ 1.60GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 1064624128 total VM: 2147352576, free: 1981661184 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Wed 21-11-2012 21:35:41 GMT your computer crashed crash dump file: C:\Windows\Minidump\112112-16083-01.dmp This was probably caused by the following module: ataport.sys (ataport+0x189CC) Bugcheck code: 0x7A (0xFFFFFFFFC0432F70, 0xFFFFFFFFC0000185, 0x33F07860, 0xFFFFFFFF865EE9CC) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\drivers\ataport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: ATAPI Driver Extension Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 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. On Wed 21-11-2012 21:35:41 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ataport.sys (ataport+0x15DA3) Bugcheck code: 0x7A (0xFFFFFFFFC0432F70, 0xFFFFFFFFC0000185, 0x33F07860, 0xFFFFFFFF865EE9CC) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\drivers\ataport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: ATAPI Driver Extension Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 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. On Fri 16-11-2012 15:09:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\111612-19094-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE98) Bugcheck code: 0x7A (0xFFFFFFFFC0535078, 0xFFFFFFFFC0000185, 0x1B36BE0, 0xFFFFFFFFA6A0F000) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 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 16-11-2012 14:50:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\111612-52962-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE98) Bugcheck code: 0x7A (0xFFFFFFFFC05D18A0, 0xFFFFFFFFC0000185, 0x3355B8C0, 0xFFFFFFFFBA314000) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 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 7-11-2012 15:57:56 GMT your computer crashed crash dump file: C:\Windows\Minidump\110712-18018-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE98) Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF84EB8A58, 0xFFFFFFFF84EB8BC4, 0xFFFFFFFF81E69E10) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 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 that cannot be identified at this time. On Sun 28-10-2012 14:32:22 GMT your computer crashed crash dump file: C:\Windows\Minidump\102812-15615-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x1512F8) Bugcheck code: 0x7A (0xFFFFFFFF872CDAB8, 0xFFFFFFFFC0000185, 0x64D5864, 0xFFFFFFFF8D1F12F8) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 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. On Sat 20-10-2012 10:07:57 GMT your computer crashed crash dump file: C:\Windows\Minidump\102012-64132-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE98) Bugcheck code: 0x7A (0xFFFFFFFFC040F6E8, 0xFFFFFFFFC000000E, 0x35D58860, 0xFFFFFFFF81EDD357) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 8-10-2012 13:21:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\100812-17971-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C) Bugcheck code: 0x7A (0xFFFFFFFFC04890A8, 0xFFFFFFFFC0000185, 0x1508B820, 0xFFFFFFFF9121567E) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 6-10-2012 14:14:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\100712-15600-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C) Bugcheck code: 0x7A (0xFFFFFFFFC040F508, 0xFFFFFFFFC000000E, 0x20DA2860, 0xFFFFFFFF81EA1357) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 2-10-2012 18:54:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\100212-16801-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xC4073) Bugcheck code: 0x7A (0xFFFFFFFFC07EC100, 0xFFFFFFFFC0000185, 0xEE038C0, 0xFFFFFFFFFD820004) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 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. On Tue 2-10-2012 11:33:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\100212-17253-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR Conclusion 11 crash dumps have been found and analyzed. 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.

[anoniem]

Hallo, Kijk hier eens: http://www.pchelpforum.com/xf/threads/bsod-ataport-sys.103587/ en http://www.pchelpforum.com/xf/threads/bsod-ntkrnlpa-exe.127353/ wellicht kom je hier ook verder mee. vr.gr.

[anoniem]

Bdedankt voor je hulp, ik ben aardig op weg. Tevens acronis drive monitor gedraaid en deze geeft aan dat de schijfkwaliteit onder de 60% is gekomen. ( na 2 jaar ). Ik denk zelf nu dat de oplossing voor de hand ligt; nieuw schijfje. groeten, Jeroen