Wish they would do something about the BSOD's

[Tairros]

I have over a hundred hours in the game at this point, All classes well leveled with some maxed. But now, after all this I can't even play the game because every time I launch it I get a BSOD ranging from immediately to a few minutes in.
I have tried all the fixes I can find. My windows is fully updated, I'm Running an I9-9900k cpu clocking 5GHZ on every core, I have 32GB of Ram running at 4000MHZ, Samsung 970 M.2 SSD, and a GTX 1080. So it is Definitely not a hardware issue or load issue since this game is the only thing running.
I have done a ton of research into other peoples fixes into this and most either don't apply or didn't work. I even re-imaged my OS at one point and it persisted between images.
Just sad to see a game I enjoy so much and I can't even play it anymore.




Edit:
I have the log file now.


This is part of the actual log from the BSOD




PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

ERROR_CODE: (NTSTATUS) 0xc2240c0 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID: {b2970ac3-3b93-468e-afe0-2117476d478d}

IMAGE_NAME: npggNT64.des

MODULE_NAME: npggNT64

FAULTING_MODULE: 0000000000000000

CUSTOMER_CRASH_COUNT: 1


FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c2240c0_npggNT64.des!_IMAGE_npggNT64.des






This shows that the critical process SVCHost was terminated from a failure of npggNT64.des
npggNT64 is Nprotect Gameguard that PSO2 uses.

[AN BIFFED ELF!!!!]

What's your PSU, and is it past its warranty?

[Tairros]

Originally posted by AN BIFFED ELF!!!!:

What's your PSU, and is it past its warranty?

Appreciate the thought on that one, but my power supply is fine. It's only a year old 1400Watt PSU, but even if it was a psu issue, it would have trouble with more than just PSO2 since compared to other things I run, PSO2 is very lightweight.

[Crescens]

What is the message given by the bug check?
Also, have you tried updating drivers? Graphics drivers tend to be one of the worst offenders, and if you reinstalled Windows and immediately reinstalled bad drivers then you would continue to see the problem.

[The Ultimate Despair]

This is a problem with your hardware, not the game, I know it sucks to hear or rather read this, but yeah. Its not the game.

[NeoLoboz]

What’s the error code you get when you get bsod

[Rogue]

Looks like impeding doom for your hardware due to the overclocking.... I recommend a PC stability test. If fails, downclock and test again, If the downclock pass, try to sell off your hardware (If scrupulous, put up information about overclocking. Otherwise I'm sorry for the person who buys your... damaged goods).

[Antineutron]

for some reason I get crashes but only during persona trigger quests where whole screen flickers in random colored bars at random time and if I dont release all buttons, crashes pc without warning or even bsod

and yes only in this game and only on that quest

wonder if its something similar

[Tairros]

Originally posted by Crescens:

What is the message given by the bug check?
Also, have you tried updating drivers? Graphics drivers tend to be one of the worst offenders, and if you reinstalled Windows and immediately reinstalled bad drivers then you would continue to see the problem.

Graphic Drivers fully updated.

Originally posted by Crescens:

What is the message given by the bug check?
Also, have you tried updating drivers? Graphics drivers tend to be one of the worst offenders, and if you reinstalled Windows and immediately reinstalled bad drivers then you would continue to see the problem.

I have a log file now so I am putting it at the end of this comment.
Same one that most people getting the BSOD are getting

Originally posted by Morgoth's Gaming Trove:

This is a problem with your hardware, not the game, I know it sucks to hear or rather read this, but yeah. Its not the game.

It's Really not the hardware. The hardware is relatively new with the oldest part being 1 year old.
I have also done tests on the hardware and it all performs perfectly.
There are reports all over the place of people getting BSOD and only when playing PSO2.

Originally posted by OxNEOxO:

What’s the error code you get when you get bsod

I have a log file now so I am putting it at the end of this comment.

Originally posted by Rogue:

Looks like impeding doom for your hardware due to the overclocking.... I recommend a PC stability test. If fails, downclock and test again, If the downclock pass, try to sell off your hardware (If scrupulous, put up information about overclocking. Otherwise I'm sorry for the person who buys your... damaged goods).

It's Really not the hardware. Only thing overclocked is the Ram and even when it's not, same issue. The hardware is relatively new with the oldest part being 1 year old.
I have also done tests on the hardware and it all performs perfectly.
There are reports all over the place of people getting BSOD and only when playing PSO2.

Originally posted by Antineutron:

for some reason I get crashes but only during persona trigger quests where whole screen flickers in random colored bars at random time and if I dont release all buttons, crashes pc without warning or even bsod

and yes only in this game and only on that quest

wonder if its something similar

That's really interesting. I have read from a lot of reports that the primary cause of the BSOD is the anti-cheat for PSO2 is causing termination of SVCHost which is a critical process, which results in that message when hit with the BSOD.








This is part of the actual log from the BSOD




PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

ERROR_CODE: (NTSTATUS) 0xc2240c0 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID: {b2970ac3-3b93-468e-afe0-2117476d478d}

IMAGE_NAME: npggNT64.des

MODULE_NAME: npggNT64

FAULTING_MODULE: 0000000000000000

CUSTOMER_CRASH_COUNT: 1


FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c2240c0_npggNT64.des!_IMAGE_npggNT64.des


This shows that the critical process SVCHost was terminated from a failure of npggNT64.des
npggNT64 is Nprotect Gameguard that PSO2 uses.

[Requimatic]

Originally posted by Terra Envy:

Originally posted by Crescens:

What is the message given by the bug check?
Also, have you tried updating drivers? Graphics drivers tend to be one of the worst offenders, and if you reinstalled Windows and immediately reinstalled bad drivers then you would continue to see the problem.

Graphic Drivers fully updated.

Originally posted by Crescens:

What is the message given by the bug check?
Also, have you tried updating drivers? Graphics drivers tend to be one of the worst offenders, and if you reinstalled Windows and immediately reinstalled bad drivers then you would continue to see the problem.

I have a log file now so I am putting it at the end of this comment.
Same one that most people getting the BSOD are getting

Originally posted by Morgoth's Gaming Trove:

This is a problem with your hardware, not the game, I know it sucks to hear or rather read this, but yeah. Its not the game.

It's Really not the hardware. The hardware is relatively new with the oldest part being 1 year old.
I have also done tests on the hardware and it all performs perfectly.
There are reports all over the place of people getting BSOD and only when playing PSO2.

Originally posted by OxNEOxO:

What’s the error code you get when you get bsod

I have a log file now so I am putting it at the end of this comment.

Originally posted by Rogue:

Looks like impeding doom for your hardware due to the overclocking.... I recommend a PC stability test. If fails, downclock and test again, If the downclock pass, try to sell off your hardware (If scrupulous, put up information about overclocking. Otherwise I'm sorry for the person who buys your... damaged goods).

It's Really not the hardware. Only thing overclocked is the Ram and even when it's not, same issue. The hardware is relatively new with the oldest part being 1 year old.
I have also done tests on the hardware and it all performs perfectly.
There are reports all over the place of people getting BSOD and only when playing PSO2.

Originally posted by Antineutron:

for some reason I get crashes but only during persona trigger quests where whole screen flickers in random colored bars at random time and if I dont release all buttons, crashes pc without warning or even bsod

and yes only in this game and only on that quest

wonder if its something similar

That's really interesting. I have read from a lot of reports that the primary cause of the BSOD is the anti-cheat for PSO2 is causing termination of SVCHost which is a critical process, which results in that message when hit with the BSOD.








This is part of the actual log from the BSOD




PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

ERROR_CODE: (NTSTATUS) 0xc2240c0 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID: {b2970ac3-3b93-468e-afe0-2117476d478d}

IMAGE_NAME: npggNT64.des

MODULE_NAME: npggNT64

FAULTING_MODULE: 0000000000000000

CUSTOMER_CRASH_COUNT: 1


FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c2240c0_npggNT64.des!_IMAGE_npggNT64.des


This shows that the critical process SVCHost was terminated from a failure of npggNT64.des
npggNT64 is Nprotect Gameguard that PSO2 uses.

Considering that only a small handful of people experience the BSODs.. it's not particularly a problem the developers can work towards fixing. Same thing with the launcher not working for some folks.. not on the game's end.

That being said, an actual Windows dump file is what you need to have. I'm not sure where you pulled that data from (PSO2 error log?), but it won't lead you anywhere from the looks of it.

So, you need to make sure Windows is set up to create dump files of the memory during a BSOD. Then, you can either paste bits of it here, or submit it to some IT forums somewhere to see if they can help you narrow down the actual cause.

I'm willing to help as much as I can, however, I and any professional will tell you that the first thing you need to check are your OCs. If your memory is the only item running outside of stock/XMP settings, you should try dialing it back some. It's easy and should be able to be all done via software now, so.. can't hurt to test that.

Worth noting also: your memory modules can very much be bad without memtest86+ or any other program being able to tell you it's bad. I had a set of modules do this to me a while back; 12+ hours of memtest on each module with no results (15+ passes), yet I kept getting BSODs during gaming. All the errors were different, and my system suddenly quit being able to write dump files.

It was at that point that I just said "yeah, we're gonna replace the memory and see what happens".. and that 2009-build is still running in the other room. Had to replace the PSU in it lately, too. It had enough power to boot up, but upon trying to log on to Windows and initialize the GPU, it would instantly shut off.

It's strange how hardware can mislead you in to thinking it ISN'T the problem.

So, to reiterate:

1. Make sure your system can create Windows dump files.
2. Play the game again to recreate a BSOD.
3. Check the \Windows\Dump\ directory (IIRC) to make sure the file is there.
4. Use something like "WhoCrashed" to analyze your dump file. Whether we do this here or somewhere else is up to you.

After you have at least one dump file to analyze, then try lowering your OCs to see if things change. My first suggestion there would be to dial them back to the XMP setting your motherboard came with. Yes, it's still an OC, and you would be advised to disable even that for thorough testing, but dialing it back there should be enough for the time being.

Ghost Edit: I'm going to save us both some time right here and say this one last thing -- If your BSODs are all for different STOP codes every time, your memory is very likely the culprit and you should look to replacing it. If you had another paired set for testing, that would be the ideal situation.

[Heru]

New products can also be defective, plugs can be loose, bad drivers, corrupted files, missing windows updates or the typical redistributables, malware, etc. The issue is most likely on your side so make that windows dump file for when your PC crashes and see from there.

[Aumires]

I remember a looooong time years ago I had BSODs when I played JP version due to my antivirus getting in the way and also giving a message similar like that one.

I know I am no tech guy but just writing this just in case it is just this.

[Crescens]

@Terra Envy:
Unfortunately, that doesn't say anything useful.
First, the NTSTATUS given is rubbish, it should be 8 digits after the 0x, and that is 7.
Secondly, svchost.exe is the service host process, any service running on Windows could be in there. So without knowing which service's process is being affected, then nothing more can be done.
Third, what is your definition of "lots"? I can see any people reporting these bug checks on the PSO2.com official forums, and yours is the only real one here.

But well, unfortunately there is a lot that could be going on, and your system's overclock being unstable still hasn't really been ruled out. But as a bit of an FYI, if you are using one of the preview versions of Windows 10 then this could be a problem. Anti-cheat software in general works on a white list basis, and the stuff in preview versions of Windows are not part of the white list because they change so often. This also means that anti-malware can also cause this (and these can also run as a service in the svchost executable.)

[SEGA_CM_GaaS]

Hi there, I think the support team could assist you with this issue.
If you haven't yet, please file a ticket with us at https://pso2.com/support#contact-us

[Tairros]

Late response, but after an update to PSO2 shortly after I posted this, everything started working no problem and BSOD stopped completely.

[Black Jesus]

npggNT64.des is the main module of nProtect's Gameguard. Gameguard is running a driver that is causing a critical failure. Svchost is also listed above because it is a container other processes run inside of for security reasons. The issue is gameguard not your hardware.