Solved

Running games of secondary HDD causes BSOD

Hey there, I have a massive problem, I keep getting Bluescreens while running games like GTA, or Ghost Recon of my secondary HDD. I thought it was the ram at first, but after the whole night of testing from a memtest86 bootable USB ruled that option out(at least I think so). I run a:
- Aorus Z270X Gaming 7 Mobo
- i7 7700K
- 16GB Corsair Vengeance LPX 3200MHz
- Asus Rog STRIX 1080 11gbps

and also I am including my minidump file:

Quote:
Microsoft (R) Windows Debugger Version 10.0.17030.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Vonti\Desktop\121017-6093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`a688e000 PsLoadedModuleList = 0xfffff801`a6bf0010
Debug session time: Sun Dec 10 04:32:18.200 2017 (UTC + 0:00)
System Uptime: 0 days 0:00:11.872
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, ffffc60090d93b30, 25c9dba1, fffff801a68f5a7f}

Probably caused by : hardware ( nt!KiDoubleFaultAbort+b3 )

Followup: MachineOwner
---------

nt!KeBugCheckEx:
fffff801`a69f20e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc600`90d939f0=000000000000007f
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffc60090d93b30
Arg3: 0000000025c9dba1
Arg4: fffff801a68f5a7f

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.98 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 8

BUGCHECK_P2: ffffc60090d93b30

BUGCHECK_P3: 25c9dba1

BUGCHECK_P4: fffff801a68f5a7f

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: ffffc60090d93b30 -- (.trap 0xffffc60090d93b30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffc60090d8b180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801a68f5a7f rsp=0000000025c9dba1 rbp=ffffc38925c9dd80
r8=0000000000000001 r9=0000000000000000 r10=0000000000000008
r11=ffffc38925c9dda8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KiExitDispatcher+0xf:
fffff801`a68f5a7f 57 push rdi
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: R3D_DEV1L

ANALYSIS_SESSION_TIME: 12-10-2017 15:04:50.0473

ANALYSIS_VERSION: 10.0.17030.1002 amd64fre

BAD_STACK_POINTER: 0000000025c9dba1

MISALIGNED_IP:
nt!KiExitDispatcher+f
fffff801`a68f5a7f 57 push rdi

UNALIGNED_STACK_POINTER: 0000000025c9dba1

LAST_CONTROL_TRANSFER: from fffff801a69fd9e9 to fffff801a69f20e0

STACK_TEXT:
ffffc600`90d939e8 fffff801`a69fd9e9 : 00000000`0000007f 00000000`00000008 ffffc600`90d93b30 00000000`25c9dba1 : nt!KeBugCheckEx
ffffc600`90d939f0 fffff801`a69fb5f3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc600`90d93b30 fffff801`a68f5a7f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb3
00000000`25c9dba1 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExitDispatcher+0xf


THREAD_SHA1_HASH_MOD_FUNC: bbce3dfa97c1e30477ecd93f875ff171f3bd6e99

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2849482e80ec2c8569304044fc196bf30d16b189

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b3
fffff801`a69fb5f3 90 nop

FAULT_INSTR_CODE: 6666c390

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b3

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.16299.98

STACK_COMMAND: .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

PRIMARY_PROBLEM_CLASS: IP_MISALIGNED

TARGET_TIME: 2017-12-10T04:32:18.000Z

OSBUILD: 16299

OSSERVICEPACK: 98

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-11-26 11:49:20

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.98

ANALYSIS_SESSION_ELAPSED_TIME: 84b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:ip_misaligned

FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup: MachineOwner
---------



I reckon it must be the HDD, because when I am streaming PUBG, or CSGO(games that are on my SSD) @60fps there are absolutely no issues even when playing (and streaming)for 6-7h straight. Thanks for the help guys, much appreciated!
10 answers Last reply Best Answer
More about running games secondary hdd bsod
  1. Have you ran a CHKDSK or checked SMART data w/ software from HDD manufacturer or HDTune? If your games run fine on on the SSD, and other tests like RAM that you tried are fine, it likely is related to the HDD. Any chance to reinstall a game to the SSD to verify.
  2. So I have done the chkdsk for D: - no errors came up, and played a game of PUBG, and another BSOD came up, I am attaching the minidump file:

    Quote:

    Microsoft (R) Windows Debugger Version 10.0.17030.1002 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Vonti\Desktop\121017-6140-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 16299 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 16299.15.amd64fre.rs3_release.170928-1534
    Machine Name:
    Kernel base = 0xfffff802`d0c92000 PsLoadedModuleList = 0xfffff802`d0ff4010
    Debug session time: Sun Dec 10 16:18:02.212 2017 (UTC + 0:00)
    System Uptime: 0 days 1:59:36.883
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff802d97a483c, 0, ffffffffffffffff}

    *** WARNING: Unable to verify timestamp for BEDaisy.sys
    *** ERROR: Module load completed but symbols could not be loaded for BEDaisy.sys
    Probably caused by : BEDaisy.sys ( BEDaisy+5483c )

    Followup: MachineOwner
    ---------

    nt!KeBugCheckEx:
    fffff802`d0df60e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffe8d`922ddcd0=000000000000001e
    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff802d97a483c, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10.0.16299.98 (WinBuild.160101.0800)

    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

    SYSTEM_PRODUCT_NAME: Z270X-Gaming 7

    SYSTEM_SKU: Default string

    SYSTEM_VERSION: Default string

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: F7

    BIOS_DATE: 07/06/2017

    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

    BASEBOARD_PRODUCT: Z270X-Gaming 7

    BASEBOARD_VERSION: x.x

    DUMP_TYPE: 2

    BUGCHECK_P1: ffffffffc0000005

    BUGCHECK_P2: fffff802d97a483c

    BUGCHECK_P3: 0

    BUGCHECK_P4: ffffffffffffffff

    READ_ADDRESS: fffff802d108a380: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    ffffffffffffffff

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

    FAULTING_IP:
    BEDaisy+5483c
    fffff802`d97a483c 8b0b mov ecx,dword ptr [rbx]

    EXCEPTION_PARAMETER2: ffffffffffffffff

    BUGCHECK_STR: 0x1E_c0000005_R

    CPU_COUNT: 8

    CPU_MHZ: 1068

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXPNP: 1 (!blackboxpnp)


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: BEService.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: R3D_DEV1L

    ANALYSIS_SESSION_TIME: 12-10-2017 16:27:17.0204

    ANALYSIS_VERSION: 10.0.17030.1002 amd64fre

    EXCEPTION_RECORD: 000000000006f211 -- (.exr 0x6f211)
    Cannot read Exception record @ 000000000006f211

    LAST_CONTROL_TRANSFER: from fffff802d0e100d1 to fffff802d0df60e0

    STACK_TEXT:
    fffffe8d`922ddcc8 fffff802`d0e100d1 : 00000000`0000001e ffffffff`c0000005 fffff802`d97a483c 00000000`00000000 : nt!KeBugCheckEx
    fffffe8d`922ddcd0 fffff802`d0e01ace : 00000000`0006f211 ffff980c`e51b2700 ffff980c`d2842700 fffffe8d`922de501 : nt!KiDispatchException+0x162931
    fffffe8d`922de380 fffff802`d0dffb34 : fffffe8d`00000000 00001f80`000000b0 00000000`00191209 00000001`401cdbd1 : nt!KiExceptionDispatch+0xce
    fffffe8d`922de560 fffff802`d97a483c : 00000000`00000000 ffff980c`e51b2700 00000000`00000293 00000000`00000000 : nt!KiGeneralProtectionFault+0xf4
    fffffe8d`922de6ff 00000000`00000000 : ffff980c`e51b2700 00000000`00000293 00000000`00000000 00000000`00000001 : BEDaisy+0x5483c


    THREAD_SHA1_HASH_MOD_FUNC: 31965ff46ebac2589ce577942f9e2a4343b3ae8e

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c486db9fa999ec0454761fb8128d65e039f8e49e

    THREAD_SHA1_HASH_MOD: 8a900b4b61cfd51e45dbf0f25bce95f411efd6ac

    FOLLOWUP_IP:
    BEDaisy+5483c
    fffff802`d97a483c 8b0b mov ecx,dword ptr [rbx]

    FAULT_INSTR_CODE: 81660b8b

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: BEDaisy+5483c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: BEDaisy

    IMAGE_NAME: BEDaisy.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5a027199

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 5483c

    FAILURE_BUCKET_ID: 0x1E_c0000005_R_BEDaisy!unknown_function

    BUCKET_ID: 0x1E_c0000005_R_BEDaisy!unknown_function

    PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_BEDaisy!unknown_function

    TARGET_TIME: 2017-12-10T16:18:02.000Z

    OSBUILD: 16299

    OSSERVICEPACK: 98

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2017-11-26 11:49:20

    BUILDDATESTAMP_STR: 160101.0800

    BUILDLAB_STR: WinBuild

    BUILDOSVER_STR: 10.0.16299.98

    ANALYSIS_SESSION_ELAPSED_TIME: 1581

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_bedaisy!unknown_function

    FAILURE_ID_HASH: {0bd42fc6-2120-bd14-0c57-c0ddc7336714}

    Followup: MachineOwner
    ---------

    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff802d97a483c, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10.0.16299.98 (WinBuild.160101.0800)

    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

    SYSTEM_PRODUCT_NAME: Z270X-Gaming 7

    SYSTEM_SKU: Default string

    SYSTEM_VERSION: Default string

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: F7

    BIOS_DATE: 07/06/2017

    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

    BASEBOARD_PRODUCT: Z270X-Gaming 7

    BASEBOARD_VERSION: x.x

    DUMP_TYPE: 2

    BUGCHECK_P1: ffffffffc0000005

    BUGCHECK_P2: fffff802d97a483c

    BUGCHECK_P3: 0

    BUGCHECK_P4: ffffffffffffffff

    READ_ADDRESS: Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    ffffffffffffffff

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

    FAULTING_IP:
    BEDaisy+5483c
    fffff802`d97a483c 8b0b mov ecx,dword ptr [rbx]

    EXCEPTION_PARAMETER2: ffffffffffffffff

    BUGCHECK_STR: 0x1E_c0000005_R

    CPU_COUNT: 8

    CPU_MHZ: 1068

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 5E'00000000 (cache) 5E'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXPNP: 1 (!blackboxpnp)


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: BEService.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: R3D_DEV1L

    ANALYSIS_SESSION_TIME: 12-10-2017 16:27:23.0110

    ANALYSIS_VERSION: 10.0.17030.1002 amd64fre

    EXCEPTION_RECORD: 000000000006f211 -- (.exr 0x6f211)
    Cannot read Exception record @ 000000000006f211

    LAST_CONTROL_TRANSFER: from fffff802d0e100d1 to fffff802d0df60e0

    STACK_TEXT:
    fffffe8d`922ddcc8 fffff802`d0e100d1 : 00000000`0000001e ffffffff`c0000005 fffff802`d97a483c 00000000`00000000 : nt!KeBugCheckEx
    fffffe8d`922ddcd0 fffff802`d0e01ace : 00000000`0006f211 ffff980c`e51b2700 ffff980c`d2842700 fffffe8d`922de501 : nt!KiDispatchException+0x162931
    fffffe8d`922de380 fffff802`d0dffb34 : fffffe8d`00000000 00001f80`000000b0 00000000`00191209 00000001`401cdbd1 : nt!KiExceptionDispatch+0xce
    fffffe8d`922de560 fffff802`d97a483c : 00000000`00000000 ffff980c`e51b2700 00000000`00000293 00000000`00000000 : nt!KiGeneralProtectionFault+0xf4
    fffffe8d`922de6ff 00000000`00000000 : ffff980c`e51b2700 00000000`00000293 00000000`00000000 00000000`00000001 : BEDaisy+0x5483c


    THREAD_SHA1_HASH_MOD_FUNC: 31965ff46ebac2589ce577942f9e2a4343b3ae8e

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c486db9fa999ec0454761fb8128d65e039f8e49e

    THREAD_SHA1_HASH_MOD: 8a900b4b61cfd51e45dbf0f25bce95f411efd6ac

    FOLLOWUP_IP:
    BEDaisy+5483c
    fffff802`d97a483c 8b0b mov ecx,dword ptr [rbx]

    FAULT_INSTR_CODE: 81660b8b

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: BEDaisy+5483c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: BEDaisy

    IMAGE_NAME: BEDaisy.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5a027199

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 5483c

    FAILURE_BUCKET_ID: 0x1E_c0000005_R_BEDaisy!unknown_function

    BUCKET_ID: 0x1E_c0000005_R_BEDaisy!unknown_function

    PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_BEDaisy!unknown_function

    TARGET_TIME: 2017-12-10T16:18:02.000Z

    OSBUILD: 16299

    OSSERVICEPACK: 98

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2017-11-26 11:49:20

    BUILDDATESTAMP_STR: 160101.0800

    BUILDLAB_STR: WinBuild

    BUILDOSVER_STR: 10.0.16299.98

    ANALYSIS_SESSION_ELAPSED_TIME: 156c

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_bedaisy!unknown_function

    FAILURE_ID_HASH: {0bd42fc6-2120-bd14-0c57-c0ddc7336714}

    Followup: MachineOwner
    ---------
  3. Looks like it software related, a good chance anyways. BEDaisy.sys seems to cause the BSOD in PUBG for quite a few. Seems like a known issue and not HDD related. UEFI updated? Do you have battle eye installed? Seems to cause it.
  4. So I downclocked my 7700K from 5.0 to 4.8 and the temperature went down by 16-19 degrees and been playing and streaming since and there hasn’t been a problem. Looks like I haven’t won the silicone lottery, but that’s strange because the aida64 stability test worked fine on the 5.0 clock for like 4h. It’s 0.2ghz so literally nothing, so I guess that’s the solution. I’ll play a game of my HDD soon and post the results how that goes. Thanks for the interest!
  5. Best answer
    first bugcheck looks like the machine rebooted and was still too hot when the CPU restarted.
    ie system up timer was 8 seconds and the cpu got a double fault and told windows to shutdown with the bugcheck.


    Jamaison said:
    So I downclocked my 7700K from 5.0 to 4.8 and the temperature went down by 16-19 degrees and been playing and streaming since and there hasn’t been a problem. Looks like I haven’t won the silicone lottery, but that’s strange because the aida64 stability test worked fine on the 5.0 clock for like 4h. It’s 0.2ghz so literally nothing, so I guess that’s the solution. I’ll play a game of my HDD soon and post the results how that goes. Thanks for the interest!
  6. Second day w/o any problems. I guess the clock was just a tad too high. All working fine now thanks!
  7. Jamaison said:
    Second day w/o any problems. I guess the clock was just a tad too high. All working fine now thanks!


    Well you forgot to check one of basic things - and those are temps.
    Always look for those when getting exit during playing.
  8. salerhino said:
    Jamaison said:
    Second day w/o any problems. I guess the clock was just a tad too high. All working fine now thanks!


    Well you forgot to check one of basic things - and those are temps.
    Always look for those when getting exit during playing.


    Well I was using THIS temperature guide and my max was 82 degrees when stress testing on prime95 or AIDA64(and even those worked for a couple of hours with no issues). When gaming those temperatures did not go that high, so it makes me wonder.
  9. why does the debugger show a cpu frequency of
    CPU_MHZ: 1068
    for a i7 7700k which should be base 4.2 ghz to 4.5 ghz ?

    any chance the cpu was hot and the cpu was being throttled by the BIOS?
    maybe the thermal drivers for the chipset are not installed?
  10. johnbl said:
    why does the debugger show a cpu frequency of
    CPU_MHZ: 1068
    for a i7 7700k which should be base 4.2 ghz to 4.5 ghz ?

    any chance the cpu was hot and the cpu was being throttled by the BIOS?
    maybe the thermal drivers for the chipset are not installed?


    It could be that I was trying to get a steady 5.0GHz OC with a DeepCool Captain 120EX(120mm). It has been a couple of days and haven't encountered that problem again. So my guess is that the CPU was overheating because of the overclock.
Ask a new question

Read More

Blue Screen Games Hard Drives