New
#41
Ooh, bluescreened again. 50 error.
Edit: Make that two errors. I might unplug my HDD and see if that stops me from bluescreening. That's the only thing that isn't relatively new.
Last edited by Reyjakai; 21 Sep 2015 at 20:10.
Ooh, bluescreened again. 50 error.
Edit: Make that two errors. I might unplug my HDD and see if that stops me from bluescreening. That's the only thing that isn't relatively new.
Last edited by Reyjakai; 21 Sep 2015 at 20:10.
Bumping, I guess. I keep getting bluescreens, and these ones seem to be related to my video card.
So,Code:BugCheck 1000007E, {ffffffffc0000005, fffff80002e894d2, fffff880042f8818, fffff880042f8070} Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )Code:BugCheck 1E, {ffffffffc0000005, fffff8800bcf69d0, 0, 0} *** WARNING: Unable to verify timestamp for e22w7x64.sys *** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys Probably caused by : e22w7x64.sys ( e22w7x64+73ff )Code:BugCheck 10E, {1f, fffff8a00d810500, 0, 84c89b} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )Code:BugCheck 3B, {c0000005, fffff80002e724c5, fffff8800cfc0540, 0} Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )The problem is caused by your graphics driver. Run Display Driver Uninstaller(DDU)Code:BugCheck 3B, {c0000005, fffff960000e3f86, fffff88008aaed00, 0} Probably caused by : win32k.sys ( win32k!memset+d146 )
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again and you should be good to go! This is the guide for DDU: Display Driver Uninstaller: How to use
Update your DirectX drivers.
Run sfc /scannow and chkdsk /f /r.
Install the latest updates from Windows Update.
Do the exact same steps for chkdsk /f /r but instead of typing in sfc /scannow type chkdsk /f /r.
Update your Killer e2200 PCI-E Gigabit Ethernet driver.