APU：7950x
without GPU
When I remove the APU driver, it will run normally. But after restarting, I won’t be able to run the program。
It usually runs for a period of time and then crash
Crash how, is there something in logs?
system：Windows 10
the gui is crash
maybe Windows doesn’t capture the full log
2024-04-01T03:27:38.773123Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:38.794746Z INFO Node: substrate: 💤 Idle (22 peers), best: #883524 (0x4d37…2ae9), finalized #798553 (0x330f…3d9d), ⬇ 415.1kiB/s ⬆ 22.3kiB/s
2024-04-01T03:27:38.845385Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:38.927408Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.011664Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.083860Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.177739Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.272662Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.370740Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.439616Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.538589Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.629139Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.728335Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.820287Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.892063Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:39.969021Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:40.047222Z WARN Node: sync: 💔 Error importing block 0x4cb128fde6b47c40020475ce57cd78582e594da3ed42391d8ff11934bdbe5055: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:40.410889Z INFO Node: substrate: ✨ Imported #e[1;37m883525e[0m (0x4cb1…5055)
2024-04-01T03:27:40.427816Z WARN Node: sync: 💔 Error importing block 0xd4ad831c46e920b70a9c16eca3c13f21795b7efdbdd4e094177c3b687106a674: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
2024-04-01T03:27:40.537088Z WARN Node: sync: 💔 Error importing block 0xd4ad831c46e920b70a9c16eca3c13f21795b7efdbdd4e094177c3b687106a674: consensus error: Checking inherents failed: The timestamp of the block is too far in the future.
Probably doesn’t, there is nothing fatal in those logs.
Check system events/logs/whatever on Windows to see what might have caused it.
“ Display driver amduw23g stopped responding and has successfully recovered”.
I then tried rolling back my APU driver to the previous version… to which the same issues persisted
Doesn’t seem to be Subspace-related then, looks like buggy drivers or something
I don’t need any other information to understand that this is a node operating within China.
If you can answer the following question, I can tell you why.
Have you blocked or are you having difficulty accessing networks outside of China?
Have you enabled a timekeeper ?
This issue seems to occur mostly with nodes inside China, and I’ve found that the nodes I run in Germany and Japan hardly ever encounter this. It seems to be related to their handling methods, where they block external traffic and enable a timekeeper .
So, I really don’t understand what they are actually doing.
You just need to make sure your machine has properly synced time. If someone else produces blocks on machine that doesn’t have correct time, this is not your fault and nothing you can do about it.