Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Recent BSOD 0x0000004E while playing Star Citizen

18 Jun 2014   #1
MrFujiKicker

Windows 7 Professional 64-bit
 
 
Recent BSOD 0x0000004E while playing Star Citizen

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.


My System SpecsSystem Spec
.
19 Jun 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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.
Quote:
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   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

Code:
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
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
My System SpecsSystem Spec
20 Jun 2014   #3
MrFujiKicker

Windows 7 Professional 64-bit
 
 

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.
My System SpecsSystem Spec
.

20 Jun 2014   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Thanks for the information.

Enable Driver Verifier to see if it catches any misbehaving driver:
My System SpecsSystem Spec
21 Jun 2014   #5
MrFujiKicker

Windows 7 Professional 64-bit
 
 

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.
My System SpecsSystem Spec
22 Jun 2014   #6
MrFujiKicker

Windows 7 Professional 64-bit
 
 

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.
My System SpecsSystem Spec
22 Jun 2014   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
23 Jun 2014   #8
MrFujiKicker

Windows 7 Professional 64-bit
 
 

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?
My System SpecsSystem Spec
24 Jun 2014   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
26 Jun 2014   #10
MrFujiKicker

Windows 7 Professional 64-bit
 
 

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.
My System SpecsSystem Spec
Reply

 Recent BSOD 0x0000004E while playing Star Citizen




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD happens daily at completely random times, recent error:0x0000004E
Hi, I've been experiencing blue screens almost daily for 6 months now. It all start around the time I upgraded to windows 8 in the summer. Since then, I downgraded to windows 7 and also experienced blue screens daily. I've updated all motherboard drivers (chipset, lan, usb ect) as well as network...
BSOD Help and Support
BSOD after playing APB, 0x000000C4 and 0x0000004E
I got the PFN corrupt while playing APB: Reloaded got the other two crashes after using driver verifier also BSOD before playing BF4
BSOD Help and Support
Anyone else interested in Star Citizen?
Posted something about this earlier, but worded it the wrong way and had it taken down. A bit too much like an advertisement. Anyway, I still think it's worth mentioning here at least and I'm wondering if anyone else has it on their watch list. If you don't know it's a space sim from the creator...
Gaming
BSOD while installing Star Citizen IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
I have come here quite often to figure out problems, but this the first time I've needed to create a profile to seek help. As the title states this issue has only happened while Star Citizen is updating and applying patches. I've recreated the issue twice. I ran sfc /scannow three times which...
BSOD Help and Support
BSOD playing BF3 - error 0x0000004e
Hi, BF3 is now unplayable for me due to crashes, freezes & BSODs (typically 0x0000004e) in every single game. So far I've tried: 1. Updating to the latest video drivers 2. Uninstalling BF3, deleting all game files & re-installing 3. Uninstalling video drivers using Driver Sweeper &...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 02:27.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App