DENNIS PETTIT asked on February 22, 2013. Status: Answered & Closed.
BSOD Error Due To Ntoskrnl.exe
» Recently I have been facing some problems due to BSOD. I have used the BlueScreenView and found out that the reason is ntoskrnl.exe, and to my knowledge I think it cannot be upgraded. Could you please tell me what is the issue.
Ntoskrnl.exe is a critical process in the boot-up cycle of your computer. It can be altered by the w32.bolzano virus and its variants. If this process appears in WinTasks, please update your virus definitions immediately. This virus often causes BSOD.
Generally speaking, the exe file runs programs and can be used as a delivery system for viruses or other malicious programs. Viruses often reside to .exe files (such as VirTool:Win32/Injector.DY); they can be running in the background, infecting or compromising the computer.
As it is a blue screen error, I suggest to use DLL Suite to deal with it. Just because it has a comprehensive feature to fix the Exe virus infection and sys bsod.
DLL Suite is an all around DLL file Error fixer. It enables you to fix all kinds of dll errors, such as .dll missing errors, .sys blue screen of death (BSOD), .exe virus infection, and supports for free download of missing DLL files, whether you are using Windows 7, Windows 8, Windows Vista and Windows XP PCs, including both 32-bit and 64-bit operating systems.
MICHAEL WHEELER replied on February 28, 2013
- JOHN WORTHAM replied on February 22, 2013: » These crashes were caused by memory corruption (probably a driver). Please run Memory test and Driver verifier to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.In other words STOP!!!
- SILVANA VELEZ replied on February 22, 2013: » ntoskrnl.exe is the kernel (core) of the Windows Operating System.It's also protected by the Windows System File Checker.So, if it were to blame, you'd be experiencing many more problems than just the occasional BSOD.That means we have to look elsewhere for the cause......
- JEAN QUINNETT replied on February 23, 2013: » TEMPORARILY uninstall Daemon Tools and ZoneAlarm.If it stops the BSOD's, then you know what you've gotta do.
You don't have Daemon Tools, it's Alcohol 120% that has the offending sptd.sys driver. AMD OverDrive is also a possible BSOD cause. Disable it in the AMD Control Center in order to test it.
- DENNIS PETTIT replied on February 26, 2013: » Thanks for the reply. For now, I have removed the Alcohol and also the SPTD drivers, I will check if there are any issues and let you know, also I would run the drivers verify utility and post the results.
DLL Q & A You Might Like:
- Application Error 0xc0000022 For All Exe Files »
- Kernelbase.dll Error Opening Excel In Windows 7 »
- Bingsurrogate.exe Using More Space »
- Explorer.exe Keep Crashing When Searching »
- EPSXe.exe Has Stopped Working »
- SearchProtocolHost.exe And SearchIndexer.exe Causing High CPU Usage »
- Setdefault.exe 0x000007b Error At Startup »