Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

ntoskrnl.exe BSOD's - Windows 10


  • Please log in to reply
1 reply to this topic

#1 Tony1987

Tony1987

  • Members
  • 1 posts
  • OFFLINE
  •  

Posted 09 October 2016 - 10:19 PM

Hey everyone,

 

Need help with an issue I've been having since I got my new rig from CyberPowerPC. Since I got it a couple months ago, it's been getting BSOD errors at weird times, mostly while playing either World of Warcraft or Overwatch. Using WhoCrashed, it's pointing me in the direction of the ntoskrnl.exe every time. I'm wondering if it's memory issues or what the case is.

 

One thing I do realize is that the BIOS is from 2014, but I do not feel safe updating it, as again, I'm not an expert.

 

Now I am no expert with computers, so I am not sure where to take and look to try and solve this annoying problem.

 

Any help would be appreciated.

 

System info is below, and for some reason this forum will not upload the .dmp files, so I'll grab what info I can from WhoCrashed.

 

OS Name Microsoft Windows 10 Home
Version 10.0.14393 Build 14393
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-IMQHR7N
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-78LMT-S2
System Type x64-based PC
Processor AMD FX™-4300 Quad-Core Processor, 3800 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F6, 2014-01-09
SMBIOS Version 2.4
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale Canada
Hardware Abstraction Layer Version = "10.0.14393.206"
Time Zone Atlantic Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 8.00 GB
Available Physical Memory 6.04 GB
Total Virtual Memory 9.25 GB
Available Virtual Memory 6.94 GB
Page File Space 1.25 GB
Page File C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
 
 
On Mon 2016-10-10 2:13:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100916-46750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8012C552A6F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
 
On Mon 2016-10-10 2:13:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8012C552A6F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
 
NOTE: The two above happened at the same time, hence why I included the second one below the first one. Just in casethere was any relevance.
 
 
On Sat 2016-10-08 6:17:38 AM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\100816-22328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0xA (0x226F, 0xFF, 0x1, 0xFFFFF80264D29086)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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. 

 

 

 

EDIT: BlueScreenView info removed, debug info from WinDBG

 

Microsoft ® Windows Debugger Version 10.0.14321.1024 X86
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\Walters & Walsh\Desktop\100916-46750-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.206.amd64fre.rs1_release.160915-0644
Machine Name:
Kernel base = 0xfffff801`2c405000 PsLoadedModuleList = 0xfffff801`2c709080
Debug session time: Sun Oct  9 23:13:27.703 2016 (UTC - 3:00)
System Uptime: 1 days 0:41:59.405
Loading Kernel Symbols
.
 
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
 
..............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1E, {ffffffffc0000096, fffff8012c552a6f, 0, 0}
 
Probably caused by : memory_corruption
 
Followup:     memory_corruption
---------
 
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8012c552a6f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 400
 
BUILD_VERSION_STRING:  10.0.14393.206 (rs1_release.160915-0644)
 
SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.
 
SYSTEM_PRODUCT_NAME:  GA-78LMT-S2
 
BIOS_VENDOR:  Award Software International, Inc.
 
BIOS_VERSION:  F6
 
BIOS_DATE:  01/09/2014
 
BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.
 
BASEBOARD_PRODUCT:  GA-78LMT-S2
 
BASEBOARD_VERSION:  sex
 
DUMP_TYPE:  2
 
BUGCHECK_P1: ffffffffc0000096
 
BUGCHECK_P2: fffff8012c552a6f
 
BUGCHECK_P3: 0
 
BUGCHECK_P4: 0
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.
 
FAULTING_IP: 
nt!KiDpcInterrupt+cf
fffff801`2c552a6f 440f22c1        mov     cr8,rcx
 
BUGCHECK_STR:  0x1E_c0000096
 
CPU_COUNT: 4
 
CPU_MHZ: ee9
 
CPU_VENDOR:  AuthenticAMD
 
CPU_FAMILY: 15
 
CPU_MODEL: 2
 
CPU_STEPPING: 0
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
 
PROCESS_NAME:  Battle.net.exe
 
CURRENT_IRQL:  2
 
ANALYSIS_SESSION_HOST:  DESKTOP-IMQHR7N
 
ANALYSIS_SESSION_TIME:  10-10-2016 18:29:10.0275
 
ANALYSIS_VERSION: 10.0.14321.1024 x86fre
 
LAST_CONTROL_TRANSFER:  from fffff8012c578286 to fffff8012c54f2b0
 
STACK_TEXT:  
ffff9980`61dea0b8 fffff801`2c578286 : 00000000`0000001e ffffffff`c0000096 fffff801`2c552a6f 00000000`00000000 : nt!KeBugCheckEx
ffff9980`61dea0c0 fffff801`2c55a502 : 00000000`00000000 00000000`05f68000 00000000`00000001 ffffd40c`00000000 : nt! ?? ::FNODOBFM::`string'+0x19df6
ffff9980`61dea790 fffff801`2c5587bd : ffffd40c`63418080 ffff9980`61deab00 00000000`0158ef00 00000000`6f3245d0 : nt!KiExceptionDispatch+0xc2
ffff9980`61dea970 fffff801`2c552a6f : ffffd40c`63519800 ffffd40c`63509800 ffff9980`00000000 ffffd40c`6156cc00 : nt!KiGeneralProtectionFault+0xfd
ffff9980`61deab00 00000000`62c7d3a6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcf
00000000`018fc198 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x62c7d3a6
 
 
STACK_COMMAND:  kb
 
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8012c45ca50-fffff8012c45ca51  2 bytes - nt!MmDeleteKernelStack+2a0
[ 80 fa:00 90 ]
    fffff8012c4730f9-fffff8012c4730fa  2 bytes - nt!MiCompletePrivateZeroFault+519 (+0x166a9)
[ 80 fa:00 90 ]
    fffff8012c47318f-fffff8012c473191  3 bytes - nt!MiCompletePrivateZeroFault+5af (+0x96)
[ 40 fb f6:80 7d fb ]
    fffff8012c474b87-fffff8012c474b88  2 bytes - nt!MiGetPage+97 (+0x19f8)
[ 80 fa:00 90 ]
    fffff8012c474d9a-fffff8012c474d9b  2 bytes - nt!MiGetFreeOrZeroPage+7a (+0x213)
[ 80 fa:00 90 ]
11 errors : !nt (fffff8012c45ca50-fffff8012c474d9b)
 
MODULE_NAME: memory_corruption
 
IMAGE_NAME:  memory_corruption
 
FOLLOWUP_NAME:  memory_corruption
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
MEMORY_CORRUPTOR:  LARGE
 
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
 
BUCKET_ID:  MEMORY_CORRUPTION_LARGE
 
PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE
 
TARGET_TIME:  2016-10-10T02:13:27.000Z
 
OSBUILD:  14393
 
OSSERVICEPACK:  206
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  784
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-09-15 13:21:59
 
BUILDDATESTAMP_STR:  160915-0644
 
BUILDLAB_STR:  rs1_release
 
BUILDOSVER_STR:  10.0.14393.206
 
ANALYSIS_SESSION_ELAPSED_TIME: 2c9e
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:memory_corruption_large
 
FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
 
Followup:     memory_corruption
 

Edited by Tony1987, 10 October 2016 - 06:31 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:11 PM

Posted 11 October 2016 - 07:13 AM

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Beyond this I have these 5 suggestions while waiting for a reply:
1.  Get ALL available Windows Updates.  It may take several trips to get them all
2.  Get ALL available, compatible updates for your system from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website
4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If all of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users