Windows 10: BSOD playing Skyforge, error 0x12b

Hi,

I was playing Skyforge for a couple hours.
I had some programs running in the back like firefox, skype, steam etc. I was reading something through firefox and as soon as I tabbed back into Skyforge the BSOD occurred.

I was running Windows 7 Home Premium before and ever since I upgraded to Win 10 I've been missing 3 drivers of Unknown Devices. I don't know if this is related to the BSOD though.

Attachment 34007

:)

 

BSOD Machine Check Exception

Hey everyone,

This BSOD has become a daily thing now and it always happens while I am playing a particular game (Skyforge). The crash is fairly random from as quick as 5 minutes to as long as couple of hours while playing the game. I noticed that 'Windowed Mode' of the
game helps delay the BSOD but it is still disappointing as this is a relatively new system and to have BSODs at the start is just :/ I run a MSI GE62 2QD Apache Pro and have not altered anything since I purchased it ~6 months ago (aside from clearing bloatwares).
It was pre-installed with Windows 8.1 and I have tried the following in sequence:

1. Updating drivers via Windows Update and via MSI Support page

2. Updating to the latest Nvidia Graphic Driver

-The following changed the BSOD from Machine Check Exception to Driver_IRQL_Not_Less_Than_Or_Equal bwcW8x64.sys which relates to a variety of .sys files including but not limited to (acpiex.sys, rdyboost.sys, bwcW8x64.sys, etc.)

3. Uninstalled the latest Nvidia Graphic Driver and allowed Windows to automatically reinstall Nvidia Graphics Driver

-Back to Machine Check Exception

4. Cleaned all my fans, reseated RAM, fans are working

5. Monitored my temps, usually in the range of 40-60 (can reach 70~80 sometimes but this only lasts couple of seconds?)

6. Stressed test with Prime95 for 6 hours, no errors

7. Reinstalled Skyforge

8. Ran Driver Verifier

-Windows BSOD constantly, driver localised to hal.dll +37745 and ntoskrnl.exe (sadly I have lost the driver file because of 9)

9. Upgrade AND clean install to Windows 10

-BSOD again Machine Check Exception within minutes of game (hal.dll +364b1)

10. Please help

BlueScreenView dump file:

032816-47828-01.dmp

MSInfo:

TEST.TXT

I hope I have not missed out anything so that the team can help me with this issue. If there's anything else you need just let me know. You will have my eternal gratitude x

 

One dump in the logs and it's blaming a hardware memory error.
Code: BugCheck 12B, {ffffffffc00002c4, 5ed, 8393a17ca0, ffffd00021b8d000} Probably caused by : hardware ( REGION_PAGED_OUT ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 00000000000005ed, physical page number Arg3: 0000008393a17ca0, zero Arg4: ffffd00021b8d000, zero[/quote]
Download and run MemTest86+ - Test RAM - Windows 10 Forums



Note



Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

 

You gotta be kidding right? *Sad I just got memory back from Corsair because I had 1 faulty module

 

Run the test and we'll work from there after you provide the results.

 

So I was gonna run memtest overnight, but apparently that wasn't necessary....

Attachment 34274

Just my luck *Sad

 

Right, now we need to ascertain if it is the RAM or the DIMM slot/s on the motherboard. Read the MemTest86+ tutorial I linked and read Part #3. If you need any more guidance let me know.

 

Little update.

I've been testing the past two nights, not fully done yet, but I do know it's not my motherboard.
| | | | <- 4 modules

Tested the two on the left side first, ran for 7-8 hours, 12 passes, no errors.
Then I tested the modules from the left side in the right slots, ran 7-8 hours, 12 passes, no errors.

Tonight I will test 1 of the two other modules to see which one is the actual faulty one, either way it means I got faulty memory back from Corsair after sending my previous kit for warranty.