BSOD on Windows 8.1 anytime I use my second monitor- Still unsolved!

SirWillow

Reputable
Apr 8, 2014
9
0
4,510
updates at end of thread

New computer- about a month old. Haven't had any problems with it and it's been running beautifully until a couple of days ago when I started getting the newest version of the BSoD. Took me a bit to figure out what (sort of) was triggering it, but it's pretty much anytime that I start to use my second monitor to run a program, then shortly after that I'll get the crash. I can run pretty much anything on one monitor, and as long as I do that, I'm fine- even multiple programs. But as soon as I open or drag something to the second monitor it's just a matter of a few minutes until it will reboot on me.

The message I'm getting on the BSoD says that it's "Memory_Management" with no codes or other information.

I've run the memory diagnostic on full passes 8 times now and it hasn't found anything. All drivers are up to date, and I went ahead and tried the latest beta build for my nvidia 770 and that didn't work either.

system specs:
Intel Core i5-4670 CPU @3.40GHz (not overclocked)
16.0 Gig's Ram
Win 8.1 64bit
Nvidia GTX 770 2Gig
AData XS900 HD (I believe this is my 255Gig SSD drive)
WDC WD10EZEX-08RKKA0 western digital 1 Tera HDD
Intel 8 Series/ C220 Series SATA AHCI Controller - 8c02
Realtek PCIe GBE network adapter
Onboard Realtek Audio

Running WinDbg I get the following:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`04604000 PsLoadedModuleList = 0xfffff801`048c8990
Debug session time: Tue Apr 8 18:47:42.485 2014 (UTC - 5:00)
System Uptime: 0 days 0:24:50.126
Loading Kernel Symbols
...............................................................
......................................Page 118343 not present in the dump file. Type ".hh dbgerr004" for details
..........................
.......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`ff42f018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41793, fffff6800016c0c0, 5, 4}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+ea52 )

Followup: MachineOwner
---------

Not sure how to copy the actual memory.dmp file but hope that will help.

Any clues or advice?
 

SirWillow

Reputable
Apr 8, 2014
9
0
4,510
Well, I'm optimistic that I might have figured it out and fixed it. Been wracking my brain trying to remember what I might have changed, and remembered that when I updated Java several days ago I also had it remove the older versions of java that were installed. when I was getting the crashes I'm almost positive I had a web browser open each time, so starting thinking it might have been making a call for that old java, couldn't find it, and would crash. Why it would only do it using 2 monitors I don't know. but in any case I downloaded and installed an older version of java in addition to the fully updated and so far so good.

Still doing some testing but so far so good. I'll update later on.
 

SirWillow

Reputable
Apr 8, 2014
9
0
4,510
Well, still getting the crashes and really hoping that someone will take a look and help me out here. Error messages I'm getting now are:
Page Fault in Nonpaged Area
PFN List Corrupt

Last scan of the memory.dmp file gave me this:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`c2005000 PsLoadedModuleList = 0xfffff801`c22c9990
Debug session time: Mon Apr 14 15:07:39.619 2014 (UTC - 5:00)
System Uptime: 0 days 0:42:22.260
Loading Kernel Symbols
...............................................................
..............................................Page 103bd2 not present in the dump file. Type ".hh dbgerr004" for details
..................
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7f79a018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 9b7bf, 1, 0}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )

Followup: MachineOwner
---------

again, running the memory diagnostic over several sweeps returned no errors. Any clues?
 

SirWillow

Reputable
Apr 8, 2014
9
0
4,510
Took a look at the RAM, pulled it out and switched the slots the two SIIMs are in. Now when I run the MemTest (full test) it gets to 21% and then sits and doesn't progress further. Doesn't matter how long I let it sit. It doesn't get past that. Doesn't show any errors, it just plain doesn't progress.

Would really like some help and hoping someone chips in. This a sign that I've got bad RAM or something else?
 

DSMjunkie

Reputable
Apr 18, 2014
1
0
4,510
So far, I have not actually been able to solve this. That being said, I have been able to stop the BSODs by switching back to the 'Microsoft Basic Display Adapter' driver. You have to disable windows updates, otherwise, the next time you reboot, it'll install the driver again, and you'll start getting your BSODs again.

1. Go into device manager, and uninstall the device (also remove the driver package, and any NVIDIA software).

2. Disable automatic driver updating.
This is an excellent guide to disable automatic driver updating:
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

3. Reboot the computer. It should automatically install the Basic Display adapter.

4. Verify that you are using the Microsoft Basic Display Adapter in Device Manager.

Until the NVIDIA Experience driver is compatible with the 770 and Windows 8.1 I guess its all we've got...