Recent BSOD 0x0000004E while playing Star Citizen

Arc · 26 Jun 2014

Disable verifier. The verifier enable crash dump is not providing any more information about the BSOD.

As per Carrona.org, STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory

And unfortunately I dont know any driver version that works good with GTX 770. You may try the drivers on a trial and error basis:

320.49 WHQL
327.23 WHQL
331.58 WHWL
331.65 WHQL
331.82 WHQL
332.21 WHQL
Any driver released later

Get them from Drivers - Download NVIDIA Drivers

Do a clean install on all of them. Uninstall the previously installed driver first.
Uninstall All nvidia items in Control Panel > Programs and features

- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
- GeForce Experience
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPU.

MrFujiKicker · 30 Jun 2014

Welp, a little update on the matter. I tested out some of the old drivers, 332.21 & 331.82 specifically. Both produced BSoDs. I decided to go with the 2nd to most recent driver release, 334.89. This driver seems stable for me at the moment. Running on 3+ days straight without any significant issues in gaming. I didn't suffer any stuttering issues with FFXIV as I described before. I decided to look more into what was causing it and it pinpointed XAudio2_7.dll DirectX drivers. Removed it and reinstalled June 2010 DirectX update. Cleared any issues that were present in FFXIV.

However, I did suffer a random BSoD with Steam running. As I was navigating through the tabs, I suffered the BSoD. At this point, I concluded that Steam may be causing several issues. I'll just upload the updated logs and I guess I'll stick to running Steam at a minimum for now.

Arc · 01 Jul 2014

Hi MrFujiKicker.

It is a great news that you found one driver that is working stable there. 334.89. Really good news.

I am not finding the BSOD caused during a stream session, but it is the fact that stream causes issues. It causes issues from two different sides, display and network. It would be better if you play the games from outside of steam.

MrFujiKicker · 06 Jul 2014

Suffered this unique one that I haven't seen out of all the BSoDs. 0x1A code. Not sure if this recent dump will give you any info on what's causing the random BSoD. I got this one from closing Chrome, watching a live stream. Had the computer running over 14 hours before the BSoD crash.

Arc · 06 Jul 2014

The new one is a MEMORY_MANAGEMENT (1a) BSOD; and in fact the crash dump is not providing adequate information about the cause of the BSOD.

Generally it occurs due to memory failure. Either a failure from the part of RAM, or any driver passing bad info the the memory.

But if it is a stray one, you may overlook it. If the BSODs continue to occur and the frequency tends to increase, then troubleshooting is needed.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If no error is found, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

MrFujiKicker · 22 Jul 2014

Okay, an update on the matter of my odd BSoD occurrences. From the last post up until now, I suffered an odd pattern of BSoD occurrences every 3 days or so. Everything felt it all directed towards Memory issue. Even though, you (Arc) suggested to re-run all the tests again, I decided to let it ride and get a better feeling of what might cause the random BSoD. In the end, I didn't reach a conclusion what was causing it.

I tried everything physically possible to re-seat the components and different slots, no cigar. So my last attempt, I decided to switch the DRAM profile "XMP" off to default settings of 1600MHz. I had the profile running under 2133MHz during those numerous BSoDs.

After 4-5 days, I never suffered any issues of any applications closing on its own. Everything is running smoothly and that's it. A simple switch from the DRAM freq to default did the trick. Unfortunate that I can't run the 2133MHz profile, but I'll make do with what I have for now and research later why I had issues with the profile in the first place.

Thank you for everything in trying to pinpoint the issue. Going to mark the thread as solve now.

Arc · 23 Jul 2014