So I then proceeded to remove the mods I had installed and disable all pre-installed ones if they had been enabled.
I figured it was perhaps an overheating issue, however upon monitoring my system usage and temperature (I use Speccy), it was only at 5% CPU usage, and sitting at ~36 degrees C. Now wishing to further my experience with the game I installed some mods including the First Person mod and 25km2 Mod, upon loading a new city in a new map with these mods enabled my computer proceeded to fully shutdown and required a disabling of the power supply, and re-enabling simply to reboot. I purchased C:SL and enjoyed 9 full hours of it succeeding in creating a Megalopolis, and it was an excellent experience. Possibly this problem is caused by another driver that cannot be identified at this time.Ĭrash dump file: C:\WINDOWS\Minidump\072920-30125-01.dmpI have also had this same issue and I'll try to be as accurate as possible as to how it occurred in the chance that the developers may be able to reproduce it, if you need any other information, please reply and I'll try to provide it:
The crash took place in the Windows kernel. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. Product: Microsoft® Windows® Operating Systemīug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)īugcheck code: 0x3B (0xC0000005, 0xFFFFF8012369AFF4, 0xFFFFF68865676290, 0x0)įile path: C:\WINDOWS\system32\ntoskrnl.exe On Wed 4:09:39 AM your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\072920-71109-01.dmp Google query: e1d68圆4.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL It is suggested you look for an update for the following driver: e1d68圆4.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation). It means that a crash dump file was properly written out.Ī third party driver was identified as the probable root cause of this system error. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. This was probably caused by the following module: e1d68圆4.sys (e1d68圆4+0x196BF)īugcheck code: 0xA (0x9B0000, 0x2, 0x1, 0xFFFFF8002F6305C3)įile path: C:\WINDOWS\System32\DriverStore\FileRepository\e1d68圆4.inf_amd64_61aa07b8041d598f\e1d68圆4.sysĭescription: Intel(R) Gigabit Adapter NDIS 6.x driverīug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. On Wed 7:11:59 PM your computer crashed or a problem was reported Click to expand.Oh also here are the two (edit, nvm there were 3 crashes) whocrashed logs from the BSODs.
0 kommentar(er)
