[SOLVED] BSOD 0x1E (0, 0, 0) in 3 games, nowhere else. FIX: used AMD driver cleaning tool, then installed AMD drivers.

C

ColdFusion769

Member
Joined
Jan 21, 2020
Posts
22
Hello, so I have been having BSOD's occuring consistently when playing Red Dead Redemption 2, Jedi: Fallen Order and it happened once in Fallout 4. They started happening early in January, yet I was playing RDR2 for a whole month before with no issues, I only get BSOD's in these games and no others. I played a bunch of other games while troubleshooting the issue, both hardware intensive games and some that aren't intensive yet they all performed perfectly.

I have checked through the hardware and they seem fine, if they were causing problems then I assume no games would work let alone the PC. I have been over my drivers thoroughly multiple times with no issues occuring whether I rolled them back or updated them. I have tested the system memory with no issues. Tested for file/drive corruption with no issues. Reverted my CPU clock speed back to the default which didn't fix the issue, and so I set it back to the overclocked speed.

I have been through a plethora of potential fixes with no luck and can't find a solution anywhere that explain it in layman's terms.

Any help on this matter would be much appreciated, and I will answer any other questions about it if I can.

OS: Windows 7 Home Premium
64-Bit
Pretty sure that Windows 7 was the initial OS (I'm well aware of the end of support for W7, I doubt that it is any cause of the problem)
Not sure if it was pre installed or purchased after, I didn't build it.
The system is about 6-7 years old, ignoring hardware upgrades of course
The OS installation will be the same as the PC, I can't recall if I re-installed it at any point

Hardware:
Intel i7 2600K 4-core @3.40GHz (O/C to 4.00GHz)
AMD Radeon RX 580 8GB VRAM
Don't recall what motherboard is being used right now
I use a 500W PSU, don't recall the brand

Custom Build

Desktop

I will check any hardware specifics that I didn't qualify soon enough.
 

Attachments

Size of RAM and size of pagefile ? Which drive for the pagefile ? Is it set on C:, game drive or another (physical drive) ? How many memory left on that drive ? Fixed pagefile size, variable size or you let windows automatically set the size ?
 
(why I'm asking these question is I suspect a Write access in a allready-used-for-writing-file, no space left in the pagefile for the ram to drop that access, and an overflow in pagefile doing that).

My instinct tells the written file is the savefile of the game (which typically grows and grows in those kind of games).
 
ColdFusion769 said:
Reverted my CPU clock speed back to the default which didn't fix the issue, and so I set it back to the overclocked speed.
Click to expand...

Please remove any overclocking at least during the troubleshooting process. I'll look at the other dump files when I'm home. Please see the analysis of one of the dump files below:

It appears that a driver may have corrupted part of the stack, I would suggest updating the following driver:

Rich (BB code): 
0: kd> lmvm atikmdag
Browse full module list
start             end                 module name
fffff880`0f047000 fffff880`12f3e000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Dec  4 17:42:59 2019 (5DE860A3)
    CheckSum:         03EB83FE
    ImageSize:        03EF7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

https://www.amd.com/en/support



Rich (BB code): 
0: kd> .frame /r 7
07 fffff800`00b9e430 fffff880`0437ad24 dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
rax=0000000000000000 rbx=fffffa8012344010 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80105f5000
rip=fffff8800437af7d rsp=fffff80000b9e430 rbp=fffffa80105f69a0
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80105f51f0
r11=fffff80000b9e4e8 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9:
fffff880`0437af7d 48f7f1          div     rax,rcx

The corruption likely lead to the divide by zero error as seen above.

Rich (BB code): 
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff800`00b9d2e8 fffff800`038f80ee nt!KeBugCheck
01 fffff800`00b9d2f0 fffff800`038fc1fd nt!KiKernelCalloutExceptionHandler+0xe
02 fffff800`00b9d320 fffff800`038bc125 nt!RtlpExecuteHandlerForException+0xd
03 fffff800`00b9d350 fffff800`039dbeee nt!RtlDispatchException+0x415
04 fffff800`00b9da30 fffff800`039033c2 nt!KiDispatchException+0x17e
05 fffff800`00b9e0c0 fffff800`038fe1e2 nt!KiExceptionDispatch+0xc2
06 fffff800`00b9e2a0 fffff880`0437af7d nt!KiDivideErrorFault+0x2e2 << Crash here!
07 fffff800`00b9e430 fffff880`0437ad24 dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
08 fffff800`00b9e4f0 fffff880`0437ac88 dxgmms1!VidSchDdiNotifyDpcWorker+0x80
09 fffff800`00b9e540 fffff880`042801cf dxgmms1!VidSchDdiNotifyDpc+0x94
0a fffff800`00b9e590 fffff880`0f111bd4 dxgkrnl!DxgNotifyDpcCB+0x77
0b fffff800`00b9e5c0 fffffa80`10d42520 atikmdag+0xcabd4 << Possible culprit driver
0c fffff800`00b9e5c8 fffffa80`10d42520 0xfffffa80`10d42520
0d fffff800`00b9e5d0 000000f4`10000000 0xfffffa80`10d42520
0e fffff800`00b9e5d8 fffffa80`10d42520 0x000000f4`10000000
0f fffff800`00b9e5e0 00000000`00000000 0xfffffa80`10d42520
 
The games are on my E: drive, which is 4TB. Plenty of room there as well a decent bit of space on my C: drive. I could perhaps try clearing some space from C: but I don't know if that is the problem.

As for the question about pagefiles, not quite sure I follow. I'm not really sure how to go about checking any of that.
 
I'll take a look at the driver, but I did already do a fresh install of my GPU drivers to the current recommended and that didn't fix it.
 
Keep in mind that @x BlueRobot found the actual part of software that crashed the computer so his advices are lot better than mine. Usually, this happen when you update your drivers by overwriting an old version. Try to clean desinstal your videodriver first, reboot in safe mode, then use a video driver cleaner tool that AMD recommends (i don't know AMD cards), reboot in safe mode, then reinstall the last videodriver from AMD.
Those are recent games, AMD did not evacuate each bug in these.

I suppose this happened when you changed from a zone in the game, then make a U turn and go back, no ?
If C, D and E are different physical drives, I, as a random computer-joe advice, would still recommend to put the virtual memory on your D drive, and set it to a fixed size of 1.5x your total RAM. Making it fixed would hang and release the system instead of making it crash (in my opinion). Making it variable or automatic would increase the hang time. If set to low, then here are your overflow.
Setting it on the a different physical disk than C or the game is an oldschool optimisation than proven good result with windows systems (nerd reason : C get a full SATA bandwidth for OS, then D get a full SATA bandwidth for swap, then E get a full SATA bandwidth for game files. This is oldschool but still work well).
 
Last edited:
I tried some of the suggestions here, unfortunately with no success. I did a full clean install of my graphics drivers (safe mode and everything) and got the latest version available yet it didn't solve it, although it did last a fair while when testing it in Fallout 4, around 80-90 mins. I swapped the virtual memory to my F drive (only C, E and F are available. No idea why it defaulted one of the drives to F instead of D, but that should be fine too) yet this didn't do anything either.

As for the occurrences being in specific areas, that simply isn't the case. The crashes are completely random, and always illicit a 1E error code. I only wish they happened in a consistent fashion so I could narrow it down, but the only thing I can ascertain from the crashes is that they only occur in those 3 games listed.
 
Can you tell me what size you put for the virtual memory, and what size of RAM you have ?

-edit- ok i see. nothing wrong there. Sorry for false lead, but keep virtual mem on F, it's better. Do you have users of those games complaining for the same BSOD ? That also could be a game programing problem (again, recent games but fallout, which is out of maintenance by devs). Last videodrivers could be a risk too.
 
Last edited:
Apparently my system does not meet the requirements for the USB driver

I am pretty sure that the ethernet driver was installed successfully
 
1. Run Driver Verifier Manager through write verifier in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 2 additional settings (force pending i/o request and irp logging)
4. Select "Select driver names from a list"
5. Tick AMD graphics drivers (atikmdag.sys and atikmpag.sys) and DirectX graphics drivers (dxgkrnl.sys and dxgmms2.sys)
6. Apply changes and reboot computer
 
Now play games where you encounter problems and wait for BSODs. As they appear, you are posting new crash dumps
 
Blue screen appeared or just the computer hang up?
 
It just crashed, I haven't actually had a blue screen appear for a while. It always crashes, reboots and shows a 'Windows has recovered from an unexpected shutdown' message as well as presenting the error code. However there is never any indication of any problematic drivers
 
And in C:\Windows\Minidump there are no new memory dumps?
 

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

Back
Top