Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The first steps for troubleshooting a BSoD would be to remove the overclock on the system, and run MemTest overnight at the least, but preferably for 24 hours.
If the RAM checks out, next you would boot into safe mode and attempt to replicate the problem. If the BSoD does not occur in safe mode, then boot normally, reproduce the BSoD and use BlueScreenView to discover whether a system driver, or third-party hardware driver is causing the problem.
the easy solution would be to turn off the powersaving features in Bios (C/G/S/P states,speedstep, EIST).
Historically disabling sleep states was a mandatory first step before attempting any overclock.
i would turn them all off retest then turn them on one at a time to find witch state is causing problem.
If your Bios allows you might try Ocing you sleep states to be compatible with your OC( maybe called "CPU Features" or"Adaptive Mode").
or use offset voltage to keep your sleep states stable with OC.
Kmode and driver crash hint at P state but the blue screen only tells what it was doing when it crash (not why it crashed)and your almost always using drivers.
And that 65 temp is suspiciously cold for stress test