|
Post by Andrew on Nov 6, 2020 22:07:35 GMT
I'm getting the Blue Screen of Death issues whilst racing that I had a few months back. It happened twice this evening, once in qualy and once in the first race so I figured there wasn't much point in carrying on to the second (hour long) race as it would just happen again.
It happens without warning, the game just freezes and there's a loud buzzing noise in the headset for a few seconds whilst the PC bluescreens then does a soft reset. I've looked at the logs and nothing is obvious as to why. Win 10 is up to date as is rFactor 2. A google search doesn't reveal anything obvious either.
Any ideas as to what I can do to try and fix it?
|
|
|
Post by cageyh on Nov 6, 2020 22:16:07 GMT
You still running an overclock? Try dropping it slightly, as it may be unstable.
|
|
|
Post by Andrew on Nov 8, 2020 12:27:30 GMT
Cheers Kev, I hadn't thought of that so I've stress tested the PC over the last few days with OCCT and it's done a full 24 hour test perfectly. The overclock is a mild one but at least it's ruled the hardware out.
After a bit of reading around the subject I've managed to read the memory.dmp files and both issues when playing rF2 were caused by a file called ntoskrnl.exe so I'll have a read up on that later today.
|
|
|
Post by scoops on Nov 8, 2020 12:46:31 GMT
|
|
|
Post by Andrew on Nov 8, 2020 14:26:12 GMT
Cheers Simon, I actually stumbled on that page too. It seems memory is the prime issue for this type of fault so I've removed the (mild) overclock and set the memory to it's default speed rather than the XMP profile it was set too. I've also flashed the BIOS to the latest version so I'll leave it now and see if it bluescreens in rF2 this week. Fingers crossed.
Are you still snowed under with work Simon, or are you able to do any Friday night racing now?
|
|
|
Post by scoops on Nov 8, 2020 14:59:47 GMT
Work is piling up but that’s no surprise but I’ve also been asked to take on a second directors post which I’m trying to get up to speed with. Hoping to get back to racing soon but just need to be sure I’ve got my head around things.
Now isn’t the time for me to mess things up.
|
|
|
Post by Si on Nov 8, 2020 15:06:56 GMT
Worse case, is that you have duff memory. What brand do you have? I'm running Corsair memory. In the past I had issues with Crucial memory modules. I always make sure that the memory is running at the recommend clock speed. e.g. Mine are 1200 MHz, so I make sure that they are set to that speed in the BIOS.
|
|
|
Post by Andrew on Nov 8, 2020 16:38:53 GMT
Its Corsair DDR4 Vengeance LPX Black, (PC4-24000 3000). According to the specs it's designed to run with XMP 2.0 at 1.35V which is exactly how it's been configured since I built the PC. The BIOS detects it as 2133 though which is pretty odd but that's what I got it running at now just to try to find out if it is the RAM that's at fault.
|
|
|
Post by Andrew on Nov 8, 2020 16:42:34 GMT
Work is piling up but that’s no surprise but I’ve also been asked to take on a second directors post which I’m trying to get up to speed with. Hoping to get back to racing soon but just need to be sure I’ve got my head around things. Now isn’t the time for me to mess things up. Fair enough Simon, best of luck with it. I had a break from racing over the summer as didn't have the headspace for it with the stress of being made redundant from BA and then rejoining the RAF, so I can completely empathise.
|
|
|
Post by Si on Nov 8, 2020 16:44:55 GMT
I use this to see what I have. Probably tells you what you already know anyway. It should tell you the clock speed of your RAM and what you are actually running it at. www.hwinfo.com/
|
|
|
Post by scoops on Nov 8, 2020 21:35:17 GMT
Thanks Andrew not having headspace is exactly how I feel.
|
|