BSOD errors when I installed new cpu + gpu

duderox123 · 26 Jan 2017

I just received a BSOD regarding tcpip.sys whilst doing an error scan which was nearly done. Now I have to redo it..

Attachment 118615

philc43 · 26 Jan 2017

If the BSODs are too frequent it may make it difficult to complete all the tests. If you can't we will just continue working through other possibilities.

I would like you to try running your PC with one of your memory sticks removed - I suggest you take out the 2GB stick. As your memory is of different type and different size it is just possible they might not be working well together. Another possibility is to try with the sticks fitted into different slots.

duderox123 · 27 Jan 2017

Healthcheck:
Attachment 118710
Error scan: BSOD twice at the last 4 bars with 0 errors so I cannot finish it. I'm assuming its fine.
Benchmark:
Attachment 118708
File Benchmark:
Attachment 118704

Chkdsk:
I have done chkdsk /f and it repaired the drive when I restarted. It took a couple of minutes because I have reset this PC like a week ago due to this BSOD. I checked event viewer logs and it said there was nothing to repair and was successful.

I did this in safe mode with networking and I ENCOUNTERED A BSOD in safe mode.

Does this mean this is a hardware problem?

I will attach a minidump:

Attachment 118707

duderox123 · 28 Jan 2017

I put the RAM in the other slots and I have reseated my GPU.

I have attempted to swap my new cpu to my old one and I found out that it was dead somehow as the power LED did not open but the fans were spinning.
I reseated my old CPU and it opened up fine.

Still BSOD'S

philc43 · 28 Jan 2017

BSOD events in safe mode do suggest that it is likely to be hardware since there is only a minimum set of drivers loaded just sufficient to get the PC working. You could try Safe mode without the network and see if it still gives a BSOD.

Please also run with just one of your memory sticks and see if it still gives a BSOD. Hopefully you are now narrowing down the possibilities and will soon find the cause. I'm a bit confused by your CPU comment; are you saying you bought a new CPU but it did not work in your PC? Did you change the BIOS settings to accommodate the new CPU specification?

duderox123 · 28 Jan 2017

philc43 said:

BSOD events in safe mode do suggest that it is likely to be hardware since there is only a minimum set of drivers loaded just sufficient to get the PC working. You could try Safe mode without the network and see if it still gives a BSOD.

Please also run with just one of your memory sticks and see if it still gives a BSOD. Hopefully you are now narrowing down the possibilities and will soon find the cause. I'm a bit confused by your CPU comment; are you saying you bought a new CPU but it did not work in your PC? Did you change the BIOS settings to accommodate the new CPU specification?

I bought a new cpu which was the 880k and replaced it with my old cpu (a8 5500)
a8 5500 was dead when I swapped it out to check if my 880k was causing problems and turns out the a8 5500 was dead as i couldnt power on

I do not know how to change the BIOS settings to accommodate with my new CPU nor do I know what to change

philc43 · 28 Jan 2017

Simply going into the BIOS menu and loading optimised defaults will automatically select the right settings.

duderox123 · 28 Jan 2017

philc43 said:

Simply going into the BIOS menu and loading optimised defaults will automatically select the right settings.

Cannot find it in the HP bios.

philc43 · 28 Jan 2017

duderox123 said:

Cannot find it in the HP bios.

HP must have limited access to the usual BIOS settings. There might be a reset CMOS option but I guess we are getting side tracked now - it is more important to continue with the tests I suggested (single memory stick, safemode without network etc.)

duderox123 · 28 Jan 2017

Received a new BSOD, heres the output:

Code:

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


Loading Dump File [C:\Windows\Minidump\012817-26046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff800`71683000 PsLoadedModuleList = 0xfffff800`71988060
Debug session time: Sat Jan 28 17:14:12.904 2017 (UTC + 0:00)
System Uptime: 0 days 0:07:53.919
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80071706fef, ffffbc01bd5538e8, ffffbc01bd553110}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80071706fef, The address that the exception occurred at
Arg3: ffffbc01bd5538e8, Exception Record Address
Arg4: ffffbc01bd553110, Context Record Address

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_MANUFACTURER:  Hewlett-Packard

SYSTEM_PRODUCT_NAME:  500-326na

SYSTEM_SKU:  G9C37EA#ABU

BIOS_VENDOR:  AMI

BIOS_VERSION:  80.10

BIOS_DATE:  10/23/2014

BASEBOARD_MANUFACTURER:  Hewlett-Packard

BASEBOARD_PRODUCT:  2B17

BASEBOARD_VERSION:  1.0 

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80071706fef

BUGCHECK_P3: ffffbc01bd5538e8

BUGCHECK_P4: ffffbc01bd553110

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

FAULTING_IP: 
nt!PopFxResidentTimeoutRoutine+a7
fffff800`71706fef 488b14c8        mov     rdx,qword ptr [rax+rcx*8]

EXCEPTION_RECORD:  ffffbc01bd5538e8 -- (.exr 0xffffbc01bd5538e8)
ExceptionAddress: fffff80071706fef (nt!PopFxResidentTimeoutRoutine+0x00000000000000a7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffbc01bd553110 -- (.cxr 0xffffbc01bd553110)
rax=6080000000000000 rbx=ffffd30fa9025e0a rcx=0000000000000000
rdx=ffffd30fa900a8a8 rsi=000000011a7a6fab rdi=0000000000000000
rip=fffff80071706fef rsp=ffffbc01bd553b20 rbp=fffff800719853c0
 r8=0000000000000000  r9=0000000000000000 r10=fffff80071610c40
r11=fffff80071683000 r12=0000000000000011 r13=00000000ffffffff
r14=0000000000000000 r15=fffff800719853b0
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!PopFxResidentTimeoutRoutine+0xa7:
fffff800`71706fef 488b14c8        mov     rdx,qword ptr [rax+rcx*8] ds:002b:60800000`00000000=????????????????
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: f99

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 38

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

FOLLOWUP_IP: 
nt!PopFxResidentTimeoutRoutine+a7
fffff800`71706fef 488b14c8        mov     rdx,qword ptr [rax+rcx*8]

READ_ADDRESS: fffff80071a2a338: Unable to get MiVisibleState
 ffffffffffffffff 

BUGCHECK_STR:  AV

ANALYSIS_SESSION_HOST:  DESKTOP-S8DSEMJ

ANALYSIS_SESSION_TIME:  01-28-2017 17:17:25.0207

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8007171a1b9 to fffff80071706fef

STACK_TEXT:  
ffffbc01`bd553b20 fffff800`7171a1b9 : ffffd30f`ad579040 ffffd30f`00001000 00000000`6e2c7d46 ffffd30f`00007000 : nt!PopFxResidentTimeoutRoutine+0xa7
ffffbc01`bd553b80 fffff800`71685729 : fffff800`719c5180 00000000`00000080 ffffd30f`a781f040 ffffd30f`ad579040 : nt!ExpWorkerThread+0xe9
ffffbc01`bd553c10 fffff800`717d2bb6 : fffff800`719c5180 ffffd30f`ad579040 fffff800`716856e8 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffbc01`bd553c60 00000000`00000000 : ffffbc01`bd554000 ffffbc01`bd54e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80071706915-fffff80071706916  2 bytes - nt!MiCopyHeaderIfResident+111
    [ 80 fa:00 86 ]
    fffff80071706c44-fffff80071706c45  2 bytes - nt!MiInitializeImageProtos+210 (+0x32f)
    [ 80 fa:00 86 ]
    fffff80071706cec-fffff80071706ced  2 bytes - nt!MiInitializeImageProtos+2b8 (+0xa8)
    [ 80 fa:00 86 ]
    fffff80071706df9-fffff80071706dfa  2 bytes - nt!MiGetPageForHeader+c1 (+0x10d)
    [ 80 fa:00 86 ]
    fffff80071706e79-fffff80071706e7a  2 bytes - nt!MiGetSystemPage+49 (+0x80)
    [ 80 fa:00 86 ]
10 errors : !nt (fffff80071706915-fffff80071706e7a)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffbc01bd553110 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2017-01-28T17:14:12.000Z

OSBUILD:  14393

OSSERVICEPACK:  693

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-12-21 06:50:57

BUILDDATESTAMP_STR:  161220-1747

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 2842

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80071706fef, The address that the exception occurred at
Arg3: ffffbc01bd5538e8, Exception Record Address
Arg4: ffffbc01bd553110, Context Record Address

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_MANUFACTURER:  Hewlett-Packard

SYSTEM_PRODUCT_NAME:  500-326na

SYSTEM_SKU:  G9C37EA#ABU

BIOS_VENDOR:  AMI

BIOS_VERSION:  80.10

BIOS_DATE:  10/23/2014

BASEBOARD_MANUFACTURER:  Hewlett-Packard

BASEBOARD_PRODUCT:  2B17

BASEBOARD_VERSION:  1.0 

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80071706fef

BUGCHECK_P3: ffffbc01bd5538e8

BUGCHECK_P4: ffffbc01bd553110

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

FAULTING_IP: 
nt!PopFxResidentTimeoutRoutine+a7
fffff800`71706fef 488b14c8        mov     rdx,qword ptr [rax+rcx*8]

EXCEPTION_RECORD:  ffffbc01bd5538e8 -- (.exr 0xffffbc01bd5538e8)
ExceptionAddress: fffff80071706fef (nt!PopFxResidentTimeoutRoutine+0x00000000000000a7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffbc01bd553110 -- (.cxr 0xffffbc01bd553110)
rax=6080000000000000 rbx=ffffd30fa9025e0a rcx=0000000000000000
rdx=ffffd30fa900a8a8 rsi=000000011a7a6fab rdi=0000000000000000
rip=fffff80071706fef rsp=ffffbc01bd553b20 rbp=fffff800719853c0
 r8=0000000000000000  r9=0000000000000000 r10=fffff80071610c40
r11=fffff80071683000 r12=0000000000000011 r13=00000000ffffffff
r14=0000000000000000 r15=fffff800719853b0
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!PopFxResidentTimeoutRoutine+0xa7:
fffff800`71706fef 488b14c8        mov     rdx,qword ptr [rax+rcx*8] ds:002b:60800000`00000000=????????????????
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: f99

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 38

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

FOLLOWUP_IP: 
nt!PopFxResidentTimeoutRoutine+a7
fffff800`71706fef 488b14c8        mov     rdx,qword ptr [rax+rcx*8]

READ_ADDRESS:  ffffffffffffffff 

BUGCHECK_STR:  AV

ANALYSIS_SESSION_HOST:  DESKTOP-S8DSEMJ

ANALYSIS_SESSION_TIME:  01-28-2017 17:17:42.0564

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8007171a1b9 to fffff80071706fef

STACK_TEXT:  
ffffbc01`bd553b20 fffff800`7171a1b9 : ffffd30f`ad579040 ffffd30f`00001000 00000000`6e2c7d46 ffffd30f`00007000 : nt!PopFxResidentTimeoutRoutine+0xa7
ffffbc01`bd553b80 fffff800`71685729 : fffff800`719c5180 00000000`00000080 ffffd30f`a781f040 ffffd30f`ad579040 : nt!ExpWorkerThread+0xe9
ffffbc01`bd553c10 fffff800`717d2bb6 : fffff800`719c5180 ffffd30f`ad579040 fffff800`716856e8 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffbc01`bd553c60 00000000`00000000 : ffffbc01`bd554000 ffffbc01`bd54e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80071706915-fffff80071706916  2 bytes - nt!MiCopyHeaderIfResident+111
    [ 80 fa:00 86 ]
    fffff80071706c44-fffff80071706c45  2 bytes - nt!MiInitializeImageProtos+210 (+0x32f)
    [ 80 fa:00 86 ]
    fffff80071706cec-fffff80071706ced  2 bytes - nt!MiInitializeImageProtos+2b8 (+0xa8)
    [ 80 fa:00 86 ]
    fffff80071706df9-fffff80071706dfa  2 bytes - nt!MiGetPageForHeader+c1 (+0x10d)
    [ 80 fa:00 86 ]
    fffff80071706e79-fffff80071706e7a  2 bytes - nt!MiGetSystemPage+49 (+0x80)
    [ 80 fa:00 86 ]
10 errors : !nt (fffff80071706915-fffff80071706e7a)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffbc01bd553110 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2017-01-28T17:14:12.000Z

OSBUILD:  14393

OSSERVICEPACK:  693

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-12-21 06:50:57

BUILDDATESTAMP_STR:  161220-1747

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 2faf

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------

I will first try the single stick of RAM then.