BSOD on Windows 10 Multiple Times a Day

OrigamiShawn

Senior Member
Hello. I BSOD mostly when playing video games, but it can happen about ten seconds after logging in to Windows occasionally. I'd like to know what the problem is. I put new thermal paste on my CPU today (temps were a bit high) and also replaced the GPU cable to try and solve the issue, but I still BSOD. I have a suspicion it's my GPU or ram.

Here are my specs:
- Intel Core i7 4790K CPU
- 16GB 1600MHz Memory
- NVIDIA GTX 780 Ti 3GB
- 120mm CPU Liquid Cooling
- 120GB Samsung 840 EVO SSD
- 1TB 7200RPM Storage HDD
- ASUS Z97 Chipset Motherboard
- 750W Corsair CX PSU
- DVD-R/RW/CD-R/RW
- Windows 10 64bit
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe581df72c028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner
Hi,
bugcheck 124 is usually associated with overclocking and overheating so do stop any overclocks and check your temps.

Also please ensure any apps or drivers are the latest versions.

Code:
===============================================================================
Common Platform Error Record @ ffffe581df72c028
-------------------------------------------------------------------------------
Record Id     : 01d41e0f00ce2801
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/17/2018 21:35:07 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe581df72c0a8
Section       @ ffffe581df72c180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe581df72c0f0
Section       @ ffffe581df72c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000005
CPU Id        : c3 06 03 00 00 08 10 05 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe581df72c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe581df72c138
Section       @ ffffe581df72c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 5 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00007ff68da8931b
  Misc.       : 0x00007ff68da8931b
The above error check on your CPU leads me to believe you might be needing a bios update and you do have updates available for your board:
Your current bios:
BIOS_VERSION: 2202

BIOS_DATE: 07/11/2014

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z97-C
Update available:
Version 2801
2016/03/
Z97-C
BIOS 2801
Improve system stability
Z97-C Driver & Tools | Motherboards | ASUS Global

If your unsure on how to flash the bios, leave it.

I'm running late for an appointment but will be back in a couple of hours.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,
I'm back. So if your unsure how to proceed with the bios flash take it either to a shop or ask a friend who has experience.

Although bios flashing isn't as risky as it once was it still does carry some risk. If the flash is somehow interrupted then it can affect the motherboard so care is needed.
 

OrigamiShawn

Senior Member
Hi,
I'm back. So if your unsure how to proceed with the bios flash take it either to a shop or ask a friend who has experience.

Although bios flashing isn't as risky as it once was it still does carry some risk. If the flash is somehow interrupted then it can affect the motherboard so care is needed.
Thank you for this info! I looked up a tutorial online on how to flash my BIOS and updated it to the latest version. I haven't had a BSOD yet, but I think I had a TDR. My screens go black and fans get set to 100% right after loading in to the game Guild Wars 2 but I can still talk to my buddy on discord while it's happening (This was happening before updating the BIOS so it didn't cause this). I don't overclock anything, and when I updated the BIOS I changed all the settings to default. Here's a new W7F from after the bios update
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff800074e9378, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
Hi,
nice job with the bios update.

Although the above dump file isn't opening properly I can see enough details via whats called a stack trace to see that the Nvidia gpu driver was the cause with this bsod.

You sent three dump files, one is a bugcheck 124 and two are like the above.

You may have some corruption within the gpu driver and Windows 10.

To clear the gpu corruption, uninstall the current driver using the DDU or Display Driver Uninstaller.

You must run this in safe mode (disconnect from the net too just so windows won't install a driver via Windows updates)

Once back in windows pop your driver (update to the latest version if need be) back on windows.

Run these scans which hopefully will cure any corruption within the system:

Open an administrators command prompt (you can find command prompt in the start menu under 'windows system', simply right click on it and run as admin). Type (or copy and paste):
sfc /scannow
Press enter and await results.

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

Hope this helps. Please post any new dump files after making the above changes.
 

OrigamiShawn

Senior Member
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff800074e9378, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
Hi,
nice job with the bios update.

Although the above dump file isn't opening properly I can see enough details via whats called a stack trace to see that the Nvidia gpu driver was the cause with this bsod.

You sent three dump files, one is a bugcheck 124 and two are like the above.

You may have some corruption within the gpu driver and Windows 10.

To clear the gpu corruption, uninstall the current driver using the DDU or Display Driver Uninstaller.

You must run this in safe mode (disconnect from the net too just so windows won't install a driver via Windows updates)

Once back in windows pop your driver (update to the latest version if need be) back on windows.

Run these scans which hopefully will cure any corruption within the system:

Open an administrators command prompt (you can find command prompt in the start menu under 'windows system', simply right click on it and run as admin). Type (or copy and paste):
sfc /scannow
Press enter and await results.

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

Hope this helps. Please post any new dump files after making the above changes.
Done all above. No corruption found from command prompt scans. I crashed again right after loading in to Gw2 when I realized I hadn't checked to see if I had a TDR delay still set (I didn't.). Set value to 60 and BAM! I'll post any new BSOD dumps.
BAM.png
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,
I had another look over your drivers and you could do with updating your chipset and storage drivers:

iaStorA.sys Fri Apr 4 00:00:05 2014: Intel RST (Rapid Storage Technology) driver. A later version can be found under the heading of SATA in the driver section:
Z97-C Driver & Tools | Motherboards | ASUS Global

I couldn't actually find your chipset drivers to see a date so try updating anyway.

Look under the chipset heading and you'll see drivers for both chipset and 'engine management', you want both.
Z97-C Driver & Tools | Motherboards | ASUS Global

The trouble is with TDR's is that they can caused by a multitude of issues and tracking the cause down can sometimes take a bit of trial and error.

Consider trying earlier drivers.

3D.com carries copies of recent Nvidia drivers so you can see if the issue is with every driver.
Videocards - NVIDIA GeForce Windows 7 | 8 | 10

See if the gpu will complete the burn in test on furmark:
Furmark
 

OrigamiShawn

Senior Member
Hi,
I had another look over your drivers and you could do with updating your chipset and storage drivers:

iaStorA.sys Fri Apr 4 00:00:05 2014: Intel RST (Rapid Storage Technology) driver. A later version can be found under the heading of SATA in the driver section:
Z97-C Driver & Tools | Motherboards | ASUS Global

I couldn't actually find your chipset drivers to see a date so try updating anyway.

Look under the chipset heading and you'll see drivers for both chipset and 'engine management', you want both.
Z97-C Driver & Tools | Motherboards | ASUS Global

The trouble is with TDR's is that they can caused by a multitude of issues and tracking the cause down can sometimes take a bit of trial and error.

Consider trying earlier drivers.

3D.com carries copies of recent Nvidia drivers so you can see if the issue is with every driver.
Videocards - NVIDIA GeForce Windows 7 | 8 | 10

See if the gpu will complete the burn in test on furmark:
Furmark
Updated RST and chipset drivers. I got in to Guild Wars 2 for about 5 minutes this time and then the same deal. I still haven't had a BSOD so I think that issue has been resolved. I can play Battlefield 1 for hours now with no problem, but I can't get Guild Wars 2 to run properly. FurMark came back with normal results. Should I consider buying a new GPU?
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Should I consider buying a new GPU?
Not yet.. :) If you ran Furmark ok then chances are your card is fine, we just need to find the culprit.

So if Battlefield 1 runs ok, what about other games? (apart from guild wars 2)

Does guild wars 2 need patching perhaps or re-installing?

Did you try using an older driver as i suggested above?

I know your running a 780Ti but can you post the make and model of your PSU please. (edit: Apologies I see you posted the psu in your first post)
 
Last edited:

OrigamiShawn

Senior Member
I reinstalled the game with no luck. Then installed an old driver version (397.64). This seems to have fixed my problem! I haven't had a black screen after 30 minutes, but I'll post back later if anything happens. Thanks for your help!
 
Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
You don't mention which game it was but is it the one which usually gives you issues? (GW2?)

It could be that you may have to try more than one older driver before you find a total fix. I would also use the DDU periodically to ensure corruption doesn't build up.

Also are you running anything, app wise, which runs alongside the games you play?

As an example, if you use skype to chat to other members of your party does it need updating?

I see you have a USB mic attached, perhaps this needs updating? All i'm saying is check everything as i said earlier TDR's can caused by almost anything.
 

OrigamiShawn

Senior Member
My apologies. I hadn't finished installing my game before loading in to the new area so I'm pretty sure that's why I crashed. Been playing for about 3 hours with no problem. If the problem shows up again I feel like I can tackle it better on my own now (thanks to you!). You can close this thread. Again, thank you for all your help. :D
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Your very welcome Shawn and to be honest we never close threads so do pop back if issues arise again.

All the best! :)
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff910cf332c028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner
Code:
===============================================================================
Common Platform Error Record @ ffff910cf332c028
-------------------------------------------------------------------------------
Record Id     : 01d42061731ba5c5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/20/2018 20:44:23 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff910cf332c0a8
Section       @ ffff910cf332c180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000007

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff910cf332c0f0
Section       @ ffff910cf332c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000007
CPU Id        : c3 06 03 00 00 08 10 07 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffff910cf332c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff910cf332c138
Section       @ ffff910cf332c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 7 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00007ff6f81177b6
  Misc.       : 0x00007ff6f81177b6
Hi,
when your gaming have you checked your temperatures. I don't mean when it's quiet and not much happening, I mean when all hell has broken loose.. I know it can be awkward to suddenly stop mid battle and check on temps but believe me when i say it's worth doing.
I had a similar issue to this a few years ago and it wasn't until i checked the cpu temps mid battle (Crysis 3 beta) that i could see i was overheating ( i was actually shocked to see the temps so high).

Try running the Intel diagnostic app and see if anything pops up:
Download Intel® Processor Diagnostic Tool

Try thinning out your apps.

Anything thats old or no longer used please remove.
 
Top