[SOLVED] Repeated and varied BSODs - Windows 8.1 x64

O

Obso1e7e

Member
Joined
Mar 10, 2014
Posts
14
I built my new computer about 3 weeks ago and since then I've had varied and seemingly random BSODs. There are a few repeaters, but in many, many different forms. The problem is most pronounced when playing games, seemingly more so with games that are fairly unpolished (in beta, known for being buggy, etc). I have two monitors and if I am watching a video on the other while playing a game, it seems to exasperate the problem as well.

My System:
Motherboard: Asus Z87-A ATX LGA1150
CPU: Intel Core i5-4670k 3.4 GHz Quad-Core
Graphics: Asus GeForce GTX 770 2GB
HDD: Seagate Barracuda 2TB 3.5 7200 RPM
SDD: Crucial M500 240GB
PSU: SeaSonic 650W 80+ Gold Certified Semi-Modular ATX Power Supply
RAM: G.Skill Ares Series 8GB (2x4GB) DDR3-1600 Memory
OS: Windows 8.1 64 bit-OEM

Currently I am only running with 4 GB of ram as I'm running through to check if the problem is with the memory (rotating slots and checking for BSODs)

I went ahead and attached the BSOD logs from BlueScreenView as well in a text document.

View attachment Windows7_Vista_jcgriff2.zipView attachment Blue Screen.txt
 
Hi,

We have various different bug checks:

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)

This indicates that an attempt was made to execute non-executable memory.

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

This indicates that the video memory manager has encountered a condition that it is unable to recover from.

Code: 
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`23d1d558 fffff800`01e729ca : 00000000`0000010e 00000000`0000001f ffffc000`0aec19f0 00000000`00000000 : nt!KeBugCheckEx
ffffd000`23d1d560 fffff800`01ecfbbf : ffffe000`00ae7090 00000000`00531cbb ffffc000`0211fdb8 ffffd000`23d1d6a0 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`23d1d5a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=#ff0000][B]dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x18e2f[/B][/COLOR]

From the above call stack, we can see that a Direct X MMS routine called into a watchdog event error, and then the bugcheck. This is generally caused by the video driver behaving improperly, or a faulty video card.

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

BugCheck 3B, {c0000005, fffff803a9d1406c, ffffd0002a57ca40, 0}

Code: 
2: kd> ln fffff803a9d1406c
(fffff803`a9d13e30)   [COLOR=#ff0000][B]nt!ExDeferredFreePool+0x23c[/B][/COLOR]   |  (fffff803`a9d142d0)   nt!ExFreePoolWithTag

^^ The exception occurred in nt!ExDeferredFreePool which indicates probable pool corruption.

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

^^ This appears to be the case, indeed.

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

KERNEL_SECURITY_CHECK_FAILURE (139)

This bug check indicates that the kernel has detected the corruption of a critical data structure.

BugCheck 139, {3, ffffd000208b36d0, ffffd000208b3628, 0}

The 1st parameter of the bugcheck is 3 which indicates that a LIST_ENTRY was corrupted. Code 3, LIST_ENTRY corruption. This type of bug check can be difficult to track down and indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list).

-- FAILURE_BUCKET_ID: X64_0x139_cng!g_pool+e0

^^ Windows Kernel Cryptography, Next Generation driver.


1. Uninstall Asus AI Suite (or PC Probe).

2. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely causing conflicts:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

3.
Code: 
CORK95    fffff800`031d2000    fffff800`031e0000    Wed Oct 31 04:59:51 2012 (5090e887)    000090ab        CORK95.sys

^^ I believe this might be a trojan or some other form of malware. It has empty values and no documentation whatsoever. Due to this, I'm going to have you head over to the proper forum here.

Make a thread here - Security Arena - Sysnative Forums

Be sure to follow this first before making the thread - https://www.sysnative.com/forums/security-arena/2507-malware-removal-posting-instructions.html

4. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

5. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

Regards,

Patrick
 
I removed Asus AI Suite, I removed Avast with the utility, I turned on Windows Defender. I ran malware bytes and removed 4 objects. I have removed Daemon Tools completely. A new update to my drivers had just come out, and I tried it out for a few hours. Unfortunately it didn't seem to fix the problem, so I went back to one that seemed to have been around without updates for a few months from November, unfortunately the problem is still occurring.

I have an old graphics card, I am going to plug that in and see if it fixes the problem, but otherwise, what else can I do?
 
If you crash again with the different GPU installed, attach the latest crash dumps and we'll proceed accordingly. Remember to uninstall your drivers before replacing the video card, and then installing the proper ones for the different card.

Regards,

Patrick
 
Patrick said:
If you crash again with the different GPU installed, attach the latest crash dumps and we'll proceed accordingly. Remember to uninstall your drivers before replacing the video card, and then installing the proper ones for the different card.

Regards,

Patrick
Click to expand...


I installed my old graphics card, a Radeon HD 4870. It has been giving me notable problems, but not unlike the types of problems it gave me before I replaced it-though more exasperated. My old graphics card (the 4870) would often give me flickering black (and sometimes grey) boxes when playing games, this problem was exasperated by dark colors. This problem would only happen when starting my computer from a full power off state (such as when I booted it up in the morning) and was usually fixed by letting the computer sit for a bit and then restart. Towards the end of my old computer's life, I reached the point where sometimes I wouldn't be able to successfully restart at all. However, I could turn off the power, turn it back on quickly and go from there, which would generally fix the problem.

Currently, the card is showing similar problems, but it doesn't seem to be fixed by restarting and, in fact, doesn't seem to be able to restart successfully, and when it does I invariably have graphical errors on the screen (multicolored lines, things of this nature). Unfortunately right now just powering off and turning back on doesn't fix the graphical defects. My old computer also ran much hotter. Obviously I'm not worried about fixing the problems with this current graphics card, it's quite old, but I figured the information may be relevant to the issue. That said, I have had a few BSODs since I installed in, but not with the frequency of regularity that I experienced before, and they seem to be different errors. Going to attach them here all the same.

Thank you for the assistance.

View attachment Blue Screen - Batch 2.txt
 
Unfortunately, those are .txt files (cannot run through WinDbg). Can you please either manually zip up and attach any crash dumps located in the Minidump directory, or re-run the collection app?

Regards,

Patrick
 
installed my old, defective Radeon 4870 graphics card.
Click to expand...

Pardon, but why would you install a known defective piece of hardware over a piece of hardware we're testing to see if it's the culprit? :grin1:

Do you have another GPU laying around, or perhaps integrated graphics?
 
Patrick said:
installed my old, defective Radeon 4870 graphics card.
Click to expand...

Pardon, but why would you install a known defective piece of hardware over a piece of hardware we're testing to see if it's the culprit? :grin1:

Do you have another GPU laying around, or perhaps integrated graphics?
Click to expand...

Honestly? I forgot that I integrated graphics were a thing. I haven't had that as an option since 2007, so I didn't even think to check to see if I had them. I didn't have an extra GPU, so I made due with that one. Either way, I've taken it out, switched to integrated graphics and am going to go give it a stress test.
 
Integrated graphics still hold a very special place in my heart! :lol:

Great, keep me updated.

Regards,

Patrick
 
Patrick said:
Integrated graphics still hold a very special place in my heart! :lol:

Great, keep me updated.

Regards,

Patrick
Click to expand...

Well, everything graphically intensive is pretty laggy. Lowest settings, all that. Nothing you don't expect from low end graphics though. So far, no BSODs. I've got to work early in the morning so I'm going to pass out, but I'm going to leave it on and doing something graphically intensive to see if anything happens.
 
Indeed, it'll run terribly, but we're checking for crashes, not worrying about performance. You don't have to leave it on all night and doing something intensive. You can simply use it when you have the chance.

In any case, keep me updated.

Regards,

Patrick
 
Patrick said:
Indeed, it'll run terribly, but we're checking for crashes, not worrying about performance. You don't have to leave it on all night and doing something intensive. You can simply use it when you have the chance.

In any case, keep me updated.

Regards,

Patrick
Click to expand...

I've been using it for the last 5 hours off and on. Since it is integrated it obviously only supports one monitor, so I've not been able to properly recreate the circumstances that seemed to exasperate the crashes before (Video on one screen, game on the other) but I have been gaming with some videos on in the background, just listening to them. It was running perfectly until just now when I got another bsod. Here is the minidump.

View attachment 031314-4015-01.zip
 
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This indicates that a system thread generated an exception which the error handler did not catch.

BugCheck 1000007E, {ffffffffc0000005, fffff80001e5b17c, ffffd00022890318, ffffd0002288fb20}

^^ The 1st parameter is c0000005 which indicates an access violation occurred, let's see what caused it:

Code: 
0: kd> .exr 0xffffd00022890318
ExceptionAddress: fffff80001e5b17c ([COLOR=#4b0082]dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation[/COLOR]+0x000000000000002c)
   ExceptionCode: [COLOR=#ff0000]c0000005 (Access violation)[/COLOR]

^^ Direct X MMS.

Right, so we're on integrated graphics and still seeing Direct X faults. No good...

Let's run Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
So far, here is what I've got.

Slot 1, Stick 2-14 passes and 36 errors
Slot 1, Stick 1-8 passes and 1746 errors
Slot 2, Stick 2-14 passes and 6 errors
Slot 2, Stick 1-10 passes and 334 errors

I should have the last 2 slots done in about 3 days.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top