Several BSOD errors, hard to repeat, extremely frequent

Rasket · 24 Sep 2014

Hi guys,

I built a PC about 12 months ago and have had BSOD problems on and off since making it.

The first month of operation was fine. Then during the Battlefield 4 Beta, I started to get BSOD's (can't remember the error), and then in Guild Wars 2. I did some basic troubleshooting but ended up reinstalling windows. This fixed the problem for several months.

Now for the last 6 months I have had increasing amounts of BSOD's, culminating in tonight's new record of 5 in one hour.

They are most apparent in various hard to run video games, including but not limited to the Battlefield 4, Beta, and Release; Aion; Firefall; Dota 2; Star Citizen; Elite Dangerous; Guild Wars 2, ArcheAge. Some of these, like Battlefield 4, were prolific. Some of these rarely ever crashed.

I've also had two blue screens while using Adobe After Effects, one using Photoshop, and one using Blender. I don't use these programs enough at home to have a decent sample size of usage.

99% of the time, the computer never bluescreens in general usage, or in heavy CPU usage. Only heavy GPU usage, from what I can tell. There have been one or two during normal operation for sure, but much rarer than ingame/program.

I have spent what time I can in the last 10 or so months, trying to figure out what it could be. I have done everything from Testing Ram (memtest for 48 hours, passed everything, no fails) to trying hundreds of drivers for every component. I have tried both BIOS on my GPU, but have not flashed it to a different type.

Reinstalling windows might fix it again, but there's clearly a problem that needs to be addressed. I will now attach the two recommend utilities output dumps.

My profile has my system specs too.

Any help would be much appreciated, it's becoming extremely frustrating, and confusing.

Thanks,
R

Edit: Forgot to say, temps under load average at 60o for GPU, 39o for CPU.

essenbe · 24 Sep 2014

Hi Rasket, I'll see if I can help you. first, your dump files list a whole bunch of drivers and Windows Updates. Almost every one is a different bug code. My experience with ones like this are either a bad install, bad memory or a bad overclock. So, first of all, if you are overclocking anything at all, set everything back to default levels. Next I would like you to reinstall your graphics drivers using this method
NVIDIA Drivers - Avoid Problems

Also, accept the idea that some of the games you are playing just cause serious issues for many people. I have helped at least 6 people in the last 2 weeks who had similar issues with Archage. From everything I can gather, it appears to simply be a very badly encoded game. I have had 2 people with otherwise stable machines that would BSOD from trying to install it. BF4, is not quite so bad, but there are quite a few people, including myself, who have serious issues with it. It was patched and patched and every time it got worse. Strangely, many people have no problem with it, others it gives them fits. Finally I had to simply uninstall it. So, at least part of your problem may be the games you are playing.

Next I would like you to test your SSD for any Firmware updates and run Seatools for DOS on your other hard drive (SeaTools for DOS | Seagate) please run both the short and the long test. The instructions are at the bottom of the page.

Please make sure your Windows updates are fully run and properly installed. Also, check your Motherboards web site for your board and install all updated drivers that you use.

Here are the errors reported by your dump files. many of them were reported repeatedly, I only am showing them once.

Code:

dxgmms1
start             end                 module name
fffff880`101b0000 fffff880`101f6000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\5164DC1346000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Apr 09 22:27:15 2013 (5164DC13)
    CheckSum:         00043C9B
    ImageSize:        00046000
    File version:     6.1.7601.18126
    Product version:  6.1.7601.18126
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.18126
    FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That's the Direct X driver from Windows Update

Code:

nvlddmkm
start             end                 module name
fffff880`0f445000 fffff880`100d3000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 12:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics driver

Code:

Wdf01000
start             end                 module name
fffff880`00e5e000 fffff880`00f20000   Wdf01000   (pdb symbols)          c:\symcache\Wdf01000.pdb\03FC6AA4329F4372BE924775887225632\Wdf01000.pdb
    Loaded symbol image file: Wdf01000.sys
    Mapped memory image file: c:\symcache\Wdf01000.sys\51C51641c2000\Wdf01000.sys
    Image path: \SystemRoot\system32\drivers\Wdf01000.sys
    Image name: Wdf01000.sys
    Timestamp:        Fri Jun 21 22:13:05 2013 (51C51641)
    CheckSum:         000CC9CA
    ImageSize:        000C2000
    File version:     1.11.9200.16648
    Product version:  1.11.9200.16648
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     wdf01000.sys
    OriginalFilename: wdf01000.sys
    ProductVersion:   1.11.9200.16648
    FileVersion:      1.11.9200.16648 (win8_gdr.130621-1503)
    FileDescription:  Kernel Mode Driver Framework Runtime
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That is a Kernel mode driver from Windows update

Code:

 iaStorF
start             end                 module name
fffff880`01ca7000 fffff880`01cb2000   iaStorF  T (no symbols)           
    Loaded symbol image file: iaStorF.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStorF.sys
    Image name: iaStorF.sys
    Timestamp:        Thu Jun 27 16:18:46 2013 (51CCAC36)
    CheckSum:         0000DEC7
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Intel Rapid Storage Technology

Code:

asmtxhci
start             end                 module name
fffff880`10182000 fffff880`101eb000   asmtxhci T (no symbols)           
    Loaded symbol image file: asmtxhci.sys
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        Mon Jun 24 12:16:27 2013 (51C87EEB)
    CheckSum:         00075B99
    ImageSize:        00069000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Asmedia USB 3.0 Driver

Code:

 bcmwl664
start             end                 module name
fffff880`05a90000 fffff880`060d2000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Mon May 06 02:33:12 2013 (51875CB8)
    CheckSum:         0064CD56
    ImageSize:        00642000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card

As you can see, the errors shown pretty much run the gamut of everything. Which tends to make the real problem somewhere else. Please try what I posted above and let us know how it goes.

Rasket · 27 Sep 2014

Hi essenbe,

I've done everything you asked, but am still bluescreening.

All drivers, bios and firmwares are up to date. Most recent bluescreen was:

On Sat 27/09/2014 13:51:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-12807-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x80000000030, 0x2, 0x0, 0xFFFFF8000303131C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I think I might have to reinstall windows, which I really don't want to do. Also, if I do reinstall windows, I might still set it up wrong, and have the same problems. I think I should know what this is first.

Edit: I forgot I haven't done Seagate because I don't have discs to burn. Nothing is installed to my Seagate drive, it's just for storage though.

Also, I have a new bluescreen message:

On Fri 26/09/2014 23:51:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-13400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8015800280, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

essenbe · 27 Sep 2014

Please upload Blue Screen of Death (BSOD) Posting Instructions

Either test the Seagate or disconnect it.

Rasket · 27 Sep 2014

New SF tool attached, will find a dvd to burn the test iso to.

IS there possible a USB bootable version of the seagate tool?

essenbe · 27 Sep 2014

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800030204e9, fffff8801203c700, 0}
Probably caused by : memory_corruption ( nt!MiRemoveIoSpaceMap+129 )
Followup: MachineOwner

Code:

nvlddmkm
start             end                 module name
fffff880`0f436000 fffff880`1010a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Sep 13 14:59:50 2014 (5414A236)
    CheckSum:         00C8E3A6
    ImageSize:        00CD4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please Run Memtest86+

Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Rasket · 27 Sep 2014

Ok I have 32gb of Ram, 2 passes took 24 hours. I will do what I can to get 8 passes done.

essenbe · 27 Sep 2014

We have dump files saying Memory Corruption. That is very important. If the Memory is causing the BSOD, the dump files we read will not be correct, the majority of the time.