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:
Not sure how to copy the actual memory.dmp file but hope that will help.
Any clues or advice?
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?