Persistent BSOD playing Day Z/AoE HD - 1E & 3B, dumps included

Ronanman · 10 Jan 2014

CPU
AMD X4 "Raid" AMD FX-4 4100 3.6GHz DDR3 Quad Core Gaming System

RAM
GeIL Black Dragon 16GB (2x8GB) DDR3 PC3-12800C11

Motherboard
Award Modular Bios v6.00pg

Graphics
KFA2 GeForce GTX 660 2048MB GDDR5 PCI-Express

Storage
Seagate Barracuda 7200RPM 1TB SATA 6Gb/s 64MB Cache - OEM (ST1000DM003) HDD

Microsoft Windows 7 Home Premium SP1 64-Bit

So I had this built in early August 2013, and since then have had a few Blue Screens of Death playing League of Legends, and sometimes when im not gaming.

In the last few days I have downloaded Day Z and when trying to play, every 15 minutes or so I will BSOD with the error 3B. The weirder thing is that every time it happens, my PC restarts and my brother's internet cuts out (he is on the other side of a wall). We have no idea why that happens and need help!
It BSOD'd 4 times playing Day Z yesterday, and then again tonight when playing Age of Empires HD, but with a different error code - 1E.

I would be very grateful if someone could point me in the right direction - I have tried googling but there doesn't seem to be much help for the particular error codes I am getting.

Repeated error from Day Z: imgur: the simple image sharer[1]

Once off error from Age of Empires HD imgur: the simple image sharer[2]

Thanks!

Ronanman · 11 Jan 2014

Bump!

Ronanman · 14 Jan 2014

Happened again yesterday, this time with a new code that I haven't seen recently. (0x0000007E) Also, this time I wasn't even gaming.

Included are the new dump files, hope someone can help! :)

koolkat77 · 14 Jan 2014

Code:

dtsoftbus01.sys Thu Jun 20 13:22:51 2013 (51C2ADCB)

Daemon Tools driver [br] Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Code:

AppleCharger.sys Thu Mar 8 07:48:06 2012 (4F580FD6)

GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
Driver Reference Table - AppleCharger.sys

Follow:

Arc said:

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

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
(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
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive(s): Disk Check

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

If this does not provide stability. Test RAM.

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.

Code:

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Jan 13 20:20:47.956 2014 (UTC + 6:00)
System Uptime: 0 days 3:11:38.470
BugCheck 1000007E, {ffffffffc0000005, fffff80002e8db2e, fffff88002fc47c8, fffff88002fc4020}
Probably caused by : afd.sys ( afd+2ca31 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Jan  9 04:00:48.148 2014 (UTC + 6:00)
System Uptime: 0 days 0:39:39.662
BugCheck 3B, {c0000005, fffff8800100ad6a, fffff8800977da10, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+3ea )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  DayZ.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Jan  9 03:20:28.142 2014 (UTC + 6:00)
System Uptime: 0 days 0:32:58.640
BugCheck 3B, {c0000005, fffff880010c4d6a, fffff8800b732a10, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+3ea )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  DayZ.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Jan  9 02:46:50.618 2014 (UTC + 6:00)
System Uptime: 0 days 0:07:50.726
BugCheck 3B, {c0000005, fffff880010b8d6a, fffff8800caf8a10, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+3ea )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  DayZ.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Jan  9 02:38:18.415 2014 (UTC + 6:00)
System Uptime: 0 days 8:16:28.914
BugCheck 3B, {c0000005, fffff8800109ad6a, fffff8800cd4ea10, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+3ea )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  DayZ.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Jan  8 04:11:11.022 2014 (UTC + 6:00)
System Uptime: 0 days 3:08:48.520
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : afd.sys ( afd+505b0 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  DayZ.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``