Изтегли си една Live CD Linux  и виж как ще се държи

А  бе стига с тестове! Имаш дефектен хардуер. Не си длъжен сега да изучаваш цялата материя, само и само, че някой ти е продал повреден лаптоп.Отиваш с АИДА на компютъра, пускаш им стрес теста и да видят.

След сканиране с WhoCrashed ми дава това :

 

Crash Dump Analysis 

Crash dump directory: C:WindowsMinidump

Crash dumps are enabled on your computer.

On Sat 26.4.2014 г/ 8:01:15 GMT your computer crashed
crash dump file: C:WindowsMinidump042614-26187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF690002AFCF8, 0x0, 0xFFFFF80276EEC1AE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time. 



On Sat 26.4.2014 г/ 8:01:15 GMT your computer crashed
crash dump file: C:Windowsmemory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF690002AFCF8, 0x0, 0xFFFFF80276EEC1AE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 that cannot be identified at this time. 



On Sat 26.4.2014 г/ 5:59:05 GMT your computer crashed
crash dump file: C:WindowsMinidump042614-28234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF69000AC4CD8, 0x0, 0xFFFFF802EF8751AE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time. 



On Fri 25.4.2014 г/ 19:52:01 GMT your computer crashed
crash dump file: C:WindowsMinidump042514-17968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF690000BE328, 0x0, 0xFFFFF8004C4FD1AE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time. 



On Thu 24.4.2014 г/ 11:24:06 GMT your computer crashed
crash dump file: C:WindowsMinidump042414-26000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF6900033BA38, 0x0, 0xFFFFF80026E801AE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time. 



On Thu 24.4.2014 г/ 10:31:57 GMT your computer crashed
crash dump file: C:WindowsMinidump042414-23281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803E5E5BC83, 0xFFFFD00022C98D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time. 



On Tue 22.4.2014 г/ 12:11:29 GMT your computer crashed
crash dump file: C:WindowsMinidump042214-25281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFF69000023F60, 0x0, 0xFFFFF8017067CBA8, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:Windowssystem32ntoskrnl.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 that cannot be identified at this time. 



Conclusion 

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

Според това сканиране Уиндоуса е омазан.

Значи да преинсталирам ?

Да преинсталирай, но без да слагаш никакви драйвъри, остави само това, което ще си сложи уиндоуса, и тествай така системата.

Проблема е с рам-а заводски проблем онзи ден им го пратих в сервиза на Acer в София сега очаквам след празниците да ми го върнат !!!

Тествай RAM паметта.

 

Като ти пее радиото, ще го слушаш   А на онези отиди и им тегли една сочна и дълга. Чак ми иде да дойда с теб и аз да им се изкефя. Няма такива помияри