Hallo,

mein Netbook hat immer Bluescreens beim Hochfahren und reagiert immer wieder extrem langsam. Kann mir jemand helfen?

Helfen kann man dir nur wenn du vernünftige Angaben machst.

Betriebssystem, Patchstand, Eckdaten der Hardware und Wortlaut des BlueScreens.

Und seit wann du diesen BlueScreen hast, was zuvor am System verändert wurde.

Danke für die schnelle Antwort.
Betriebssystem: Windows 7 Starter
Patch: Service Pack 1
Eckdaten:
Prozessor: Intel(R) Atom(TM) CPU N270 @ 1.60 Ghz
Installierter Arbeitsspeicher: 1,00 GB
Systemtyp: 32 Bit-Betriebssystem
Zum Wortlaut des Bluescreens kann ich leider nichts sagen, er trat heute nicht auf.
Der Erste war vor etwa zwei Wochen.
Veränderungen habe ich in letzter Zeit keine vorgenommen.

Prozessor: Intel(R) Atom(TM) CPU N270 @ 1.60 Ghz
Installierter Arbeitsspeicher: 1,00 GB

Ähm ganz ehrlich......frag ich mich gerade was man damit noch sinnvoll überhaupt machen kann. Ultrabillige-Schrumpf-CPU mit extrem wenig Arbeitsspeicher? Das Gerät in dieser Ausstattung sollte besser mit Linux betrieben werden

Ansonsten läuft Windows aber nohc? Wenn ja, mal dieses Tool laufen lassen und Logs posten => WhoCrashed - Download - Filepony

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.52
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) 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 (or black) 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: NETBOOK1
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\windows
Hardware: N130 , SAMSUNG ELECTRONICS CO., LTD.
CPU: GenuineIntel Intel(R) Atom(TM) CPU N270 @ 1.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 1063641088 bytes total




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

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Sun 28.02.2016 12:49:06 GMT your computer crashed
crash dump file: C:\windows\Minidump\022816-24055-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x119C4E) 
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFFFF8B67A8B0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sun 21.02.2016 08:42:46 GMT your computer crashed
crash dump file: C:\windows\Minidump\022116-97157-01.dmp
This was probably caused by the following module: rtkvhda.sys (RTKVHDA+0x23852F) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF9826252F, 0xFFFFFFFF86E76AC8, 0xFFFFFFFF86E766A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\drivers\rtkvhda.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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: rtkvhda.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.). 
Google query: Realtek Semiconductor Corp. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Wed 10.02.2016 05:40:08 GMT your computer crashed
crash dump file: C:\windows\Minidump\021016-18969-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA7891) 
Bugcheck code: 0x19 (0x22, 0x10000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue). 
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 09.02.2016 18:41:05 GMT your computer crashed
crash dump file: C:\windows\Minidump\020916-23462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x821F2) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0402062, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
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 30.01.2016 10:27:03 GMT your computer crashed
crash dump file: C:\windows\Minidump\013016-17534-01.dmp
This was probably caused by the following module: rtkvhda.sys (RTKVHDA+0x23852F) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF80E4752F, 0xFFFFFFFF86A6AAC8, 0xFFFFFFFF86A6A6A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\drivers\rtkvhda.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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: rtkvhda.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.). 
Google query: Realtek Semiconductor Corp. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 23.01.2016 19:51:21 GMT your computer crashed
crash dump file: C:\windows\Minidump\012316-17238-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA9375) 
Bugcheck code: 0x1A (0x41287, 0x18, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
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 Thu 30.04.2015 10:06:37 GMT your computer crashed
crash dump file: C:\windows\Minidump\043015-19110-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD233C) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC040204A, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
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 25.03.2015 15:24:02 GMT your computer crashed
crash dump file: C:\windows\Minidump\032515-21403-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x77CF2) 
Bugcheck code: 0x50 (0xFFFFFFFF800052E4, 0x0, 0xFFFFFFFF87272CF2, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\ndis.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NDIS 6.20-Treiber
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 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. 





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

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

rtkvhda.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)

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.
         

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

rtkvhda.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)

whocrashed meint, der Realtek Treiber sei schuld. Prüfe ob es Trieberupdates gibt.
Und nochmal, wenn du nur ne billige Atom CPU und 1 GiB RAM hast musst du dich nun wirklich nicht über ein langsames System beschweren.