Windows 10: BSOD's while gaming, citing Memory management issues.

Hi guys,

I recently bought a new PC, its maybe 6 months old at this point and around 3 months ago I started having BSOD's.
These only occur when I am gaming, never had one before when browsing etc.

The stop code is generally memory management, though i have had one irql_page_less_than_equal i think it was, and a couple others I have forgotten.

I HAVE ran Memtest86+, 8 passes no errors, as having browsed through the forum looking for the answers, this seemed to be a common request for this type of issue.

This leads me to believe I have a driver issue, but having updated every driver I could easily update, as well as flashing my BIOS to the most recent version, I am still having these BSOD's.

If anyone can help me identify the issue that would be much appreciated.

Thanks,
.

Attachment 118574

:)

 

BSOD during gaming

I got BSOD while playing games, the error message shows memory manager, after that I cannot boot into windows because of BSOD error 0xc000021a, I can only boot into it by selecting "disable driver signature enforcement" , what information I need to provide
to get help?

 

BSODs, help plz

So I updated the software and firmware of my NAOS 7000 mouse and also the two other drivers. However, my laptop still gets the BSOD with the Memory Management stopcode while I was gaming. After that, I unplugged my mouse and started playing my CSGO again,
but using the touchpad this time, trying to test if my mouse was the cause. Unfortunately, the BSOD still occurs(also memory management). There is one strange thing that I don't know if it is worth mentioning. I never encounter any BSOD when I was playing
the cracked version of CSGO. However, I always encounter BSOD when I was playing the genuine CSGO from Steam and other online games. Dump files below.

Click here for the dump files

 

Code: ffffc500`9b890500 00000000`ffffffff ffffc500`9b890508 00000000`00080008 ffffc500`9b890510 ffffd983`3a9ac090 ffffc500`9b890518 fffff807`6c8f4f8f*** WARNING: Unable to verify timestamp for EasyAntiCheat.sys *** ERROR: Module load completed but symbols could not be loaded for EasyAntiCheat.sys EasyAntiCheat+0x14f8f ffffc500`9b890520 ffffc500`9b890810 ffffc500`9b890528 fffff807`68db318e registry!RegistryCallback+0x1ee ffffc500`9b890530 00000000`00000010 ffffc500`9b890538 fffff807`6c8f7bfc EasyAntiCheat+0x17bfc ffffc500`9b890540 00000000`00000000 ffffc500`9b890548 ffffd983`28261a70 ffffc500`9b890550 00000000`00000000 . . . fffff807`6c8e0000 fffff807`6c96b000 EasyAntiCheat T (no symbols) Loaded symbol image file: EasyAntiCheat.sys Image path: \??\C:\WINDOWS\system32\drivers\EasyAntiCheat.sys Image name: EasyAntiCheat.sys Browse all global symbols functions data Timestamp: Tue Jan 24 02:38:56 2017 (58862390) CheckSum: 0008F172 ImageSize: 0008B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] It looks like the EasyAntiCheat driver is to blame. The only thing I can suggest is to play without the application installed, or contact the developer so see if they are aware of the issue, and have a fix in the pipeline.

EasyAntiCheat - Don't Bear with the Cheaters

 

Well, I've uninstalled it for now, so I will report back on if it makes a difference, unfortunately I need it to play Squad, which is definitely the game Im putting the most hours into atm.

if this does turn out to be the problem, I will submit a bug report to EAC about this, what should I use as evidence? would the above error information be adequate?

Anyway, thanks for your help, ill get back to you on whether it works or not.

 

Squad.exe was the process running when the crash occurred.

The developer may ask you to send them the .dmp file : send them the one named 012417-3765-01.dmp dated 24 January 2017 5:26pm. Any developer worth his salt should be able to use that to debug his driver.

You could also include the eventlog file which shows this entry:
Code: event[8429]: Log Name: System Source: Application Popup Date: 2017-01-26T17:46:58.198 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FO79DJR Description: Application pop-up: Squad.exe - Application Error : The instruction at 0x0000021302026C60 referenced memory at 0x0000021302026C60. The memory could not be written.[/quote]

 

Thanks for that.

I'll test to make sure, because I've had other games that weren't Squad throw BSOD's and if EAC was the culprit ill send them a message.

 

Well, that driver didnt turn out to be the problem, as I just got another BSOD today, this being the first one while I wasn't gaming as well, how should I provide the dump logs for this, just run the info gathering .exe again and upload the new one?

 

The BSOD you just got could be something else entirely - the first set you provided were categorical about EasyAntiCheat.sys.

Re-run DMLogCollector, upload the zip file, and lets take an objective look at the crashes.

 

Theres the newest log, after uninstalling EAC and playing some Mount and Blade to test if it still happened, this occured aroung 15 minutes after exiting the game.




Attachment 118649

 

Can you check to see if your Razor Naga is using the most up-to-date driver?

 

Righto, everything Razer should be up to date, downloaded Razer Synapse, and hopefully that did it.
Will report back on how it goes.