No BSOD but frequent crashes.

S

sjm

New member
Joined
Apr 16, 2018
Posts
1
Hi,
I've been having problems with my new build for months now. Can't find a link to the crashes - sometimes 3 per day. I've had stable periods which I think are related to Win 10 updates so I'm blaming Win 10 for the issues - perhaps wrongly.

I've tried to do a clean windows install but, no surprise, it crashes.

Thinking of starting from scratch, formatting the hard drive and installing win 7 again.

Any help or suggestions would be appreciated.

Sam
 

Attachments

Hi sjm,

:welcome: to Sysnative.

Unforunately you have had BSOD crashes, only the system is unable to record the dumps.
The 0xEA (driver in endless loop) is commonly a result of an issue with the display drivers.
Please check Desktop for driver updates, or reinstall the drivers.

I would also recommend to run SeaTools DOS on your hard drives
Hard Drive Diagnostics & SSD Test

Code: 
2018-04-12T12:48:03.988		Crash dump initialization failed!
2018-04-12T12:48:03.988		Crash dump initialization failed!
2018-04-12T12:21:55.007		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffba86b42da700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0937f751-9756-4a24-9a04-dd5b791b3dfa.
2018-04-12T12:21:55.007		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffba86b42da700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0937f751-9756-4a24-9a04-dd5b791b3dfa.
2018-04-03T10:51:07.078		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-04-03T10:51:07.078		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-30T21:10:31.730		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-30T21:10:31.730		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-30T10:32:00.145		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffc000fa9c1700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ed374253-0175-4eaf-b56f-ace5ebb19aa4.
2018-03-30T10:32:00.145		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffc000fa9c1700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ed374253-0175-4eaf-b56f-ace5ebb19aa4.
2018-03-29T17:25:28.207		Crash dump initialization failed!
2018-03-29T17:25:28.207		Crash dump initialization failed!
2018-03-29T13:53:28.288		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-29T13:53:28.288		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-29T13:16:34.680		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffff9a0583c86080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 51e43888-0760-48d1-ad1b-d38e6525c407.
2018-03-29T13:16:34.680		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffff9a0583c86080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 51e43888-0760-48d1-ad1b-d38e6525c407.
2018-03-25T15:41:21.531		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-25T15:41:21.531		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-20T10:07:20.113		Crash dump initialization failed!
2018-03-20T10:07:20.113		Crash dump initialization failed!
2018-03-20T09:59:19.165		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffe10e5932a080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6bf4412d-f319-43af-80cb-ef980e01b3cb.
2018-03-20T09:59:19.165		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffe10e5932a080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6bf4412d-f319-43af-80cb-ef980e01b3cb.
2018-03-16T13:37:32.190		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-16T13:37:32.190		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-15T11:45:26.848		Crash dump initialization failed!
2018-03-15T11:45:26.848		Crash dump initialization failed!
2018-03-15T11:34:21.429		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffda83f7e71080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 331f7173-ee00-4554-9ca8-da45c73074cb.
2018-03-15T11:34:21.429		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffda83f7e71080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 331f7173-ee00-4554-9ca8-da45c73074cb.
2018-03-13T17:11:51.698		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-13T17:11:51.698		The IO operation at logical block address 0x3f for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-13T15:57:56.471		The IO operation at logical block address 0x404de837 for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-13T15:57:56.471		The IO operation at logical block address 0x404de837 for Disk 2 (PDO name: \Device\00000036) was retried.
2018-03-09T17:42:25.488		Crash dump initialization failed!
2018-03-09T17:42:25.488		Crash dump initialization failed!
2018-03-07T12:33:48.004		Crash dump initialization failed!
2018-03-07T12:33:48.004		Crash dump initialization failed!
2018-03-05T13:37:52.775		The driver detected a controller error on \Device\Harddisk2\DR2.
2018-03-05T13:37:52.775		The driver detected a controller error on \Device\Harddisk2\DR2.
2018-03-04T15:08:29.884		The IO operation at logical block address 0x321865b7 for Disk 2 (PDO name: \Device\0000003d) was retried.
2018-03-04T15:08:29.884		The IO operation at logical block address 0x321865b7 for Disk 2 (PDO name: \Device\0000003d) was retried.
2018-02-27T14:51:57.903		Unable to produce a minidump file from the full dump file.
2018-02-27T14:51:57.903		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffe286f4068700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-02-27T14:51:57.903		Unable to produce a minidump file from the full dump file.
2018-02-27T14:51:57.903		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffe286f4068700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-02-25T09:38:55.906		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffc88f763de080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8e50b537-539d-48b3-9fa8-95c3a313ff0c.
2018-02-25T09:38:55.906		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffc88f763de080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8e50b537-539d-48b3-9fa8-95c3a313ff0c.
2018-02-24T09:47:15.262		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffc00e050d6040, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5d90738d-f103-4d87-a0ac-b77aac92d260.
2018-02-24T09:47:15.262		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffc00e050d6040, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5d90738d-f103-4d87-a0ac-b77aac92d260.
2018-02-22T10:12:09.002		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffcd8a8a481080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eb7e2b56-1a85-4072-bd36-82c30f3d92cd.
2018-02-22T10:12:09.002		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffcd8a8a481080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eb7e2b56-1a85-4072-bd36-82c30f3d92cd.
2018-02-21T11:56:00.473		Crash dump initialization failed!
2018-02-21T11:56:00.473		Crash dump initialization failed!
2018-02-20T22:08:12.614		A corruption was discovered in the file system structure on volume Windows7.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x40c000000000100.  The name of the file is "\Users\Sonia\AppData\Local\Microsoft\OneDrive\logs\Personal\SyncEngine-2018-2-12.1557.10744.1.odl".
2018-02-20T22:08:12.614		A corruption was discovered in the file system structure on volume Windows7.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x40c000000000100.  The name of the file is "\Users\Sonia\AppData\Local\Microsoft\OneDrive\logs\Personal\SyncEngine-2018-2-12.1557.10744.1.odl".
2018-02-17T14:50:20.362		A corruption was discovered in the file system structure on volume Windows7.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x40c000000000100.  The name of the file is "\Users\Sonia\AppData\Local\Microsoft\OneDrive\logs\Personal\SyncEngine-2018-2-12.1557.10744.1.odl".
2018-02-17T14:50:20.362		A corruption was discovered in the file system structure on volume Windows7.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x40c000000000100.  The name of the file is "\Users\Sonia\AppData\Local\Microsoft\OneDrive\logs\Personal\SyncEngine-2018-2-12.1557.10744.1.odl".
2018-02-14T15:48:01.853		A corruption was discovered in the file system structure on volume Windows7.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x40c000000000100.  The name of the file is "\Users\Sonia\AppData\Local\Microsoft\OneDrive\logs\Personal\SyncEngine-2018-2-12.1557.10744.1.odl".
2018-02-14T15:48:01.853		A corruption was discovered in the file system structure on volume Windows7.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x40c000000000100.  The name of the file is "\Users\Sonia\AppData\Local\Microsoft\OneDrive\logs\Personal\SyncEngine-2018-2-12.1557.10744.1.odl".
2018-02-13T09:09:40.152		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x000000000000003f, 0x000000000001c45d, 0x00000000cb238a1e, 0x0000000071135d1b). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ec554861-4849-45e7-a13b-613749f2c2d7.
2018-02-13T09:09:40.152		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x000000000000003f, 0x000000000001c45d, 0x00000000cb238a1e, 0x0000000071135d1b). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ec554861-4849-45e7-a13b-613749f2c2d7.
2018-01-26T15:20:17.166		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffff8209eed25700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: f98ce337-6e36-4438-90d7-3a4e65482695.
2018-01-26T15:20:17.166		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffff8209eed25700, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: f98ce337-6e36-4438-90d7-3a4e65482695.
 
Hello sjm,

Can you describe the crashes in more detail - does the system shutdown or freeze? Do you see anything on the screen or hear any sound after the system crashes?

When you tried the clean install how did you do it, from scratch or via a refresh? Did it finish the install or did you crash during the install?

Have you tried running the system in safe mode to see if it still crashes? If so, this would indicate a hardware problem.
 

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

Back
Top