[SOLVED] Unrepeatable BSOD, fixed few problems I think, more inside - Windows 8.1 x64

Thanks Patrick!

I'll update the situation with the new 7950 if I get another bluescreen, as well as the Memtest results when I get the chance to do that.

Cheers!

Xivinas
 
I haven't done a Memtest like you told me to, but I plan to tomorrow morning. I had previously switched the video card out from the 270x I had to the 7950. So the 7950 is currently installed. I had another blue screen, dump file attached, that's pretty much the same as the old one I think. I'll run the memtest again and post the results tomorrow in the afternoon.
 

Attachments

If the Memtest results pass, I'll go ahead and take a look at the crash dump as I'm off to bed now. Let me know how it goes.

Regards,

Patrick
 
Thanks Patrick.

Memtest is running now, been ~two and a half passes and no errors so far. Takes like two hours per pass so I'll update after eight.
 
Something interesting. I started playing WoW again and got an error that looks similar to one I've had in league. Mentions referencing memory at "0xFFFFFFFFFFFFFFFFFFFFF" and can't be read. I didn't bluescreen, WoW just had a critical error and shut itself down. Anything to be made of this?
 

Attachments

The first thing I checked was:

Wow-64.exe.

One of the most notorious app hang/crashes for WoW regarding its 64 bit client is rendering with DirectX 11. Do you have DX11 enabled? If so, drop to 9 and let me know how it goes.

Again though, this could just be a manifestation of bad hardware or a buggy display driver. You'll need to do some troubleshooting on the software-end of things.

So long as you're not getting BSOD's, we can likely rule out any major problems for the time being.

Regards,

Patrick
 
Question about my virtual memory paging file size, this is currently what it's set at automatically. You asked me what it was before on like page 4 of this thread and instead of 2944 MB currently allocated it's 16384 MB. Should it be that high?

imgur: the simple image sharer
 
The page file should be twice the physical memory present, I believe.
The only disadvantage to having a higher page file is that it takes up more disk space.
 
Yes, just leave it at recommended; there isn't a really any reason to alter it.
 
This was a new experience. The graphics driver stopped working and "has successfully recovered", or so the message on the taskbar said. Too bad when that was happening it happened ~5 times repeatedly before bluescreening with GRAPHICS_DRIVER_TDR_FAULT error and the following dump file.

Crash happened at desktop with like, skype and a facebook tab open.
 

Attachments

It all comes back to this:

2. If the above BIOS update fails, do you have a secondary video card to test, or perhaps integrated video on that board? If so, uninstall your current video card drivers, shut down, physically remove your video card, install your secondary video card (or enable integrated video), and then install the latest drivers for whichever. See if the crashes stop, and if they do, your GPU is faulty.
Click to expand...

I am going to go ahead and say you have a bad GPU.

Regards,

Patrick
 
Alright fair enough. I'm getting a hold of a friends Nvidia card that he hasn't had an issue with ever. If it ends up working alright I'll be on my way to purchase a new one.
 
Update:

Since August 29th I haven't had an error until just now. On September 1st I removed the 270x and replaced it with my old 560 TI. Today I got a bluescreen with it but I'm not sure if it's the same thing or not. Can you let me know if it points to anything in specific? I was watching a video fullscreened in VLC, and I clicked the button to get out of fullscreen which seemed to trigger the crash.
 

Attachments

Code: 
Child-SP          RetAddr           Call Site
ffffd000`6c29ecf8 fffff803`5abd17e9 nt!KeBugCheckEx
ffffd000`6c29ed00 fffff803`5abd1b10 nt!KiBugCheckDispatch+0x69
ffffd000`6c29ee40 fffff803`5abd0d34 nt!KiFastFailDispatch+0xd0
ffffd000`6c29f020 fffff801`18273d57 nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`6c29f1b0 fffff801`18273ab1 dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0xcf [COLOR=#4b0082]// We crash here.[/COLOR]
ffffd000`6c29f1e0 fffff801`1827b8ee dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x6d
ffffd000`6c29f210 fffff801`1827da77 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x86
ffffd000`6c29f370 fffff801`1827da24 dxgmms1!VidMmiProcessSystemCommand+0x23
ffffd000`6c29f3a0 fffff801`1827db5f dxgmms1!VidSchiSubmitSystemCommand+0x48
ffffd000`6c29f3d0 fffff801`1824cb40 dxgmms1!VidSchiSubmitQueueCommand+0x37
ffffd000`6c29f400 fffff801`18278a1c dxgmms1!VidSchiSubmitQueueCommandDirect+0x174
ffffd000`6c29f490 fffff801`1827d8e4 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x3cc
ffffd000`6c29f500 fffff801`1827db17 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x50
ffffd000`6c29f560 fffff801`18275657 dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x4f
ffffd000`6c29f5e0 fffff801`1826d863 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x1c7
ffffd000`6c29f6b0 fffff801`182856a4 dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+0xb3
ffffd000`6c29f710 fffff801`1813d476 dxgmms1!VIDMM_DMA_POOL::ResizeBuffersInPool+0xb4
ffffd000`6c29f750 fffff801`18115b10 dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+0x27a
ffffd000`6c29f7f0 fffff803`5abd14b3 dxgkrnl!DxgkRender+0x6e0
ffffd000`6c29fb00 00007ffb`d23317fa nt!KiSystemServiceCopyEnd+0x13
00000075`1426e148 00000000`00000000 0x00007ffb`d23317fa

As usual regarding your issues, we were doing some heavy video work. We specifically crashed when the MMS was marking the allocated resources for eviction, which is probably right around (or right at) the time you full-screened.

When you get #140 posts into a thread it's pretty easy to be forgetful, so have you ever had an issue crashing with this currently installed GPU before? If so, then this comes as no surprise. If this however is a completely different GPU that we've yet to try that you can confirm is working in another motherboard other than yours, this is not the GPU's fault.

Regards,

Patrick
 

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

Back
Top