[INVESTIGATING] Blue screens on Windows 10 PC version

Troubleshooting Hub Legacy Troubleshooting Legacy Motorsport Issues
1

I’ve been playing Forza 7 since launch on my Windows 10 PC. I’ve been loving the game so far. My only major problem is the game sometimes dropping out to desktop and worse, sometimes blue screening. Not sure what the cause is or how to fix it.

The message I get during BSOD is related to dxgmms2.sys. I’ve googled it without much success. I’ve only had this happen during Forza 7, I play many other games on a regular basis with no problems, including Forza Horizon 3. I’ve noticed it seems to blue screen on the series table thing you get shown after a race, to show which position each driver is in and any changes to positions since the race. I probably have this happen around 1 in 10 races or so. Sometimes after hours of playing the game, sometimes after the first race I play. No real pattern to it other than that.

Any help or advice would be highly appreciated, as my enjoyment of the game is being spoiled by this.

2

I actually got that dxgmms2.sys 3 times in a row in FH3 for the first time EVER after the FM7 was crashing to the desktop. I tried restart etc and then run the troubleshooter for the Windows Store and it went away. I think a lot of people are blaming T10 when most issues appear related to the store app and I wonder if there is not some sort of phone home on startup to check credentials then once the store is corrupted it throws exceptions.

I checked back on that and it was the same issue I thought I was going to have to contact support. If you are using an MS XBOX controller when it goes it is like a yoke on a 767 in stall mode to the point if you had false teeth they would end up on your lap.

3

grab Bluescreen View

It may give you more information

4

I can only find that this is related to overclocking / faulty ram (do a memtest) or Killer Network drivers. Disable the integrated graphics card etc.
The file itself has something to do with DirectX12.

You can also try to complete remove the graphics card driver using DDU (Display Driver Uninstaller) and reinstall it.

Driver Verifier to track down crashing drivers :
https://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

5

Hi , just had a blue screen myself just now , did you manage to get it resolved ?
Ive had a lot of crashing since launch but blue screening is a first for me with this game . It happened just after a race while i was getting rewards .

my pc specs in case it matters to someone :
windows 10 home fully updated 64bit
i7 4790k stock
gtx 1070 stock latest nvidia driver 388.13
16gb ddr3 @1866 stock
and the game is running of an mx300 525gb dedicated ssd .

thanks

6

I had my first BSOD not too long ago as well. It happened after getting Forza 7. I don’t want to blame the game, but for the year-and-a-half I’ve had this PC, it has never happened before. Someone told me to limit my graphics card’s FPS output. I restricted frames at no more than 100fps with the EVGA Precision software. Everything seems fine.

As for my i5 6600K, it is overclocked, and I don’t intend on reseting it. Especially when it’s been working flawless with all my other close-to 100 games. I also have a very odd amount of Ram at 20gb. Microsoft and T10 need to adjust to the PC enthusiast community. Not the other way around.

EDIT: Let me add that (and I’m not sure it is the case with FM7), some loading screens in some games are uncapped, and if you have a powerful GPU, those FPS will shoot up, creating a voltage spike. This will most likely trigger a BSOD if your mobo can’t handle it, or you have a faulty PSU. Know that FH3 has this issue. So try and limit your GPU.

1 Like
7

Yeah this the only game i had a blue screen with too .
Also i use vsync 60fps aption because a have a 60hz 1080p tv im playing on so it mustnt be a frame rate spike i dont know for sure .
One thing though , did you happen to use the new final version of rivatuner statistics server 7.0.0 final with msi afterburner when it happened ? because i im not sure if its that or not but when i installed the latest version of the rivatuner (i use it for on screen display) its when it happened . Any other game works fine with it though and forza 7 worked without a blue screen with the beta version of rivatuner .
Im asking this cause also i played forza 7 without the on screen display and dint have a blue screen this time .

8

I got the same BSOD last night after a few minutes into a race.

I got around the constant CTDs by avoiding the dynamic video settings, just to be replaced by BSODs. :slight_smile:

Really not enjoying the Forza (FH3 + 7) PC experience. I don’t have these issues with any other games, including Gears of War 4 which is also UWP!! Will stick with them and hope these issues can be resolved as, when working, it is the best driving game around.

BTW - Afterburner and Riva Tuner weren’t running at the time, I always close them before starting Forza.

9

I have the same bsod. Here’s the debugging info:

BugCheck 1000007E, {ffffffffc0000005, fffff802b0659320, ffff8381a7709618, ffff8381a7708e60}

Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+120 )

Followup: MachineOwner

1: kd> !analyze -v

  • Bugcheck Analysis *

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but …
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff802b0659320, The address that the exception occurred at
Arg3: ffff8381a7709618, Exception Record Address
Arg4: ffff8381a7708e60, Context Record Address

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.674 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: LENOVO

SYSTEM_PRODUCT_NAME: 80WW

SYSTEM_SKU: LENOVO_MT_80WW_BU_idea_FM_Lenovo R720-15IKBN

SYSTEM_VERSION: Lenovo R720-15IKBN

BIOS_VENDOR: LENOVO

BIOS_VERSION: 4KCN28WW

BIOS_DATE: 05/18/2017

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: Provence-5R3

BASEBOARD_VERSION: SDK0L77769 WIN

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff802b0659320

BUGCHECK_P3: ffff8381a7709618

BUGCHECK_P4: ffff8381a7708e60

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 -

FAULTING_IP:
dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+120
fffff802`b0659320 4c8b10 mov r10,qword ptr [rax]

EXCEPTION_RECORD: ffff8381a7709618 – (.exr 0xffff8381a7709618)
ExceptionAddress: fffff802b0659320 (dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0x0000000000000120)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: ffff8381a7708e60 – (.cxr 0xffff8381a7708e60)
rax=0000000000000000 rbx=ffff960adb24fc20 rcx=00000000ffffff00
rdx=0000000000000001 rsi=0000000000000001 rdi=0000000000000000
rip=fffff802b0659320 rsp=ffff8381a7709850 rbp=ffff8381a77098a0
r8=ffff960adb246000 r9=7fff960adb250008 r10=7ffffffffffffffc
r11=fffff780000003b0 r12=ffff960ae2a2db20 r13=0000000000020000
r14=ffffe380383f9a10 r15=ffff960ada37f370
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0x120:
fffff802b0659320 4c8b10 mov r10,qword ptr [rax] ds:002b:0000000000000000=???
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 9c0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 5E’00000000 (cache) 0’00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: LAPTOP-15IKBN

ANALYSIS_SESSION_TIME: 11-07-2017 00:18:28.0465

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff802b064e433 to fffff802b0659320

STACK_TEXT:
ffff8381a7709850 fffff802b064e433 : 0000000000000000 0000000000000001 ffffe3803e8f2408 ffff960ada37f300 : dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0x120
ffff8381a77098e0 fffff8001336feb7 : fffff80011b77180 ffff960adb1ec700 fffff802b0630b20 ffffe380383f9a10 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1d903
ffff8381a7709b90 fffff80013404a06 : fffff80011b77180 ffff960adb1ec700 fffff8001336fe70 0000000000000000 : nt!PspSystemThreadStartup+0x47
ffff8381a7709be0 0000000000000000 : ffff8381a770a000 ffff8381a7703000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC: 64e5be602d458f9f545dee5670043c0f90da00cb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: affae9fb141de82cc6b0acf396f22f832d70ffbc

THREAD_SHA1_HASH_MOD: 395a8e26dd3d32f9decac500f32d66bbc1f5d92b

FOLLOWUP_IP:
dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+120
fffff802`b0659320 4c8b10 mov r10,qword ptr [rax]

FAULT_INSTR_CODE: 49108b4c

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+120

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c0a8147

IMAGE_VERSION: 10.0.15063.673

STACK_COMMAND: .cxr 0xffff8381a7708e60 ; kb

BUCKET_ID_FUNC_OFFSET: 120

FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure

BUCKET_ID: AV_dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure

PRIMARY_PROBLEM_CLASS: AV_dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure

TARGET_TIME: 2017-10-21T04:44:52.000Z

OSBUILD: 15063

OSSERVICEPACK: 674

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-09-29 15:20:26

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.15063.674

ANALYSIS_SESSION_ELAPSED_TIME: fa0

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_dxgmms2!vidmm_worker_thread::handlerecoverablepageinfailure

FAILURE_ID_HASH: {a4678fc3-4329-210d-c0db-63757bdd12c6}

Followup: MachineOwner

10

My machine is crashing with the exact same bugcheck and stacktrace in debugger. win10, 1080GTX w/ 8GB. ultra settings with vsync disabled and no cap on frame rate (gsync enabled). This is the only game that crashes my machine, like this.

11

Hey everyone,

Sent this over to the team. Ill update once I have more information.

Thanks,

12

I also have bluescreens with dxgmms2.sys indicated as the culprit. This is along side the regular CTDs that occur.
In both cases the crash is most likely to occur after crossing the finish line when the results are displayed on screen and the AI is driving the car.
I have let both memtest86 and prime95 run for a few hours each and neither program unearthed any instability issues.

13

Just an update. I haven’t had any problems ever since I put an FPS lock on my GTX1070. I also locked FM7 at 60fps. My other games are no longer going over 100fps, which kind of defeats the purpose of having a 144hz monitor, but I rather be safe. My temps have lowered as well.

All in all, the last patch fixed the game for me at least. Playing for hours with no lockups, save loops, CTD’s, stutters or any visual glitch that I’ve noticed.

I don’t really have a reason to be in this section, to be honest XD

14

Hi everyone,

The team is currently investigating. I will let you know when I have more information.

Thank you

15

I also had BSOD everytimes i launched game last time (since month) Today game freezed, including sound but no BSOD. From changes on my PC from last time i buyed Blizzard mountain DLC, updated rivatunner, updated Windows to PRO.
No problem before, but i had break with the game, so cant aquire fault directly.

se !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80065d01775, fffffa816505f658, fffffa816505eea0}

  • WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+121 )

Followup: MachineOwner

nt!KeBugCheckEx:
fffff8004af816e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa816505e6a0=000000000000007e

ONCE AGAIN :
Probably caused by : dxgmms2.sys

So its something with direct. Microsoft, please help.

16

I got good news and bad news.
I tried yesterday something more extremal from available possibilities;

  • I have created local account in windows and maked it as admin.
  • Moved Forza to C drive (SSD, same that have system on it)
  • Deleted all savegames in C:\Users\ACCOUNT NAME\AppData\Local\Packages\Microsoft.OpusPG_8wekyb3d8bbwe\SystemAppData\wgs\XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  • Once i stared game i stopped synchronisation, i started new game ( Was it necessary Microsoft!?)
  • GAME FINALLY SAVES MY VIDEO SETTINGS - ONE LITTLE VICTORY, WHICH WHOLE MS SUPPORT TEAM COULDNT ACHIEVE IN 8 MONTHS.
  • Thanks to above i managed to disable multithreading support in game, decreased pre-rendered frames to 1 (och, finally!)
  • Disabled Rivatuner and…
    GAME STARTED CRASHING INSTEAD BLUESCREENS AND FREEZING WHOLE PC. I think i found reasons of not saving video settings - sync is making files read-only, as i stop sync everytime i launching game and settings stays intact, and i can change them when i try, it will stays as i leave them after game rebot. Game is not reading settings from cloud, but from Hard disc, so is there any way i can disable syncing on every game boot?
    Now all that is left, and cannot be fixed by players (IT IS YOUR JOB MS and Turn10) is making game not crashing to desktop. I can help you with logs as soon as i find them (where are those logs?). Issue is not connected to Display driver, audio driver, or any other, but… I found myself in many situations when not common reason of crash was WLAN. I would check this if i would be on Your place. DirectX is final reason of crash, but none of other games is crashing, and i didnt saw any topic in DX 12 games about crashing last time. Now, let me enjoy my little succes about saving progress and post it everywhere, where i writed about this issue, beacuse ISSUE still exist. I jsut found temponrary solution.

BTW opinion center (i use Polish sorry for misleading translation) is not working since yesterday, it have endless problems with connection.

17

I don’t own Forza 7 however I can’t find anything similar to this thread for Horizon 3. I get the same BSOD message and blue screens most commonly happen before or after a loading screen of any sort. I have tried cleanly reinstalling my GPU drivers twice with no success. This issue (among many others) plagues Horizon 3 aswell and I seriously hope the devs do SOMETHING about it.

18

It’s such a shame that such a nice and excellent game suffers from this critical flaw. I don’t have FM7 but Forza Horizon 3. However it seems that both games suffer from the same issue. My PC can run the game easily at Ultra quality with constant 60fps, but suddenly the game would crash and send the whole system into a BSoD.

On Windows 10 1709 the game used to crash but the system wouldn’t BSOD, just a CTD. Now with Windows 10 1803 it’s BSoD all the time. This is unacceptable and that’s why I had to uninstall it after investing so much money into this game. I hope it can be figured out and fixed. AND I also really HOPE Forza Horizon 4 doesn’t suffer from this altogether. Such a bummer.

19

I too, have this problem while playing Forza Horizon 3. What the heck? Unacceptable. I love the game, but I can’t play if it’s going to BSOD all the time.

20

I have had this problem also for a while. First time the BSOD (PAGE_FAULTED_IN_NONPAGED_AREA in my case) occurred was while playing Forza Horizon 4. I gave Forza Motorsport 7 a go with the hopes of this not happening but you guessed it, the same blue screen happens. These are the only 2 games that cause a blue screen on my PC. I really enjoy both of these games but since I couldn’t find a solution to this I’m losing interest in playing Forza games on my PC.

UPDATE: Doesn’t blue screen anymore! But crashes instead.
After updating my NVIDIA GeForce drivers to 417.35 Forza Horizon 4 crashes constantly, but without a blue screen this time. I can sometimes play for about 10 minutes before my game closes itself without any sign of it all. Same thing with Forza Motorsport 7. I don’t have any explanation for this and I would actually rather still have the blue screens since they occurred more rarely and I was at least able to play for about an hour before the whole PC went to a blue screen.
Will keep updating my status if I somehow fix this issue!
I will also gladly try any ideas on how to fix this mess.

New update which included the Mitsubishi cars did not resolve the issue. Still crashes within 5 minutes of starting, sometimes even on startup.