Computer crashing and getting Blue Screen

Eddiecb

Prominent
Apr 11, 2017
3
0
510
Good morning, this has been happening for the last few weeks now my computer just turns off and then blue screen and the restarts with do you want to start windows normally etc. i downloaded the Who crashed program and after the last crash this is what came up.

On Thu 21/09/2017 08:02:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092117-20061-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AF68060, 0xFFFFFA800AF68340, 0xFFFFF80003DD2100)
Error: CRITICAL_OBJECT_TERMINATION
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 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 Tue 19/09/2017 14:43:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091917-14866-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AE93060, 0xFFFFFA800AE93340, 0xFFFFF80003D81100)
Error: CRITICAL_OBJECT_TERMINATION
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 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 Fri 15/09/2017 15:31:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091517-26863-01.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x19D6E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001B63D6E, 0xFFFFF8800C0567C8, 0xFFFFF8800C056030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\volsnap.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Shadow Copy 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.
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 Mon 28/08/2017 07:51:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082817-14710-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B35CA10, 0xFFFFFA800B35CCF0, 0xFFFFF80003DC3D30)
Error: CRITICAL_OBJECT_TERMINATION
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 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 Mon 21/08/2017 09:24:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082117-36441-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AD20060, 0xFFFFFA800AD20340, 0xFFFFF80003D80D30)
Error: CRITICAL_OBJECT_TERMINATION
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 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.

could someone advise me on whats going on. Thank you
 
Solution
"Windows NT could not start because the following file is missing or corrupt: <windows root="">\System32\Ntoskrnl.exe</windows> . ... The error occurs as a result of one or more causes: corrupt boot volume, corrupted or deleted ntoskrnl.exe file, invalid boot.ini configuration or missing drivers for hard disk controller."

as for the others...

"SYS file errors are typically caused by faulty hardware or corrupt device driver files. Because of the importance of Volsnap.sys in the functionality of MSDN Disc 2085 and other Windows functions, any corruption or damage to this file can create critical system errors in the form of a "blue screen of death" (BSOD)"

Sources...

TwilightRavens

Reputable
Mar 17, 2017
341
0
4,960
"Windows NT could not start because the following file is missing or corrupt: <windows root="">\System32\Ntoskrnl.exe</windows> . ... The error occurs as a result of one or more causes: corrupt boot volume, corrupted or deleted ntoskrnl.exe file, invalid boot.ini configuration or missing drivers for hard disk controller."

as for the others...

"SYS file errors are typically caused by faulty hardware or corrupt device driver files. Because of the importance of Volsnap.sys in the functionality of MSDN Disc 2085 and other Windows functions, any corruption or damage to this file can create critical system errors in the form of a "blue screen of death" (BSOD)"

Sources: http://www.solvusoft.com/en/files/bsod-blue-screen-error/sys/windows/microsoft/msdn-disc-2085/volsnap-sys/
http://www.wikihow.com/Fix-Ntoskrnl.exe-Missing-or-Corrupt-Error

Hope this helps
 
Solution

Eddiecb

Prominent
Apr 11, 2017
3
0
510



Thank you twilightRavens