NTOSKRNL.exe driver failing

Hi Experts,

 I am trying to troubleshoot a BSOD. I have copied the memory.dmp from the server 2012R2 .

 When I run the Windows debugging tool, I get the output (See attachment). Please advise me the best way to analyse the file.

 I am not sure why I can't get the whole dump info.
 I am also getting a Symbol Loading Error Summary report while running the Windows Debug tool(*64 & *32)

This is the error from the application log
011615-65218-01.dmp      16/01/2015 14:58:56      PAGE_FAULT_IN_NONPAGED_AREA      0x00000050      fffff6fb`40000000      00000000`00000000      00000000`00000000      00000000`00000006      ntoskrnl.exe      ntoskrnl.exe+150aa0                              x64      ntoskrnl.exe+150aa0                              C:\Windows\Minidump\011615-65218-01.dmp      1      15      9600      294,296      16/01/2015 15:00:38      

PS: Please see the attached Memory.DMP info as well

This is what MSDN reckons.

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.
The following parameters are displayed on the blue screen.
Memory address referenced
0: Read operation
1: Write operation
Address that referenced memory (if known)
If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.
Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.
Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.
Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.
Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.
Typically, this address is in freed memory or is simply invalid.
This cannot be protected by a try - except handler -- it can only be protected by a probe.

 Many Thanks,

Who is Participating?
backtrace would be nice.
try nirsoft bluescreenview - maybe it makes one from your dmp, so you can skip the step of making another crash...
la-tempestadAuthor Commented:
One more thing I suspect this crash/restart of the server started after we installed the Tiger Communication service(Tiger 2020 Pro), but before going back to the vendor, I need to make sure it is not the Server 2012 issue. Since the installation of this application, we were getting "Application Hang" errors for all Tiger related exe's.

------------------------------------------application log --------------------------------------------------------------------------------------------------------------
The program Tigersys.exe version stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: d78
Start Time: 01cfb15fb4c4651c
Termination Time: 3
Application Path: D:\tig2020\Tigersys.exe
Report Id: 0084c44d-1d53-11e4-80c6-0050568a4b56
Faulting package full name:
 Faulting package-relative application ID:

The program TigBackup.exe version stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 2f8
Start Time: 01cfb162530089c7
Termination Time: 4294967295
Application Path: D:\tig2020\Utility\TigBackup.exe
Report Id: c7ae4ae7-1d55-11e4-80c7-0050568a4b56
Faulting package full name:
 Faulting package-relative application ID:


Faulting application name: install_reader10_en_air_gtbp_chra_aih.exe, version:, time stamp: 0x4e8ced69
Faulting module name: install_reader10_en_air_gtbp_chra_aih.exe, version:, time stamp: 0x4e8ced69
Exception code: 0xc0000005
Fault offset: 0x0000435b
Faulting process id: 0x360
Faulting application start time: 0x01cfb175f42eca5b
Faulting application path: C:\Users\SA_Tiger-Avaya\AppData\Local\Temp\install_reader10_en_air_gtbp_chra_aih.exe
Faulting module path: C:\Users\SA_Tiger-Avaya\AppData\Local\Temp\install_reader10_en_air_gtbp_chra_aih.exe
Report Id: 67a7b32a-1d69-11e4-80c8-0050568a4b56
Faulting package full name:
Faulting package-relative application ID:

thanks again
How userland process could even remotely cause page fault in the very core of system kernel?

I dont see memory dump attached. Make the short 64k minidump and attach that here.
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

la-tempestadAuthor Commented:
Actually that is the memory dump(C:\Windows\MEMORY.DMP) which I have extracted by using Windows Debug Tool.
How do you want the minidump to be extracted/attached here?

la-tempestadAuthor Commented:
I have found out the problem with the crash,it was due to one of the windows updates.
The vendor re-installed the software with the latest version and since then there isn't any crash at all.

thanks for all your inputs anyway.

la-tempestadAuthor Commented:
Its a good tool for finding memory dumps.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.