Solved Recent BSOD 0x0000004E while playing Star Citizen

[MrFujiKicker]

Recently, I built my new PC build early June. After all the Windows Update and hopefully, installed all the recent/updated drivers, I've been experiencing some odd BSoD crashes at random times. Some cases, I would experience a random BSoD, while my computer was idle. Another case was related to accessing my Device Manager that somehow triggered the BSoD. Just recently, I was testing/tweaking some game/graphic settings within Star Citizen, while I was alt-tabbed to answer a few messages via Facebook.

I have uploaded the DM Log Collector zip file.

 

[koolkat77]

Welcome to the forum MrFujiKicker,

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

[FONT="Lucida Console"]Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu Jun 19 08:30:00.918 2014 (UTC + 6:00)
System Uptime: 0 days 1:56:33.104
BugCheck 4E, {99, 135fde, 2, 1e685d}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  StarCitizenLau
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue Jun 17 23:51:45.978 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:01.775
BugCheck FC, {fffff900c0848350, d1a0000395c9b863, fffff880094f6040, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44dfc )
BUGCHECK_STR:  0xFC
PROCESS_NAME:  cpuz_asus.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Jun 16 16:22:08.880 2014 (UTC + 6:00)
System Uptime: 0 days 6:12:48.051
BugCheck 1E, {ffffffffc0000005, fffff80002e71ac5, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Jun 16 05:23:01.231 2014 (UTC + 6:00)
System Uptime: 0 days 3:24:26.418
BugCheck D1, {0, d, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Jun 15 04:24:27.552 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:44.722
BugCheck 3B, {c0000005, fffff80002e9bd31, fffff8800933adc0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+171 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun 13 07:03:38.171 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:22.967
BugCheck 3B, {c0000005, fffff80002c4d656, fffff880075a25b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExfReleasePushLock+56 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[MrFujiKicker]

Hello koolkat, thank you for responding. I have ran the Memtest and experienced no errors. However, I did run the memtest on each individual stick separately within their respective slots. I did not test both sticks at the same time. Each stick had successfully went through 8 passes with no errors to report.

I have uploaded the photos of the results via imgur: MemTest - Imgur

I noticed that my BIOS had another update available and currently testing the waters with the new BIOS version 1103. I wonder if the old BIOS version 1008 was the culprit of causing several BSoDs. I will update if I have experienced another one.

 

[koolkat77]

Thanks for the information.

Enable Driver Verifier to see if it catches any misbehaving driver:

• Driver Verifier - Enable and Disable

 

[MrFujiKicker]

Okay, quick update after running Driver Verifier for the majority of the day, while playing some Star Citizen/Watch Dogs. I haven't encountered any issues in regards to BSoDs or any sort of crashing including Firefox/Flash player crashes prior to the new BIOS update. Looks like the BIOS update might have helped any sort of errors I was receiving. Thank you for your help koolkat.

Just in case, if I do receive any additional BSoDs, then I'll remove the "Mark Solved" and report back to this thread.

 

[MrFujiKicker]

Welp, just suffered a BSoD, while playing Final Fantasy XIV. Error Code 0x000000D1. Driver Verifier has been off at this point.

Uploaded the new set of logs.

 

[Arc]

Apparently it is a driver failure (stop 0xD1) but no driver is flagged even in the deepest digging of the crash dump.

Sometimes Steam throws such clueless crashes, but it would be better if you play FF XIV with DV on .... a try to replicate the BSOD with drivers being verified.

 

[MrFujiKicker]

So a little update on the situation. I re-enabled Driver Verifier right after that BSoD and tried to recreate the same situation to force another BSoD. However, I didn't suffer any issues at all. For the past 2 days, I didn't experience anything out of the ordinary compare with the DV off. So at this moment, I'm at lost what to do. I don't think the DV will experience another BSoD.

However, I do suspect that I will suffer the same potential BSoD upon turning off the Driver Verifier. I did experience something odd, while playing FFXIV. With DV off, I had intermittent 1/2 sec freezes within the game. Game did crash twice. Upon the third time, I suffer that BSoD error. With DV on again, I never saw any of those 1/2 sec freezes/crashes within FFXIV. Such a strange case.

Nvidia drivers are up-to-date on the official release. I did not install GeForce Experience, but I do not suspect it being an issue without the extra software. I'll keep the DV on for the next couple of days, but if I do not experience anything, shall I turn it off and hope that my system is fine?

 

[Arc]

That is a total odd situation, and you are not the first person reporting this issue with FF XIV.

Better you contract the game developer. They should have a solution for you.

If it is the fault of the driver actually, DV must have caught it.

 

[MrFujiKicker]

Okay, after several days with Driver Verifier on, I finally caught a BSoD 0x3B. This time, I was playing some Sins of a Solar Empire. Upon exiting the game, I suffer the BSoD. I only exited the game to see why I lost audio, lo and behold a BSoD appeared. Hopefully, this next log will prove to be useful so I can finally be cleared of any issues in the near future.

 

[Arc]

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 http://carrona.org/bsodindx.html#top
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]

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]

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]

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]

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]

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]