Laptopen BSODar ibland,
Hej Sweclockers!!!
Laptopen har börjat att BSODa emellanåt och det är ju sjukt jävla störigt. Frågan är vad jag ska göra för att fixa problemet.
Jag har kört de senaste virusprogrammet och scannat hårddisken och den hittar inget.
Har inte uppdaterat några drivrutiner innan den började bsoda. Uppdaterat de drivrutiner jag kan och fortfarande samma skit.
Kan det vara hårddisken som är dålig eller kan det vara något annat??
Och hur gör jag för att köra ett minnestest på hårddisken?? TOSHIBA THNSNF128GCSS
Körde någon whocrasched och det var detta som kom fram
Någon som har tips på vad jag kan göra för att fixa detta??
//niclas
Bild
BildBildBild
System Information (local)
computer name: nckmtt
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: QOSMIO X870, TOSHIBA, Portable PC
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17129771008 total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 2015-06-18 18:47:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061815-5343-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800DDF4A3FB, 0xFFFFD001C02DCE70, 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 that cannot be identified at this time.
On Thu 2015-06-18 18:34:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061815-6171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x19 (0x3, 0xFFFFC00165CD1170, 0xFFFFC00165CD11D0, 0xFFFFC00165CD1170)
Error: BAD_POOL_HEADER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
20 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 344.60 , NVIDIA Corporation)
npf.sys (npf.sys (NT5/6 AMD64) Kernel Driver, CACE Technologies, Inc.)
iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation)
smb_driver_intel.sys (Synaptics SMBus Driver, Synaptics Incorporated)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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.
//niclas
