Tweet
Log has errors like this
Many different memory locations (offsets) were affected and the memory corruption involved many bits (0x264 in binary is 0010 0110 0100, which means 4 bits are being flipped).
This isn't typical of a hardware DRAM failure. So more likely there is some software corrupting the memory.
This can happen for example when a bug results in the allocation of the same video RAM twice, to two different tasks and then they corrupt each others RAM. Typically the bug is in the video card driver. Maybe the new version of Windows is using the graphics differently, triggering the bug.
If you search through the forum you will find lots of examples of this in the past. But they are hard bugs to fix and only maybe 1 or 2 people on the planet have power to fix these video drivers. They are very hard people to get access to.
Updating the video card driver (or falling back to an older one) can also help.... sometimes.
Also trying V11 can't hurt.
Many different memory locations (offsets) were affected and the memory corruption involved many bits (0x264 in binary is 0010 0110 0100, which means 4 bits are being flipped).
This isn't typical of a hardware DRAM failure. So more likely there is some software corrupting the memory.
This can happen for example when a bug results in the allocation of the same video RAM twice, to two different tasks and then they corrupt each others RAM. Typically the bug is in the video card driver. Maybe the new version of Windows is using the graphics differently, triggering the bug.
If you search through the forum you will find lots of examples of this in the past. But they are hard bugs to fix and only maybe 1 or 2 people on the planet have power to fix these video drivers. They are very hard people to get access to.
Updating the video card driver (or falling back to an older one) can also help.... sometimes.
Also trying V11 can't hurt.
Comment