Solved Win 8.1 - Fresh Install w/ Multiple Vague BSODs a Day

[Trigger]

Hello,


I finally got my new computer up and running on Friday, and for a couple of days it was going well. I'd installed all my drivers before doing anything, making sure the system was properly configured using the latest updates. Windows Update was fully up-to-date, as was Windows Defender.


Since Sunday night, I've been having constant BSOD's, most of which have been very vague and haven't pointed squarely at any particular driver or hardware fault.


I've since reinstalled Windows using a new installation media to see if that was the cause, to no avail. I've also tried reseating the graphics card and running my RAM through several passes of Memtest; also without luck.


Some days the system will happily let me play a few hours of games, others it won't let me watch a youtube video without a bluescreen.


An odd symptom is that my USB DAC/AMP (FiiO E10) will often skip or jump audio every 2-3 seconds on some boots (others will be fine) unless I'm playing audio via any WASAPI output (foobar).
This skipping also tends to result in Chrome tabs crashing if I'm watching any YouTube videos or similar.


My most recent BSODs have been:


IRQL_NOT_LESS_OR_EQUAL pointing at ntoskrnl.exe
SYSTEM_SERVICE_EXCEPTION pointing at dxgmms1.sys
SYSTEM_SERVICE_EXCEPTION pointing at ntoskrnl.exe
DRIVER_IRQL_NOT_LESS_OR_EQUAL pointing at e1d64x64.sys


However on my original Windows install I recall also seeing a BAD_POOL_HEADER BSOD pointing to ntoskrnl.exe and another pointing at win32k.sys


Thank you for any assistance,


Adam / Trigger

 

[usasma]

I'm late for work. I'll reply back in about 12 hours - or 24 if I get hung up after work.

Meanwhile:
For starters:

At work we start all repairs with a set of diagnostics. Often they find problems that weren't even expected. It's a waste of time to try to fix software on a system that has hardware problems.
Please try these free diagnostics for starters: Initial Hardware Diagnostics
Also, please ensure that you have ALL available Windows Updates (it may take several trips to get them all).

 

[Trigger]

Hi John,

Thanks for the primer, I've given the memory a bash a few days ago with memtest which didn't return any errors, however I gave the HDD tests a run today.

For a little more info, I'm running two 120GB SSD's in RAID 0 for my OS drive. Both SSD's have been tested this week and have shown no bad sectors or other faults. The symptoms I'm having still show when my motherboard runs in AHCI mode using either drive alone for Windows.

As a final test today I've removed my graphics card as I noticed it was still hanging down more than it should, possibly remaining loose in the slot. I'm now on a new, fresh install of Windows 8.1 64-bit using the Intel HD graphics instead and the system has been running constantly for the past 11 hours, which is longer than any other day since my problems first appeared.

However, it may require longer testing to see if I'm not just in a lucky patch right now. I'll update this thread accordingly if I continue to have issues another day or if my GPU was the issue.

Would a slightly loose GPU even cause these errors? Aside from my single dxgmms1.exe BSOD there's been nothing pointing at my graphics drivers.

Again, thanks for any assistance,

Adam / Trigger

 

[usasma]

Yes, an improperly fitted/loose video card can cause BSOD's (it's happened to me!)

The following is from the reports that you generated previously - they probably don't apply to the fresh install of Windows.

You have at least 4 or 5 hard drives. I've gotta wonder if your current PSU is capable of handling the load on the system. To test, please disconnect a lot of stuff that's not currently needed - and then see if the frequency of BSOD's decreases. Also, PSU efficiency decreases w/age - so if this is an older PSU, it may be reaching the end of it's lifespan.

The pattern of BSOD errors is suggestive of low-level/hardware errors. If this is the case, then the low-level errors may not return - but hardware errors will likely return.

If they do return, please start by running Driver Verifier according to these directions: Driver Verifier Settings
You can also get a head start on the hardware troubleshooting by running these free diagnostics: Hardware Diagnostics

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Thu Nov  7 18:12:33.721 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110713-14109-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16404.amd64fre.winblue_gdr.130913-2141
System Uptime:[B]0 days 7:07:11.383[/B]
*** WARNING: Unable to verify timestamp for e1d64x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1d64x64.sys
Probably caused by :[B]e1d64x64.sys ( e1d64x64+2290c )[/B]
BugCheck [B]D1, {fffffa00010acc2b, 2, 8, fffffa00010acc2b}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
Arguments: 
Arg1: fffffa00010acc2b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffffa00010acc2b, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]AV_CODE_AV_BAD_IP_e1d64x64+2290c[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  F6
  BIOS Release Date             08/03/2013
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-OC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov  7 11:04:44.750 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110713-12156-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16404.amd64fre.winblue_gdr.130913-2141
System Uptime:[B]0 days 0:28:05.413[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ObpCreateHandle+3e8 )[/B]
BugCheck [B]3B, {c0000005, fffff8013d1d6738, ffffd000239ecb80, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8013d1d6738, Address of the instruction which caused the bugcheck
Arg3: ffffd000239ecb80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID: [B]0x3B_nt!ObpCreateHandle[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  F6
  BIOS Release Date             08/03/2013
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-OC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Nov  6 11:38:00.861 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110613-14812-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16404.amd64fre.winblue_gdr.130913-2141
System Uptime:[B]0 days 2:22:51.551[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VidMmInterface+1d492 )[/B]
BugCheck [B]3B, {c0000005, fffff80001c81442, ffffd00028328480, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80001c81442, Address of the instruction which caused the bugcheck
Arg3: ffffd00028328480, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: [B]0x3B_dxgmms1!VidMmInterface[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  F6
  BIOS Release Date             08/03/2013
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-OC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Nov  6 09:10:37.613 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110613-11750-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16384.amd64fre.winblue_rtm.130821-1623
System Uptime:[B]0 days 0:05:52.303[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+12df3 )[/B]
BugCheck [B]A, {20, 2, 0, fffff80013790383}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Arguments: 
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80013790383, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]AV_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  F6
  BIOS Release Date             08/03/2013
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z87X-OC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Thu Nov  7 18:12:33.721 2013 (UTC - 5:00)**************************
nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
dump_iaStorA.sys            Thu Aug  1 21:39:52 2013 (51FB0DE8)
iaStorA.sys                 Thu Aug  1 21:39:52 2013 (51FB0DE8)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
e1d64x64.sys                Thu Aug 29 19:55:45 2013 (521FDF81)
TeeDriverx64.sys            Thu Sep  5 14:02:18 2013 (5228C72A)
RTKVHD64.sys                Tue Oct 22 08:31:34 2013 (52667026)
nvlddmkm.sys                Wed Oct 23 02:21:50 2013 (52676AFE)
[/font]

http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
e1d64x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

 

[Trigger]

Thanks John,

The PSU is less than a year old, it's an 850W Corsair from their high-end AX line so I'd not expect it to be struggling. That said my last PSU was the same model which died after roughly the same time so I'm open to the possibility. Sadly I don't have any accurate way to test the power output of the unit.

Reinstalling Windows may have wiped my error slate clean for now, but this week I've reinstalled fresh at least 6-7 times and each time have faced the same kinds of BSODs.

For now, nothing's being particularly screwy except once or twice my DisplayPort connection to my monitor has reset. This is using the onboard Intel HD graphics.

No lockups or BSODs to report yet though.

 

[usasma]

OCCT has a nice looking, free power supply tester (but I haven't used it myself): Home
Please note that the last tab in the program is the Power Supply function.

Another way to "test" a PSU is to remove everything that you don't need right now (spare storage drives, CD/DVD drives, extra cards in slots, fans, etc) and then see if the problems lessen.

If BSOD's recur after repeatedly reinstalling Windows - it's either:
- hardware (most likely IMO) - this includes things like loose cards, overheating, etc.
- incompatibility (this is actually a sub-set of the hardware problems)
- bad 3rd party programs (in other words, test the system for BSOD's before installing additional programs)
- bad Windows disk (unlikely, but still a possibility)

 

[Trigger]

Just tried OCCT, gave me a bit of a scare as it doesn't seem to be compatible with my motherboard. Every voltage reading was way off the mark from where it should be: +3.3V was at 2.03V, +5V at 3.2V, +12V was 3.5V and -12V was 7V.

Did some reading into it to make sure what I was seeing wasn't real and installed a trial of AIDA64 instead. All voltage readings are stable and well within the 3-5% tolerances for power supplies. This includes under load.

The system prior to these issues was water cooled, I realised when I was dismantling everything the other day to do the GPU-less test that the tubing between the CPU and GPU blocks was possibly pushing the GPU downwards and out of its socket slightly by around 1-2mm on the latch end. Is it possible this has been the culprit all along?

 

[usasma]

It's possible that the pressure prevented good contact between the video card and the slot.
The test is to fix it - then see if the BSOD's stop.

If the BSOD's continue, zip up the contents of C:\Windows\Minidump and upload it with your next post (you may have to copy it to your Desktop in order to zip it up).

 

[usasma]

Did you delete a post? I got notified about a D4 error - but can't see it here.

 

[Trigger]

Yeah, sorry about that. My motherboard was showing a POST D4 code most days which the manual says is a PCI resource allocation error.

What isn't listed is the code 04, which on a 7-segment LCD looks the exact same and simply means the PC has come out of S4 sleep. That'd be Windows Fast Boot.

No worries there. Sorry for the confusion.

 

[usasma]

Not a problem - glad to hear it wasn't a problem.

 

[Trigger]

John,

Thank you for offering up assistance during this; I reinstalled the stock air cooler on my graphics card again as a final test and put it back in my system two days ago; been running like silk since.

So it turns out it was just the card being forced out of the slot by my tubing that was to blame for this, I'll see about stopping it doing that when I reapply my loop.

Thanks again, I'll mark this as solved.

 

[usasma]

I'm glad to hear that this is fixed.
Thanks for letting us know!