Is my PSU causing only in-game BSOD's?

[SchrodingersCat_]

I have been plagued by random BSOD's when I am playing demanding games. I am using Crysis 3 currently to test stability.

System Specs:

CPU: FX-8350

GPU: Stock NVidia GTX 770

PSU: Specs here - Why I bought it, it was 80+ Bronze, fairly inexpensive, had good reviews at the time. This PSU is my main suspect as to causing the BSOD's

MOBO: MSI 990FXA-GD80V2

Drivers: All updated to the latest including: BIOS, Nvidia Drivers, Chipset, Audio, Lan, and RAID.

Details of the problem:

So problems only started showing up after I updated my graphics card from a HD7870 to a GTX770. I posted a thread on this forum here asking if people thought it would be enough, well I have to second guess that because of these BSOD's which never happened on my 8350 and 7870 combo. With the FX-8350 and GTX 770, I can usually games play from anywhere from 5-15 min before a total hard shutdown (like pulling the power cable), or a BSOD. I have really searched hard for a problem that could be something other than the PSU, and got some interesting results:

Stress tester used: AIDA64 Extreme

Conditions:

CPU: Pass

FPU: Pass

Cache: Pass

Memory: Pass

GPU: Pass

CPU + FPU: Pass

CPU + FPU + Cache: Pass

CPU + FPU + Cache + Memory: Fail

CPU + FPU + Cache + Memory + GPU: Fail

Stress tester used: Prime95 Small FFT

Results:

It ran for a few minutes, then failed with multiple errors. Errors are here.

This is really baffling me, I think that the PSU is to blame for the in-game crashes, but the Prime95 results are a real curveball, unless there is something that I don't know about power supplies, the 650w should definitely be able to push an 8350. The CPU was purchased used, and I stress tested it after I installed it, with no errors, but I have never had any problems in-game with it until I put the new GPU in.

If the power supply is to blame, this is the one I would get to replace it.

Concerning Overheating:

No overclocks are applied.

All clockspeeds and voltages are at stock/auto.

My CPU cooler is a Hyper 212 EVO

My CPU is not overheating.

DUMP FILES:

#1

#2

EDIT:

I also remember some really weird wattage numbers from HWMonitor, on my 8350, it said the max power was like 34w or something during a stress test. Not sure why.

If anyone can help me figure out what is going on here, I would be eternally grateful.

[ionbasa]

8350? 

With my experience they usually require a higher load line calibration setting.

 

Are you overclocking?

 

Also since you are getting bsods there should be minidump files located under "%systemroot%\minidump"

If you can copy them to a temporary folder on your desktop, zip the folder an attach it to your post here in the thread and I can take a look at it.

[killcomic]

Have you tried downclocking your CPU? Sound almost like an error when you overclock. So perhaps dropping your speed below the stock might help. Also, you can try setting the voltage and CPU settings manually. Your PSU is giving you enough power, I'd say.

[SchrodingersCat_]

8350? 

With my experience they usually require a higher load line calibration setting.

 

Are you overclocking?

 

Also since you are getting bsods there should be minidump files located under "%systemroot%\minidump"

If you can copy them to a temporary folder on your desktop, zip the folder an attach it to your post here in the thread and I can take a look at it.

I didn't think about LLC, I will mess with that and get back to you, in the meantime, the dump files have been added to the original post, and no I am not overclocking. Also, like I said, the CPU was working fine until I put the new GPU in.

 

Have you tried downclocking your CPU? Sound almost like an error when you overclock. So perhaps dropping your speed below the stock might help. Also, you can try setting the voltage and CPU settings manually. Your PSU is giving you enough power, I'd say.

I have tried bumping up the voltage a bit, but I haven't messed with it enough to call it yet. I am not overclocking, and I was about to downclock as well, it is just past midnight here, so I will do it tomorrow.

[ionbasa]

I didn't think about LLC, I will mess with that and get back to you, in the meantime, the dump files have been added to the original post, and no I am not overclocking. Also, like I said, the CPU was working fine until I put the new GPU in.

 

I have tried bumping up the voltage a bit, but I haven't messed with it enough to call it yet. I am not overclocking, and I was about to downclock as well, it is just past midnight here, so I will do it tomorrow.

The first BSOD was caused by the GPU driver, uninstall all old drivers, and during the re-install of the latest non-beta driver make sure to select "clean install"

 

The second BSOD didn't get 'caught' by the system, so I suspect a memory issue. Do you know how to run a memory test with Memtest86++?

Here is a tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

Try at least 6 hours and see if it finds any issues.

 

Also in case you want to see the bug-check output:

 

 

EDIT:

 

Both were caused by GPU drivers, make sure you have the amd drivers uninstalled also.

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`034566d0Debug session time: Tue Jan  7 23:35:49.549 2014 (UTC - 5:00)System Uptime: 0 days 5:01:24.875********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: fffffa800af60290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff88004057d88, The pointer into responsible device driver module (e.g. owner tag).Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.Arg4: 000000000000000d, Optional internal context dependent data.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2FAULTING_IP: atikmpag+bd88fffff880`04057d88 4883ec28        sub     rsp,28hDEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULTCUSTOMER_CRASH_COUNT:  1BUGCHECK_STR:  0x116PROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  fffff880`044fb758 fffff880`04149140 : 00000000`00000116 fffffa80`0af60290 fffff880`04057d88 00000000`00000000 : nt!KeBugCheckExfffff880`044fb760 fffff880`04148ec7 : fffff880`04057d88 fffffa80`0af60290 00000000`00000000 fffffa80`08c43010 : dxgkrnl!TdrBugcheckOnTimeout+0xecfffff880`044fb7a0 fffff880`11f97f13 : fffffa80`0af60290 00000000`00000000 00000000`00000000 fffffa80`08c43010 : dxgkrnl!TdrIsRecoveryRequired+0x21ffffff880`044fb7d0 fffff880`11fc5ed6 : 00000000`00000000 00000000`0011af6c fffff880`044fb930 00000000`00000102 : dxgmms1!VidSchiReportHwHang+0x40bfffff880`044fb8b0 fffff880`11fc191a : fffffa80`08c43010 ffffffff`feced300 00000000`00000002 fffffa80`08c60230 : dxgmms1!VidSchWaitForCompletionEvent+0x196fffff880`044fb8f0 fffff880`11fc01b0 : fffffa80`08c43010 00000000`00000002 fffff880`11fbff3c 00000000`00000000 : dxgmms1!VidSchiWaitForDrainFlipQueue+0x92fffff880`044fb9e0 fffff880`11fc047a : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x4cfffff880`044fba10 fffff880`11f932d2 : ffffffff`ff676980 fffffa80`08c43010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23efffff880`044fbab0 fffff880`11fbfff6 : 00000000`00000000 fffffa80`07004970 00000000`00000080 fffffa80`08c43010 : dxgmms1!VidSchiScheduleCommandToRun+0x1dafffff880`044fbbc0 fffff800`035252ea : 00000000`fffffc32 fffffa80`08634b50 fffffa80`06ce3040 fffffa80`08634b50 : dxgmms1!VidSchiWorkerThread+0xbafffff880`044fbc00 fffff800`032798e6 : fffff880`009ea180 fffffa80`08634b50 fffff880`009f50c0 fffffa80`086bed10 : nt!PspSystemThreadStartup+0x5afffff880`044fbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND:  .bugcheck ; kbFOLLOWUP_IP: atikmpag+bd88fffff880`04057d88 4883ec28        sub     rsp,28hSYMBOL_NAME:  atikmpag+bd88FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: atikmpagIMAGE_NAME:  atikmpag.sysDEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sysBUCKET_ID:  X64_0x116_IMAGE_atikmpag.sysFollowup: MachineOwner--------- 

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364a6d0Debug session time: Sat Jan 11 19:10:10.695 2014 (UTC - 5:00)System Uptime: 0 days 0:31:36.771********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003.  This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG.  This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG.  This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff800034ad622, The address that the exception occurred atArg3: fffff880009a9868, Exception Record AddressArg4: fffff880009a90c0, Context Record AddressDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlapEXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KxWaitForLockOwnerShip+12fffff800`034ad622 48890a          mov     qword ptr [rdx],rcxEXCEPTION_RECORD:  fffff880009a9868 -- (.exr 0xfffff880009a9868)ExceptionAddress: fffff800034ad622 (nt!KxWaitForLockOwnerShip+0x0000000000000012)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT:  fffff880009a90c0 -- (.cxr 0xfffff880009a90c0)rax=0000000000000001 rbx=00000000000139ed rcx=fffff880009a9b28rdx=4000000000000000 rsi=fffffa80065d4d08 rdi=fffff880009a9b28rip=fffff800034ad622 rsp=fffff880009a9aa0 rbp=00000000000000ff r8=0000000000000000  r9=0000000000000000 r10=fffffa80065d4d28r11=000000000000000f r12=000000000000000d r13=fffffa80003adc70r14=0000000000000100 r15=fffff800035f7e80iopl=0         nv up ei ng nz na pe nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282nt!KxWaitForLockOwnerShip+0x12:fffff800`034ad622 48890a          mov     qword ptr [rdx],rcx ds:002b:40000000`00000000=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100GetUlongFromAddress: unable to read from fffff800036b41c0 ffffffffffffffff FOLLOWUP_IP: nt!KxWaitForLockOwnerShip+12fffff800`034ad622 48890a          mov     qword ptr [rdx],rcxBUGCHECK_STR:  0x7ELAST_CONTROL_TRANSFER:  from fffff8000343fb9f to fffff800034ad622STACK_TEXT:  fffff880`009a9aa0 fffff800`0343fb9f : 00000000`000139ed 00000000`000000ec 00000000`0000000c fffffa80`065d2f30 : nt!KxWaitForLockOwnerShip+0x12fffff880`009a9ad0 fffff800`037192ea : fffffa80`066e0450 00000000`00000080 fffffa80`066e09e0 fffff800`0346d8d9 : nt!MmZeroPageThread+0x4a2fffff880`009a9c00 fffff800`0346d8e6 : fffff800`035f7e80 fffffa80`066e0450 fffff800`03605cc0 db1d44a6`502600d0 : nt!PspSystemThreadStartup+0x5afffff880`009a9c40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9870 00000000`00000000 : nt!KxStartSystemThread+0x16SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  521ea035STACK_COMMAND:  .cxr 0xfffff880009a90c0 ; kbFAILURE_BUCKET_ID:  X64_0x7E_nt!KxWaitForLockOwnerShip+12BUCKET_ID:  X64_0x7E_nt!KxWaitForLockOwnerShip+12Followup: MachineOwner--------- 

[SchrodingersCat_]

The first BSOD was caused by the GPU driver, uninstall all old drivers, and during the re-install of the latest non-beta driver make sure to select "clean install"

 

The second BSOD didn't get 'caught' by the system, so I suspect a memory issue. Do you know how to run a memory test with Memtest86++?

Here is a tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

Try at least 6 hours and see if it finds any issues.

 

Also in case you want to see the bug-check output:

 

 

EDIT:

 

Both were caused by GPU drivers, make sure you have the amd drivers uninstalled also.

When I installed the new GPU, I had to update my BIOS, which was a success, then I installed the GeForce Drivers, then I uninstalled AMD drivers. However, I DID NOT do a clean install. I will uninstall and clean install when I get home. Also, I forgot to mention that the FX-8350 and 7870 combo were running on the BIOS that my Motherboard came with, but I had to update it when I installed the new GPU. Is it possible that the new BIOS configured itself incorrectly or is causing some of these problems?

 

Also, while I did not run memtest86+ because I didn't have enough time, I did run windows memory diagnostics, and no problems were found.

 

Thanks again for the detailed instructions and replies!

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`034566d0Debug session time: Tue Jan  7 23:35:49.549 2014 (UTC - 5:00)System Uptime: 0 days 5:01:24.875********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: fffffa800af60290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff88004057d88, The pointer into responsible device driver module (e.g. owner tag).Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.Arg4: 000000000000000d, Optional internal context dependent data.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2FAULTING_IP: atikmpag+bd88fffff880`04057d88 4883ec28        sub     rsp,28hDEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULTCUSTOMER_CRASH_COUNT:  1BUGCHECK_STR:  0x116PROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  fffff880`044fb758 fffff880`04149140 : 00000000`00000116 fffffa80`0af60290 fffff880`04057d88 00000000`00000000 : nt!KeBugCheckExfffff880`044fb760 fffff880`04148ec7 : fffff880`04057d88 fffffa80`0af60290 00000000`00000000 fffffa80`08c43010 : dxgkrnl!TdrBugcheckOnTimeout+0xecfffff880`044fb7a0 fffff880`11f97f13 : fffffa80`0af60290 00000000`00000000 00000000`00000000 fffffa80`08c43010 : dxgkrnl!TdrIsRecoveryRequired+0x21ffffff880`044fb7d0 fffff880`11fc5ed6 : 00000000`00000000 00000000`0011af6c fffff880`044fb930 00000000`00000102 : dxgmms1!VidSchiReportHwHang+0x40bfffff880`044fb8b0 fffff880`11fc191a : fffffa80`08c43010 ffffffff`feced300 00000000`00000002 fffffa80`08c60230 : dxgmms1!VidSchWaitForCompletionEvent+0x196fffff880`044fb8f0 fffff880`11fc01b0 : fffffa80`08c43010 00000000`00000002 fffff880`11fbff3c 00000000`00000000 : dxgmms1!VidSchiWaitForDrainFlipQueue+0x92fffff880`044fb9e0 fffff880`11fc047a : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x4cfffff880`044fba10 fffff880`11f932d2 : ffffffff`ff676980 fffffa80`08c43010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23efffff880`044fbab0 fffff880`11fbfff6 : 00000000`00000000 fffffa80`07004970 00000000`00000080 fffffa80`08c43010 : dxgmms1!VidSchiScheduleCommandToRun+0x1dafffff880`044fbbc0 fffff800`035252ea : 00000000`fffffc32 fffffa80`08634b50 fffffa80`06ce3040 fffffa80`08634b50 : dxgmms1!VidSchiWorkerThread+0xbafffff880`044fbc00 fffff800`032798e6 : fffff880`009ea180 fffffa80`08634b50 fffff880`009f50c0 fffffa80`086bed10 : nt!PspSystemThreadStartup+0x5afffff880`044fbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND:  .bugcheck ; kbFOLLOWUP_IP: atikmpag+bd88fffff880`04057d88 4883ec28        sub     rsp,28hSYMBOL_NAME:  atikmpag+bd88FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: atikmpagIMAGE_NAME:  atikmpag.sysDEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sysBUCKET_ID:  X64_0x116_IMAGE_atikmpag.sysFollowup: MachineOwner--------- 

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364a6d0Debug session time: Sat Jan 11 19:10:10.695 2014 (UTC - 5:00)System Uptime: 0 days 0:31:36.771********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003.  This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG.  This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG.  This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff800034ad622, The address that the exception occurred atArg3: fffff880009a9868, Exception Record AddressArg4: fffff880009a90c0, Context Record AddressDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlapEXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KxWaitForLockOwnerShip+12fffff800`034ad622 48890a          mov     qword ptr [rdx],rcxEXCEPTION_RECORD:  fffff880009a9868 -- (.exr 0xfffff880009a9868)ExceptionAddress: fffff800034ad622 (nt!KxWaitForLockOwnerShip+0x0000000000000012)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT:  fffff880009a90c0 -- (.cxr 0xfffff880009a90c0)rax=0000000000000001 rbx=00000000000139ed rcx=fffff880009a9b28rdx=4000000000000000 rsi=fffffa80065d4d08 rdi=fffff880009a9b28rip=fffff800034ad622 rsp=fffff880009a9aa0 rbp=00000000000000ff r8=0000000000000000  r9=0000000000000000 r10=fffffa80065d4d28r11=000000000000000f r12=000000000000000d r13=fffffa80003adc70r14=0000000000000100 r15=fffff800035f7e80iopl=0         nv up ei ng nz na pe nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282nt!KxWaitForLockOwnerShip+0x12:fffff800`034ad622 48890a          mov     qword ptr [rdx],rcx ds:002b:40000000`00000000=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100GetUlongFromAddress: unable to read from fffff800036b41c0 ffffffffffffffff FOLLOWUP_IP: nt!KxWaitForLockOwnerShip+12fffff800`034ad622 48890a          mov     qword ptr [rdx],rcxBUGCHECK_STR:  0x7ELAST_CONTROL_TRANSFER:  from fffff8000343fb9f to fffff800034ad622STACK_TEXT:  fffff880`009a9aa0 fffff800`0343fb9f : 00000000`000139ed 00000000`000000ec 00000000`0000000c fffffa80`065d2f30 : nt!KxWaitForLockOwnerShip+0x12fffff880`009a9ad0 fffff800`037192ea : fffffa80`066e0450 00000000`00000080 fffffa80`066e09e0 fffff800`0346d8d9 : nt!MmZeroPageThread+0x4a2fffff880`009a9c00 fffff800`0346d8e6 : fffff800`035f7e80 fffffa80`066e0450 fffff800`03605cc0 db1d44a6`502600d0 : nt!PspSystemThreadStartup+0x5afffff880`009a9c40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9870 00000000`00000000 : nt!KxStartSystemThread+0x16SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  521ea035STACK_COMMAND:  .cxr 0xfffff880009a90c0 ; kbFAILURE_BUCKET_ID:  X64_0x7E_nt!KxWaitForLockOwnerShip+12BUCKET_ID:  X64_0x7E_nt!KxWaitForLockOwnerShip+12Followup: MachineOwner--------- 

[ionbasa]

Also, while I did not run memtest86+ because I didn't have enough time, I did run windows memory diagnostics, and no problems were found.

 

Thanks again for the detailed instructions and replies!

Actually, Windows Memory Diagnostics isn't recommended as it only does one pass, and some have reported issues with the tool. I still highly urge you to try Memtest86++ as well.

 

I would also like to point out that the AMD drivers should have been uninstalled with the AMD GPU still installed, only after the AMD drivers are uninstalled should you power off your pc and then switch GPUs and install the correct Nvidia driver version.

 

If the clean install does not help, then you are going to have to manually remove some drivers.

[Mbarton]

I see the problem you mixed red(AMD CPU) with green(Nvidea GPU) lol

[ionbasa]

I see the problem you mixed red(AMD CPU) with green(Nvidea GPU) lol

Not relevant. Please stay on topic, and please post something useful.

[Mbarton]

Not relevant. Please stay on topic, and please post something useful.

Sorry just some humor to to brighten the day

[SchrodingersCat_]

Actually, Windows Memory Diagnostics isn't recommended as it only does one pass, and some have reported issues with the tool. I still highly urge you to try Memtest86++ as well. I would also like to point out that the AMD drivers should have been uninstalled with the AMD GPU still installed, only after the AMD drivers are uninstalled should you power off your pc and then switch GPUs and install the correct Nvidia driver version. If the clean install does not help, then you are going to have to manually remove some drivers.

Will do!

[SchrodingersCat_]

Actually, Windows Memory Diagnostics isn't recommended as it only does one pass, and some have reported issues with the tool. I still highly urge you to try Memtest86++ as well.

I would also like to point out that the AMD drivers should have been uninstalled with the AMD GPU still installed, only after the AMD drivers are uninstalled should you power off your pc and then switch GPUs and install the correct Nvidia driver version.

If the clean install does not help, then you are going to have to manually remove some drivers.

Oh. I did not think to do that. I didn't think it would be an issue. Thank you for telling me though. I also knew that the windows memory diagnostics were inadequate from reading forum posts about it, I just wanted to try and rule out as much stuff as I could as fast as I could.

I see the problem you mixed red(AMD CPU) with green(Nvidea GPU) lol

Best of both worlds? Lol.

[SchrodingersCat_]

8350? 

With my experience they usually require a higher load line calibration setting.

 

Are you overclocking?

 

Also since you are getting bsods there should be minidump files located under "%systemroot%\minidump"

If you can copy them to a temporary folder on your desktop, zip the folder an attach it to your post here in the thread and I can take a look at it.

I just checked but my motherboard doesn't have a setting for LLC.

 

Have you tried downclocking your CPU? Sound almost like an error when you overclock. So perhaps dropping your speed below the stock might help. Also, you can try setting the voltage and CPU settings manually. Your PSU is giving you enough power, I'd say.

I just downclocked it to 3.0GHz (200x15), and I ran all the Aida64 Extreme tests at the same time and got no errors. So now I know the issue lies with the CPU. Is it not getting enough voltage, or is there some other issue? Everything is set to auto except the multiplier right now. Should I go up to 1.3v at 4.0GHz? What voltages would be considered too high for 4.0GHz?

 

Thanks for the help guys!

[SchrodingersCat_]

@ionbasa

Thank you so much for providing information about the issues I have been having and helping me sort everything out. I have good news, it turns out that when I updated the BIOS, there are apparently bad voltage settings for this particular CPU on this BIOS. I searched online for the stock voltage for the FX-8350, and found it to be 1.375v. When I was stress testing and getting errors, I found that the voltage was around 1.28v, which was causing the CPU to provide bad data causing the GPU driver to crash. I have manually set the voltage on the CPU to 1.375v and set the chip at stock clocks (4.0GHz) and ran prime95 and all aida64 tests, and lo and behold, no errors! Thank you again for all your help and support!

[killcomic]

@ionbasa

Thank you so much for providing information about the issues I have been having and helping me sort everything out. I have good news, it turns out that when I updated the BIOS, there are apparently bad voltage settings for this particular CPU on this BIOS. I searched online for the stock voltage for the FX-8350, and found it to be 1.375v. When I was stress testing and getting errors, I found that the voltage was around 1.28v, which was causing the CPU to provide bad data causing the GPU driver to crash. I have manually set the voltage on the CPU to 1.375v and set the chip at stock clocks (4.0GHz) and ran prime95 and all aida64 tests, and lo and behold, no errors! Thank you again for all your help and support!

Ah, good stuff! Glad to hear you sorted it out!