Various BSOD problems- 0x109, 0x1a, 0x01 etc. ntoskrnl.exe seems to be cause?

oddlyenough

Honorable
Feb 5, 2014
11
0
10,510
Hello,

I've been encountering an issue with a computer running Windows 7 Enterprise 64-bit and am not sure where to look. I never catch it in the act, but when the user gets to the computer in the morning, the computer appears to have restarted and is on System Restore.

I am going to attach a screenshot of the .dmp files in BlueScreenView. All of the filenames in the bottom pane are pretty much identical through all of the .dmp files. It seems to be caused by ntoskrnl.exe, but have no idea why.

http://s000.tinyupload.com/index.php?file_id=08207403975742420268

This is what I have tried:

***Switching out the current RAM with that out of an identical, working computer. No improvement.
***Did the same with the video card. No improvement.
***Reformatted the hard drive and installed software again.
(As an aside - I am absolutely, 100% CERTAIN that the software is not causing conflict. The user had the same software always, this issue began about a month ago out of the blue with no software or hardware changes).
***It's on a corporate network, endpoint protection software is forced by AD. 100% certain as well, there is no malware, viruses etc - as mentioned, it was just reimaged yesterday and here's the problem again.
***All drivers are up-to-date, Windows Update up-to-date, devices with missing drivers have been disabled.

Here are the specs:
500 GB HDD
Intel Xeon Processor
8 GB RAM
Nvidia Quadro 600 GPU
Edit: 331.82 is driver version - seems to be stable on all other identical systems

The issue happens every evening. The odd thing is, the computer is idle, and has been for hours and it still happens. Seems to always be in the evening, but nothing happens then. The user - and everyone else - is gone. No other users report issues at that time. No corporate network policies, anything.

Any ideas? I'm about to throw this thing out the window.

Thanks so much.

 
Solution
in general, a bugcheck in ntoskrnl.exe will be cause by 3rd party device drivers that are making incorrect system calls that are handled by the windows kernel (ntoskrnl)

in your bugchecks shown in you screen capture all the different bugchecks are caused by the same location in your copy of the ntoskrnl.exe. I would suggest that your local copy of ntoskrnl.exe is corrupted.

run cmd.exe as a admin
sfc.exe /scannow <-- this will scan and attempt to find and fix the corruption.

if you want to post one of your memory dump files on a cloud server like skydrive I will have the windows debugger check the memory image of the kernel for memory corruption.
or you can install the windows debugger standalone kit and...


Oh good, its not just me who is having problems with ntoskrnl.exe :fou: Welcome to my world. I'm getting blue screens that are caused by that same file. Maybe we both have a virus or something? My problem only seems to happen when I play online games though.
 
in general, a bugcheck in ntoskrnl.exe will be cause by 3rd party device drivers that are making incorrect system calls that are handled by the windows kernel (ntoskrnl)

in your bugchecks shown in you screen capture all the different bugchecks are caused by the same location in your copy of the ntoskrnl.exe. I would suggest that your local copy of ntoskrnl.exe is corrupted.

run cmd.exe as a admin
sfc.exe /scannow <-- this will scan and attempt to find and fix the corruption.

if you want to post one of your memory dump files on a cloud server like skydrive I will have the windows debugger check the memory image of the kernel for memory corruption.
or you can install the windows debugger standalone kit and load the crash dump file and run the following command
!for_each_module !chkimg @#ModuleName

This will check the core microsoft windows files against the known files on the microsoft symbol servers
and report error for corrupted files. (it also reports errors for files it does not have matching versions of)


 
Solution