Windows 10 BSOD on Windows 10 Multiple Times a Day

O

OrigamiShawn

Extraordinary Member
Joined
Aug 29, 2014
Messages
48
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

Solution
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
*************************************************************************
***...
Sort by date Sort by votes
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:
Link Removed

Try thinning out your apps.

Anything thats old or no longer used please remove.
 
Upvote 0 Downvote
Passed Intel Diagnostic. After reading this I checked my temps during a huge fight, and my CPU temps were at 100c! So I decided that maybe I put too much thermal paste on about a week ago. Rubbed off old paste, used the dot method this time, and now I'm getting a max temp of 78c No BSOD yet. I'll keep you posted
 
Last edited:
Upvote 0 Downvote
Fantastic! I really hope we got it this time and you can can enjoy your gaming proper.

Any problems please post back and all the best!
 
Upvote 0 Downvote
TDR issue came back. I made sure every driver was up to date using Driver Easy Pro, cleaned the hell out of my apps and drives, tried at least 5 different display drivers, and reinstalled Windows 10 with no luck. Any ideas?
 

Attachments

Upvote 0 Downvote
OrigamiShawn said:
I made sure every driver was up to date using Driver Easy Pro
Click to expand...
Hmm... We do not recommend applications such as these 'Driver finders' as they can just as easily install the wrong driver and can be more trouble than they are worth.

I suggest you read up on TDR's and what their main causes are:
Timeout Detection & Recovery (TDR)

Something to consider is to back off the gpu clocks slightly and see if that helps. (reduce the MHz)
 
Last edited:
Upvote 0 Downvote
Excellent!

Hehe would you believe i just spent the night hunting down a bsod on my system... Hopefully , like yours, it's all sorted but only time will tell.
 
Upvote 0 Downvote
At least you have a lot of knowledge about computers. I honestly want to get in to this kind of work someday. Glad you got everything sorted! No crash for me yet I'll post again if I get any more issues. Thank you so much
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

K
  • Solved
Windows 11 BSOD several times a day
Replies
4
Views
847
Mike
  • Solved
Windows 10 BSOD 3-4 times a day :-(
Replies
4
Views
3K
kemical
V
  • Solved
Windows 8 BSOD sometimes a couple of times a day
Replies
7
Views
3K
kemical
W
  • Solved
Windows 7 BSOD up to 6 times a day.
Replies
12
Views
3K
usasma
P
  • Solved
Windows 7 BSOD Multiple times a day.
Replies
6
Views
2K
PeteFantastic
P