BSOD Crashes

G

Gowtham J

New member
Joined
Nov 26, 2022
Posts
2
Hi...

Im facing some issue with lenovo thinkpad E470 , after replaced the SSD drive and loaded the Windows 10 then updated the windows & BIOS blue screen error coming and restarting. After that i checked the event logs i got the error Code Bugcode 239
 
Hi,

I would recommend to run MemTest86 based on the events recorded as shown below. Also, did you recently attach a removable storage device like USB or other external storage?
Test RAM with PassMark MemTest86
Code: 
   2022-11-26T00:38:24.3960000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T15:59:00.7830000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T15:59:01.0590000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T16:04:47.9250000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T16:04:48.2040000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T16:14:12.0020000Z        A corruption was discovered in the file system structure on volume F:.
The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
   2022-11-25T16:29:31.8370000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T16:29:32.1220000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T16:48:21.8250000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T16:48:22.1010000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T17:34:18.8080000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T17:34:19.0990000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T17:45:15.7820000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T17:45:16.0700000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T17:58:25.7750000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T17:58:26.0560000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-25T18:12:22.7760000Z        Dump file creation failed due to error during dump creation.
   2022-11-25T18:12:23.0580000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T10:48:49.3670000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T11:38:23.4190000Z        A corruption was discovered in the file system structure on volume F:.
The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
   2022-11-26T12:11:55.5080000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T12:11:55.8030000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T12:31:47.8490000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T12:31:48.1350000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T13:07:59.8630000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T13:08:00.1570000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T13:19:34.8220000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T13:19:35.0990000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T15:12:52.8130000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T15:12:53.0960000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T15:21:38.8080000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T15:21:39.0830000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
   2022-11-26T15:48:42.5480000Z        Dump file creation failed due to error during dump creation.
   2022-11-26T15:48:43.1830000Z        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
In addition to the above, and since you're running on a (partitioned) single HDD, I would run a chkdsk /r /x on each partition. The /r switch tells chkdsk to scan and fix the filesystem and to also scan the disk surface for errors, assigning spare sectors for any that are bad. Note that this has the potential to destroy data, so please be sure to have complete backups of everything first!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top