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

frequent ntoskrnl.exe BSOD, possibly related to games?


  • Please log in to reply
5 replies to this topic

#1 daffy1234

daffy1234

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 26 December 2016 - 11:36 PM

I've been getting blue screen crashes a lot since I recently started playing a game (Astroneer, if you're wondering) yet the issue seems to be unrelated to the game, since it's happened in other games as well. I'm not 100% confident that games are causing it, it might simply be a coincidence that all three crashes happened during gameplay, but there seems to be a correlation.
 
All three crashes are linked to ntoskrnl.exe at address 6f400, but strangely with different bug check codes for each of them.
 
Thanks for any help.
 
Here's the BlueScreenView dump of the crashes.
 
==================================================
Dump File         : 122616-27128-01.dmp
Crash Time        : 12/26/2016 11:13:23 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`003fe526
Parameter 3       : 00000000`00000001
Parameter 4       : 00000000`003fe826
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23418 (win7sp1_ldr.160408-2045)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122616-27128-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 406,464
Dump File Time    : 12/26/2016 11:14:53 PM
==================================================
 
==================================================
Dump File         : 122616-20139-01.dmp
Crash Time        : 12/26/2016 5:02:22 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041201
Parameter 2       : fffff680`0051f9f8
Parameter 3       : da700003`f8615867
Parameter 4       : fffffa80`1a300280
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23418 (win7sp1_ldr.160408-2045)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122616-20139-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 406,440
Dump File Time    : 12/26/2016 5:04:21 PM
==================================================
 
==================================================
Dump File         : 122616-80122-01.dmp
Crash Time        : 12/26/2016 3:46:47 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff6fc`400e8478
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`02ccf6f6
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23418 (win7sp1_ldr.160408-2045)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122616-80122-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 406,400
Dump File Time    : 12/26/2016 3:49:16 AM
==================================================

Edit: Moved topic from Windows 7 to the more appropriate forum. ~ Animal

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,866 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:46 AM

Posted 27 December 2016 - 08:53 AM

How to receive help diagnosing Blue Screens and Windows crashes - http://www.bleepingcomputer.com/forums/topic176011.html

 

Louis



#3 daffy1234

daffy1234
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 27 December 2016 - 01:49 PM

Hey Louis, thanks for responding.

 

I'm running into an issue on step 4. The debugging tools aren't installing properly.

 

"A problem occurred while installing selected Windows SDK components.

 
Installation of the "Microsoft Windows SDK for Windows 7" product has reported the following error: Please refer to Samples\Setup\HTML\ConfigDetails.htm document for further information."
 
Said file does not exist, by the way.
 
When starting up the installer, I get this message. http://i.imgur.com/K8JSJ3x.png
The given link does not exist, and my attempt to install .NET framework 4 didn't work because I apparently already have a newer version installed.
 
A log file was created by the installer, which I will share if you think it will be helpful. It's quite large.

Edited by daffy1234, 27 December 2016 - 01:50 PM.


#4 daffy1234

daffy1234
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 27 December 2016 - 09:56 PM

I just did some updates to windows, one of which modified ntoskrnl.exe, and while playing the game it all seemed fine, then I got another blue screen error. This time, a forth and again different stop code.

 

==================================================

Dump File         : 122716-25880-01.dmp
Crash Time        : 12/27/2016 9:46:48 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`02df1367
Parameter 3       : fffff880`0d767a40
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23572 (win7sp1_ldr.161011-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+70400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122716-25880-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 406,408
Dump File Time    : 12/27/2016 9:48:05 PM
==================================================


#5 daffy1234

daffy1234
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 29 December 2016 - 12:46 AM

I just figured out how to install those debugging tools. Turns out you need to uninstall Redistributable C++ 2010 and let it install its own version. Never would have guessed that in a million years. Anyway, here's the result from the lastest blue screen.

Spoiler


#6 daffy1234

daffy1234
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 30 December 2016 - 09:10 PM

I installed all the windows updates I could and the problem seemed to go away. I didn't say so immediately because I got another blue screen right after, but this time it seemed to be related to some svchost.exe process. But that seemed to be an anomaly and things seem to be working normally now. I'll make another topic if this issue shows up again.

 

Thanks






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users