Windows 10: BSOD while playing games or using Chrome 0x3b

This is my first post on these forums as I've just been lurking before trying to fix my own BSOD problems. But in the end, I decided that creating an account and receiving help from pros would be better than just lurking *Redface

I recently bought my first SSD and proceeded to install Windows anew. I installed Windows 7 64-bit and upgraded to Windows 10 and I thought that my BSOD days were over (I still have my old hard drive with Windows installed with many dumps and partitioned it to install games on it). In the included zip folder are 3 dumps the newest one occurring when browsing on Chrome. The second one happened last night as I was playing Tomb Raider via Steam. The third one happened more than a week ago (possibly during a game of Overwatch) but I DDU'd and installed the newest graphics driver at the time as it had to do with atikmdag.sys. Attachment 98143

I would really like some help on this please! The more BSOD's I get the less inclined I feel to fix my computer and I think about doing a new install once again. I would prefer not to do that and I hope that you guys can help me through this *Smile

:)

 

Phantom Window?

The issue happens no matter what I'm doing. Happened while I was on Chrome, while I was playing games through Steam, and also while I was using Notepad.

 

BSOD while playing games

which game, some machine details would be useful too

 

Forum rules do not allow us to help:

Please remove counterfeit software and resubmit your files so that we can help.

 

You still have a modified hosts file to avoid activation of Malwarebytes software.

 

Guess it didn't remove it when I uninstalled it. I'll get on it once I'm home. Thank you for pointing it out.

 

Here ya go. Is the hosts file supposed to be empty?

 

The hosts file should just have the information as shown below, yours has additional entries that need to be removed

Code: # Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost[/quote]

 

Does the above file not have it empty?

 

Yes all looks good, many thanks for sorting this out.

Here are the details from your crash dump file from 26th Aug.

Code: BugCheck 1E, {ffffffffc0000005, fffff809cda67827, 0, ffffffffffffffff} Probably caused by : luafv.sys ( luafv!LuafvFindTableNode+5dd ) KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff809cda67827, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception[/quote] The probable cause is the LUA virtualisation driver but this is a windows component and it is the correct version so it does not help us. The process that was running when the error occurred was Steam:
Code: PROCESS_NAME: Steam.exe[/quote] I also noticed that your BIOS is not standard (ver FDk) was this a beta version you used? The current Gigabyte website shows a different version F10e which is also Beta but is the most recent. (In general I do not advise using Beta versions unless they solve a particular problem.)

The previous two memory dumps are different but show that you had a system service exception
Code: SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8016f83fb3e, Address of the instruction which caused the bugcheck Arg3: ffffa380dcd61bd0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero.[/quote] Code: FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE BUCKET_ID: MEMORY_CORRUPTION_LARGE PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE[/quote] These would strongly suggest you should run a memory test for your 16GB. The standard test is memtest86+ and this needs to be run for over 8 passes which will take about 1 day.

Once you have done this please report back with the results.

 

I have two sticks of RAM and I have been running 10 passes of memtest two times. One on each DIMM slot that I use. Finished testing one stick and need to do 10 more passes tonight but there is something strange.

When I put either stick of RAM in DIMM slot 1, it runs the RAM at half speed whereas DIMM slot 2 tests it at full speed. Is this normal?

Edit: the CAS timings also change from 9-9-9-24 to 4-5-5-15.

 

Finally had time to run all the tests and Memtest found no errors.

 

Just got a BSOD during a game of Overwatch
Attachment 100886