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

Couple of random BSODs while gaming


  • Please log in to reply
1 reply to this topic

#1 jambokaos87

jambokaos87

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:08:53 AM

Posted 26 April 2015 - 09:20 AM

Hi guys,

 

Getting a couple of random BSOD's while gaming.. Seems to be totally random but the BSOD's are the same.

Here is the data from BlueScreenView from them both:

 

==================================================
Dump File         : 042615-8408-01.dmp
Crash Time        : 26/04/2015 00:23:50
Bug Check String  : DRIVER_CORRUPTED_EXPOOL
Bug Check Code    : 0x000000c5
Parameter 1       : 00000002`00000001
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`035ff9cc
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72a40
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18798 (win7sp1_gdr.150316-1654)
Processor         : x64
Crash Address     : ntoskrnl.exe+72a40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\042615-8408-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 350,784
Dump File Time    : 26/04/2015 00:24:36
==================================================
 
==================================================
Dump File         : 042015-7753-01.dmp
Crash Time        : 20/04/2015 08:25:01
Bug Check String  : DRIVER_CORRUPTED_EXPOOL
Bug Check Code    : 0x000000c5
Parameter 1       : 00000002`00000001
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`035f69cc
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72a40
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18798 (win7sp1_gdr.150316-1654)
Processor         : x64
Crash Address     : ntoskrnl.exe+72a40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\042015-7753-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 344,880
Dump File Time    : 20/04/2015 08:25:44
==================================================


BC AdBot (Login to Remove)

 


#2 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 7,123 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:53 AM

Posted 26 April 2015 - 06:40 PM

Blue screens happen from time to time and often when a computer is being worked hard, as in gaming. You have had two, six days apart, and it is annoying - especially if you were just beating seven bells out of an opponent  - but I wouldn't worry too much about it unless it becomes more common.

 

It is possible that your ntoskrnl file is corrupted and it might be worth your while running sfc /scannow to see if it needs repair. To do this, click 'Start' and type 'CMD into the search box. It will show 'Command.exe'. RIGHT click on this and select 'Run as administrator'. A black window with white text will open and all you need to do is type 'sfc /scannow' at the cursor (without the ' ', and notice the space after 'sfc') and press enter.

 

If it finds any problems it will attempt to fix them, and at the end you will be able to see what it has done. Re-boot and you should be good to go.

 

Chris Cosgrove






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users