Problem - MQ2 clients crashing / PC freezing / blue screen

[Dealt21]

Hey all, returning player here...Just started to my group today and I am having issues with MQ2 clients crashing, PC locking up, and blue screen when I restart.

What I have tried -

Making sure that I am not using the new UI engine
Running everything in windowed mode
Lowering fps (80 FPS in background...too high??)
Reinstalled everything
Deleted cwtn plug-ins that I was not using
No administration mode
No compatibility mode

It seems worse when I run the RGMercs Lua...not sure why.

Any other thoughts?

 

[bigdogs175]

I was having issues, not like that, but some and I turned off intelboost and it has gone away.

 

[Cannonballdex]

Hey all, returning player here...Just started to my group today and I am having issues with MQ2 clients crashing, PC locking up, and blue screen when I restart.

What I have tried -

Making sure that I am not using the new UI engine
Running everything in windowed mode
Lowering fps (80 FPS in background...too high??)
Reinstalled everything
Deleted cwtn plug-ins that I was not using
No administration mode
No compatibility mode

It seems worse when I run the RGMercs LUA...not sure why.

Any other thoughts?

Blue Screen sounds like memory issues. If you have more than one stick, try removing all but one and try again, then try another. Rinse and repeat.

 

[Sic]

Hey all, returning player here...Just started to my group today and I am having issues with MQ2 clients crashing, PC locking up, and blue screen when I restart.

What I have tried -

Making sure that I am not using the new UI engine
Running everything in windowed mode
Lowering fps (80 FPS in background...too high??)
Reinstalled everything
Deleted cwtn plug-ins that I was not using
No administration mode
No compatibility mode

It seems worse when I run the RGMercs LUA...not sure why.

Any other thoughts?

Make sure you use framelimiter.

Also - ensure you're not running any potentially conflicting overlays like afterburner, Nahimic, overwolf, etc

You also want to ensure you don't have antivirus or file syncing causing you issues.

 

[dewey2461]

BSOD are likely going to be either bad hardware, or bad/corrupted drivers.

Memtest86+ | The Open-Source Memory Testing Tool

Memtest86+ is an advanced, free, open-source, stand-alone memory tester for 32- and 64-bit computers (UEFI & BIOS supported)

memtest.org

This is my go to first step for BSODs.

It's a stress test for your CPU and RAM. It takes your OS out of the equation. Run it overnight.

 

[Dealt21]

Thank you everyone. I will try some of these things and get back to you. I lowered my frame rates substantially and put background to min. Cpu usage and I think it is getting better. I have had issues with frame rates with my 7900 XTX graphics card in the past.

 

[Sic]

Thank you everyone. I will try some of these things and get back to you. I lowered my frame rates substantially and put background to min. Cpu usage and I think it is getting better. I have had issues with frame rates with my 7900 XTX graphics card in the past.

No. Don't do that.

Use framelimiter.

Putting background frames to min says "I don't want to do shit in the background, please make my too lns fall of ledges and act weird".

Frame limiter not only fixes your background frames, but bypasses the EQ bullshittery with max bg frames set to min.

 

[Dealt21]

No. Don't do that.

Use framelimiter.

Putting background frames to min says "I don't want to do shit in the background, please make my too lns fall of ledges and act weird".

Frame limiter not only fixes your background frames, but bypasses the EQ bullshittery with max bg frames set to min.

Okay thanks. I'll do this instead!

Oh and my shaman got stuck in some rocks earlier....pretty sure it's the fps thing lmao

 

[brainiac]

This is a HARDWARE problem. What is your cpu?

 

[Sic]

This is a HARDWARE problem. What is your cpu?

oh noes! is it the bad intel chip ?

 

[brainiac]

Regular software cannot cause BSOD alone. This is the result of failing hardware or driver bugs. Given recent history it’s more likely hardware. Knowing the BSOD error message is also very useful

 

[Dealt21]