BSOD :Whea Uncorrectable error

[shisxi]

I have installed sysnativeBSOD and run it. My error code is whea uncorrectable error while the bluescreen appeared. So, what should I do next?
Hope you will help me. Thanks :)

 

[axe0]

Hi shisxi,

Welcome to Sysnative!

Please run the tests mentioned in these tutorials:

• Test RAM with memtest.org MemTest86+
• Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test

2019-04-25T03:40:48.956        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff860448f88028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b1bd9103-6404-4f39-9a2b-d719781a48bd.
2019-04-25T03:38:29.298        Dump file creation failed due to error during dump creation.
2019-04-06T02:59:26.550        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd70bd397e028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0a0b2ad4-1d75-426e-a372-706a90cd884b.
2019-04-06T02:57:12.100        Dump file creation failed due to error during dump creation.
2019-03-26T18:40:39.905        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume6.
(A device which does not exist was specified.)
2019-03-26T18:40:39.905        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume6.
(A device which does not exist was specified.)
2019-03-26T18:29:55.007        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume5.
(A device which does not exist was specified.)
2019-03-26T18:29:55.006        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume5.
(A device which does not exist was specified.)
2019-03-26T00:01:33.117        Dump file creation failed due to error during dump creation.
2019-03-26T00:01:33.117        Crash dump initialization failed!
2019-03-22T23:27:49.243        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe60c71e2d028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b239a1d3-6786-40b1-87fa-f0cbbbb6f624.
2019-03-22T23:24:36.023        Dump file creation failed due to error during dump creation.
2019-03-22T20:05:57.897        Crash dump initialization failed!
2019-03-21T02:28:42.089        Dump file creation failed due to error during dump creation.
2019-03-21T02:28:42.089        Crash dump initialization failed!
2019-03-21T02:20:09.515        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff9783bafb7028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: cc710bdc-75ae-437f-b54a-c07c40545365.
2019-03-21T02:12:54.762        Dump file creation failed due to error during dump creation.
2019-03-21T00:12:27.438        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume5.
(A device which does not exist was specified.)
2019-03-20T18:31:14.914        The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffbc83dccf6080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0e65faf2-e758-4c3c-994f-46e7bff60b18.
2019-03-20T18:21:51.846        The computer has rebooted from a bugcheck.  The bugcheck was: 0xc000021a (0xffffc6057f679330, 0xffffffffc0000005, 0x00007ff9f88fb7f2, 0x000000fdc62bde80). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 18690d0d-5a02-407e-bb27-d05b41864e95.
2019-03-20T17:13:15.523        Crash dump initialization failed!
2019-03-18T23:31:22.715        The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffb40fdf56f240, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 205fefad-4bb8-404e-b8b4-8e35a066a100.
2019-03-18T16:32:49.172        Dump file creation failed due to error during dump creation.
2019-03-18T15:46:28.974        Crash dump initialization failed!
2019-03-18T15:37:45.520        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff978b92a99028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 80aafc1c-ead8-4bcc-a520-ac68a44a39bd.
2019-03-18T15:31:26.256        Dump file creation failed due to error during dump creation.
2019-03-14T02:10:22.277        The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffc28fc9bce080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2d34fe78-fc7b-4181-a202-07d56985a8ba.