Frequent BSOD happening on my new PC (not in safe mode apparently)

Hello L K Pung,

I'm suspecting that you may have a problem with the hardware.  Sometimes the hardware tests just do not reveal the problem.

I would try removing one of your memory modules and seeing if it makes a difference.  Repeat with the other to see if you can identify one which may be faulty.

Hi,

I will do that for the time being.

May I know if you can help with analyzing the minidump files as I couldn't understand anything from it?

Thanks!

The summary from your mini-dumps is shown below:

Debug session time: Wed Dec  2 09:18:32.345 2020 (UTC + 0:00)

Loading Dump File [120220-7953-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 0:02:30.983

BugCheck Info: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)

Bugcheck code 00000162

Arguments: 

Arg1: ffffd90f02a7c080, The address of the thread

Arg2: ffffd90f011aa0c0, The lock address

Arg3: 00000000ffffffff, The session ID of the thread

Arg4: 0000000000000000, Reserved

BUGCHECK_STR:  0x162

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  TeamViewer.exe

Probably caused by: ntkrnlmp.exe ( nt!ExReleasePushLockEx+137814 )

FAILURE_BUCKET_ID:  0x162_nt!ExReleasePushLockEx

BiosVersion = 2.30

BiosReleaseDate = 08/31/2020

SystemManufacturer = Micro-Star International Co., Ltd.

SystemProductName = MS-7C95

BaseBoardProduct = B550M PRO-VDH WIFI (MS-7C95)

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Wed Dec  2 09:15:32.437 2020 (UTC + 0:00)

Loading Dump File [120220-7453-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 0:08:46.074

BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)

Bugcheck code 0000001E

Arguments: 

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff80660934600, The address that the exception occurred at

Arg3: ffff8989870aee58, Parameter 0 of the exception

Arg4: ffffa78081dee920, Parameter 1 of the exception

*** WARNING: Unable to verify timestamp for Netwtw04.sys

*** WARNING: Unable to verify timestamp for win32k.sys

BUGCHECK_STR:  0x1E_c0000005

PROCESS_NAME:  System

Probably caused by: NETIO.SYS ( NETIO!WfpNblInfoGet+0 )

FAILURE_BUCKET_ID:  0x1E_c0000005_STACKPTR_ERROR_NETIO!WfpNblInfoGet

BiosVersion = 2.30

BiosReleaseDate = 08/31/2020

SystemManufacturer = Micro-Star International Co., Ltd.

SystemProductName = MS-7C95

BaseBoardProduct = B550M PRO-VDH WIFI (MS-7C95)

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Wed Dec  2 09:03:14.417 2020 (UTC + 0:00)

Loading Dump File [120220-7656-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 0:03:08.054

BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

Bugcheck code 1000007E

Arguments: 

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff8058490890d, The address that the exception occurred at

Arg3: fffffc0364a3d708, Exception Record Address

Arg4: fffffc0364a3cf40, Context Record Address

*** WARNING: Unable to verify timestamp for win32k.sys

PROCESS_NAME:  System

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

Probably caused by: Wof.sys ( Wof!WofGetVolumeContext+79 )

FAILURE_BUCKET_ID:  AV_Wof!WofGetVolumeContext

BiosVersion = 2.30

BiosReleaseDate = 08/31/2020

SystemManufacturer = Micro-Star International Co., Ltd.

SystemProductName = MS-7C95

BaseBoardProduct = B550M PRO-VDH WIFI (MS-7C95)

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Wed Dec  2 08:52:39.361 2020 (UTC + 0:00)

Loading Dump File [120220-7421-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 0:28:43.000

BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)

Bugcheck code 00000101

Arguments: 

Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: ffffac801f699180, The PRCB address of the hung processor.

Arg4: 0000000000000004, The index of the hung processor.

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

PROCESS_NAME:  msedge.exe

Probably caused by: ntkrnlmp.exe ( nt!KeAccumulateTicks+15e236 )

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BiosVersion = 2.30

BiosReleaseDate = 08/31/2020

SystemManufacturer = Micro-Star International Co., Ltd.

SystemProductName = MS-7C95

BaseBoardProduct = B550M PRO-VDH WIFI (MS-7C95)

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Tue Dec  1 17:01:59.991 2020 (UTC + 0:00)

Loading Dump File [120220-6859-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 1:13:31.629

BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)

Bugcheck code 00000139

Arguments: 

Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).

Arg2: ffffaa82594ca740, Address of the trap frame for the exception that caused the bugcheck

Arg3: ffffaa82594ca698, Address of the exception record for the exception that caused the bugcheck

Arg4: 0000000000000000, Reserved

BUGCHECK_STR:  0x139

PROCESS_NAME:  Adobe Premiere Pro.exe

Probably caused by: ntkrnlmp.exe ( nt!KiCommitThreadWait+5c3 )

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiCommitThreadWait

BiosVersion = 2.30

BiosReleaseDate = 08/31/2020

SystemManufacturer = Micro-Star International Co., Ltd.

SystemProductName = MS-7C95

BaseBoardProduct = B550M PRO-VDH WIFI (MS-7C95)

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

When we see so many different bugchecks and also see the mention of data corruption we generally suspect unknown hardware errors and have to start looking at components - my best guess at this stage is RAM but please keep sending any new dump files as you continue the testing.

Hi there,

I have tried using only 1 sticks at a time and it has improved my situation significantly. 

Stick 1:

I managed to have the system running for 2 hours and while I was just browsing YouTube and it went BSOD of a sudden.

https://1drv.ms/u/s!AuQ7fhfejz3UpAUeT7mW6iAU9Qw-?e=tsuLJg

Stick 2:
After the crash over stick 1, I have proceeded to swap out and replaced the ram with Stick 2. Just 30 mins in I experience BSOD and I managed to upload the minidump before heading for bed (I live in Asia so it's past midnight for me)

https://1drv.ms/u/s!AuQ7fhfejz3UpAZtGRqN70CdyUi8?e=ur7dMd

Does it mean both my ram sticks are faulty?

Hi,

I have try to use only 1 stick of ram (stick 2) for the test and it has crashed while being in slot 3(counted from right towards processor) and slot 4. 

I have attached the links to the minidump as follow:

https://1drv.ms/u/s!AuQ7fhfejz3UpAo3JV7oyghIXjVr?e=F5kOCq (RAM Stick 2 Slot 1)
https://1drv.ms/u/s!AuQ7fhfejz3UpAs0edTJyUpMI3t7?e=ht8ROW (RAM Stick 2 Slot 2)

https://1drv.ms/u/s!AuQ7fhfejz3UpAiofJlYVOVqpbZU?e=vFxdZ1 (RAM Stick 2 Slot 3)
https://1drv.ms/u/s!AuQ7fhfejz3UpAmLJPrZbG2mPFZe?e=JDXRsk (RAM Stick 2 Slot 4)
https://1drv.ms/u/s!AuQ7fhfejz3UpAwHVublfB50oKJX?e=nftLOc (RAM Stick 1 Slot 1)

I actually got my hands on a pair of new ram sticks (T-force Vulcan Z 16GB 3200MHz x 2) from my friend who bought it directly from Amazon (unopened). Do I continue with the test on my current ram (stick 1 in all 4 slots and stick 2 in 2 other slots) before I proceed to test with his new ram sticks?

You might as well complete the tests with your current RAM before switching to the new RAM.  

Good progress!

I've completed all test across my 2 ram sticks on all 4 slots.

Turns out all 4 slots encounters BSOD while the most stable (stick 1 slot 2) remained up for 2.5hrs.

https://1drv.ms/u/s!AuQ7fhfejz3UpA5uz12LGyUo9PIZ?e=IoH83K (RAM Stick 1 Slot 2)

https://1drv.ms/u/s!AuQ7fhfejz3UpA1P750ZvGxVUQ5j?e=LkMlTh (RAM Stick 1 Slot 3)
https://1drv.ms/u/s!AuQ7fhfejz3UpA-s1R4WPmeP8qsF?e=BLBQgY (RAM Stick 1 Slot 4)

Should I return my motherboard and get a new one?

It is too soon to jump to the conclusion that the motherboard is faulty.  I would try the new RAM that you said you could use.

Then we need to make sure the CPU is OK.

I have seen many peoole having similar problems on your combination of CPU and motherboard so there is a possibility that the latest Windows update has triggered this.  Some people have had success by changing BIOS settings but there has been no official acknowledgement as far as i know.