Sign-in / Sign-up
Your question
Solved

Windows 8.1 Login Flickering, then BSOD. However Perfectly fine after restart every time? [Video]

Tags:
  • Windows 8
  • Login
  • Blue Screen
  • Video
Last response: in Windows 8
July 14, 2014 5:01:53 AM

Hello everyone,
I recently purchased windows 8 for the PC that I built, it's around a year old and prior was running windows 7. Anyway, it's a gaming machine and every time I boot up on the PC from scratch, this is important as it doesn't include restarts, the login screen flickers and when I do input my password. It displays a bugged background for a couple seconds and then proceeds to blue screen.
I can't fully read the error messaging but from googling around I'm guessing the error message is something along the lines of:
"VIDEO MEMORY MANAGEMENT INTERNAL"

Here's a short video demonstrating exactly what is happening also;


Here's a link to my windows BSOD dump file if that helps: http://

My PC specs are as follows:
ASRock z77 Pro 4
Gigabyte Windforce AMD 7950 3GB
Intel i5 3570k
Samsung 840 250GB SSD

I've also:
Reinstalled AMD drivers, multiple times, even in safe mode with DDU
Updated BIOS to latest version

If anymore details are needed please ask, this is really bugging me and I can't seem to fix it.

More about : windows login flickering bsod perfectly fine restart time video

Best solution

a b * Windows 8
July 14, 2014 5:49:55 AM

Are you using LucidLogic MVP Virtu software?

If you are, try uninstalling it. Also uninstall the Intel display driver and the AMD drivers. Use DDU to remove the remnants of the Intel drivers and AMD drivers. Go into the BIOS and select PCI Express for Primary Graphics Adapter under Advanced>Northbridge Configuration>Primary Graphics Adapter. Also disable IGPU Multi-Monitor, Render Standby, and Deep Render Standby.

Then boot back into Windows and re-install your AMD display drivers.

Hopefully that sorts it out. Could be the two drivers are tripping over each other during your login.
Share
July 14, 2014 7:01:43 AM

techgeek said:
Are you using LucidLogic MVP Virtu software?

If you are, try uninstalling it. Also uninstall the Intel display driver and the AMD drivers. Use DDU to remove the remnants of the Intel drivers and AMD drivers. Go into the BIOS and select PCI Express for Primary Graphics Adapter under Advanced>Northbridge Configuration>Primary Graphics Adapter. Also disable IGPU Multi-Monitor, Render Standby, and Deep Render Standby.

Then boot back into Windows and re-install your AMD display drivers.

Hopefully that sorts it out. Could be the two drivers are tripping over each other during your login.


I followed your instructions to the letter and I can't tell if it has made it worse or better, I have another video to show what happens, I removed the intel drivers and reinstalled the new beta driver, the older driver, and the current driver. All to no avail.




Also to add to this, I have never installed anything under the name 'LucidLogic MVP Virtu' so I didn't uninstall anything under that name.
m
0
l
Related resources
a c 410 * Windows 8
July 14, 2014 8:08:36 AM

debug info:
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000002, Process heap being destroyed isn't empty.
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR: 0x10e_2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: LogonUI.exe
1: kd> k
Child-SP RetAddr Call Site
ffffd000`2482d618 fffff800`cce209ca nt!KeBugCheckEx
ffffd000`2482d620 fffff800`cce7fcea watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`2482d660 fffff800`cce6bc66 dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+0x1406a
ffffd000`2482d690 fffff800`cce3b51e dxgmms1!VIDMM_PROCESS::~VIDMM_PROCESS+0x52
ffffd000`2482d6c0 fffff800`cce3b50a dxgmms1!VIDMM_PROCESS::`scalar deleting destructor'+0xe
ffffd000`2482d6f0 fffff800`ccca3215 dxgmms1!VidMmTerminateProcess+0xe
ffffd000`2482d720 fffff800`ccd0d722 dxgkrnl!VIDMM_EXPORT::VidMmTerminateProcess+0x3d
ffffd000`2482d750 fffff800`cccf9655 dxgkrnl!DXGPROCESS::D estroy+0xce
ffffd000`2482d810 fffff960`0014abc9 dxgkrnl!DxgkProcessCallout+0x135
ffffd000`2482d870 ffffc001`19f67430 win32k+0x61bc9
ffffd000`2482d878 ffffd000`2482da20 0xffffc001`19f67430
ffffd000`2482d880 fffff901`4064cca0 0xffffd000`2482da20
ffffd000`2482d888 ffffc001`19f67438 0xfffff901`4064cca0
ffffd000`2482d890 fffff803`39cfd180 0xffffc001`19f67438
ffffd000`2482d898 ffffe000`176c6900 nt!KiInitialPCR+0x180
ffffd000`2482d8a0 00000000`00000000 0xffffe000`176c6900





your bugcheck was in the directx graphics code but you seem to have updated drivers and the image is not corrupted in memory.

I would start by with a disable of the ramdisk subsystem on the assumption there is a bug corrupting the memory in the directx heap.

AsrRamDisk \SystemRoot\system32\DRIVERS\AsrRamDisk.sys Thu Jan 12 20:52:38 2012

disable this and see if you get the same issue. (just a guess)

m
0
l
July 14, 2014 9:50:01 AM

Nope, nothing working so far. Going to try a fresh install of Win 8 and then update again. Will update the results!
m
0
l
July 14, 2014 12:03:17 PM

In the end, before I thought i'd try a fresh install. I thought I'd restart 1 more time to see if the first solution did fix it. To my amazement it did! So thank you very much sir! Yes, I did restart it multiple times to see whether it was a fluke. :) 
m
0
l
a b * Windows 8
July 14, 2014 9:23:07 PM

Good stuff, glad to hear.
m
0
l