Jump to content

Super weird bluescreen

Go to solution Solved by the-griffin,

Thanks a lot guys, but I fixed it on my own by installing windows 10.

Hey, 

I have a relativly big problem with my pc right now. I installed a new game from steam, I also had to update .NET Framework, short time after that I got the bluescreen. I can use my pc for a while, but when I try to start a game the bluescreen will pop up. Even System recovery doesnt work. 

 

CPU: Ryzen 1600x  (no oc)

GPU: GeForce GTX 960

RAM:16GB Corsair 3000mhz

M.2 ssd

WD blue 2TB

Win 8.1 Pro (i knowMicrosoft stopped support for new cpu's, but I got around by using using a patch by "Zeffy")

 

Hope you can help me  fix it

greetings, Lars

20180115_160010.jpg

Link to comment
Share on other sites

Link to post
Share on other sites

Do you have the most recent Drivers from Nvidia?

It might fix the issue.

 

Also is it any game or the new game that causes it?

Link to comment
Share on other sites

Link to post
Share on other sites

we just had another one of these last week show up. 2 users experienced the same issue. they are trying to get to the bottom of it. were you one of them? i don't remember the screen names.

[FS][US] Corsair H115i 280mm AIO-AMD $60+shipping

 

 

System specs:
Asus Prime X370 Pro - Custom EKWB CPU/GPU 2x360 1x240 soft loop - Ryzen 1700X - Corsair Vengeance RGB 2x16GB - Plextor 512 NVMe + 2TB SU800 - EVGA GTX1080ti - LianLi PC11 Dynamic
 

Link to comment
Share on other sites

Link to post
Share on other sites

Nope, I created my Account yesterday (01.31) my bluescreen also showed up yesterday the first time. 

Link to comment
Share on other sites

Link to post
Share on other sites

10 hours ago, Egg-Roll said:

Do you have the most recent Drivers from Nvidia?

It might fix the issue.

 

Also is it any game or the new game that causes it?

Yep, I have the newest drivers, I'll try to reinstall .NET Framework somehow. Well every game (which is using .NET Framework) causes this bluescreen. 

Link to comment
Share on other sites

Link to post
Share on other sites

If I overclock my ram over 1600 MHz, I get this exact same blue screen after running the Aida 64 Memory Stress Test for about 3 minutes. However, if I have it running at 1600 MHz or lower, the test runs fine without fail.

Main Rig

Spoiler

CPU: Intel Core i7 920 @ 4.0GHz

Motherboard: ASUS P6T SE

RAM: 10GB OCZ DDR3 (Triple Channel) @ 1600MHz

GPU: NVIDIA GeForce GTX 770 2GB

Case: Antec GX500 Window

Storage: 2 x 500GB Samsung 7200RPM HDD

PSU: Coolmax 1200W ATX 80 PLUS GOLD

Cooling: DEEPCOOL GAMMAXX 300

Teamwolf Mechanical Gaming KeyboardASUS ROG GX850 Laser Mouse

Main Laptop

Spoiler

Alienware 17 (2014)

(Intel Core i7 4710mq @ 2.5GHz - 3.5Ghz (Turbo) | 16GB DDR3 RAM | 4GB AMD m290x Dedicated Graphics - 1TB SSHD)

XP Machine (build in progress...)

Spoiler

CPU: AMD Athlon 64 3000+ @ 1.8GHz

Motherboard: DFI LANPARTY NF4

RAM: 1GB OCZ DDR (Dual Channel) @ 400MHz

GPU: NVIDIA GeForce GT610 2GB Synergy Edition

PSU: BFG 450W

Apple iMac (2009)

Spoiler

CPU: Intel Core2Duo @ 2.66GHz

RAM: 6GB DDR3 @ 1333MHz

GPU: NVIDIA GeForce 9400 256MB

RetroPie Machine (Linux Mint & RetroPie)

Spoiler

CPU: Intel Core2Duo @ 3.0GHz

RAM: 7GB DDR2 @ 800MHz

GPU: AMD Radeon HD 3650

 

Link to comment
Share on other sites

Link to post
Share on other sites

2 hours ago, EMAGDNIM said:

If I overclock my ram over 1600 MHz, I get this exact same blue screen after running the Aida 64 Memory Stress Test for about 3 minutes. However, if I have it running at 1600 MHz or lower, the test runs fine without fail.

I dont think thats the Problem, my System ran for a long time at 3000MHz ram without problems

Link to comment
Share on other sites

Link to post
Share on other sites

1 hour ago, the-griffin said:

I dont think thats the Problem, my System ran for a long time at 3000MHz ram without problems

Still try it. Something like a driver or windows update or something could have caused that to become unstable I guess.

Just go into your bios and disable the XMP profile.

If that doesn't fix it, you can just turn it back on.

Easy peezy thing to test.

Link to comment
Share on other sites

Link to post
Share on other sites

Thanks a lot guys, but I fixed it on my own by installing windows 10.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×