New
#11
Go ahead and disable the verifier. Then let the system crash as usual and wrap the dumps in a zip.
Best Regards,
Frederik.
Go ahead and disable the verifier. Then let the system crash as usual and wrap the dumps in a zip.
Best Regards,
Frederik.
Just tried a restart after 18hrs of uptime, no BSOD. I'm going to let it run until tomorrow night and try again.
Ran for 23 hours. During which, played CS:GO for a few hours, and used Adobe Fireworks.
Got the BSOD on shutdown. Dump files attached.
Please reinstall DirectX, seems like the files are somehow corrupted.
Download: DirectX End-User Runtime - Microsoft Download Center - Download Details
Best Regards,Code:2: kd> k Child-SP RetAddr Call Site fffff880`0a3e92a8 fffff800`0307df0f nt!KeBugCheckEx fffff880`0a3e92b0 fffff800`030d52ee nt! ?? ::FNODOBFM::`string'+0x43d51 fffff880`0a3e9410 fffff880`074ac756 nt!KiPageFault+0x16e fffff880`0a3e95a0 fffff880`074d46fc dxgkrnl!DXGADAPTER::ReleaseReference+0x16 fffff880`0a3e95d0 fffff880`075180ea dxgkrnl!DXGADAPTER::DestroyHandle+0xac fffff880`0a3e9600 fffff880`075177e0 dxgkrnl!DXGPROCESS::Destroy+0x35a fffff880`0a3e96b0 fffff960`001967a4 dxgkrnl!DxgkProcessCallout+0x268 fffff880`0a3e9740 fffff960`00195ea3 win32k!GdiProcessCallout+0x244 fffff880`0a3e97c0 fffff800`033a8641 win32k!W32pProcessCallout+0x6b fffff880`0a3e97f0 fffff800`0338bbdd nt!PspExitThread+0x4d1 fffff880`0a3e98f0 fffff800`030c9cda nt!PsExitSpecialApc+0x1d fffff880`0a3e9920 fffff800`030ca020 nt!KiDeliverApc+0x2ca fffff880`0a3e99a0 fffff800`030d64f7 nt!KiInitiateUserApc+0x70 fffff880`0a3e9ae0 00000000`775b2c1a nt!KiSystemServiceExit+0x9c 00000000`0338fba8 00000000`00000000 0x775b2c1a
Frederik.
Already did that once. Must not have fully uninstalled something?
Do I need to do more than just uninstall and reinstall? Any other files I need to delete manually?
Oh alright. We could try to download them one by one, starting from page 3 on Filehippo.
DirectX 9.0c (Jun 10) - History - FileHippo.com
I'm not sure I understand what I'm doing here... When I run the installer for the earliest release, it just checks to see if any newer versions are installed, which DirectX11 already is...
Strange.
Go ahead and boot Windows 7 without any devices plugged in. If you're using a log-on password, disable it for a short time. Also ensure that cables are tight towards the Graphics Card, and blow the fans for dust.
The dxgkrnl signature in your stack makes me wonder.
Best Regards,
Frederik.
Cords are tight in the back, however (and I just noticed this last night, never even occurred to me that it could be related) the slats between the removable PCI panels does very slightly interfere with the connection to the input. I was getting a slower... drag effect I guess... on one monitor and not the other.
I was thinking about cutting them away (area outlined in red)... might that help?
Attachment 226686
You can try that, as far as I'm concerned you can actually bend those from the inside of the case, and then pull them out. Sounds interesting, definitely worth a watch.
You might also want to plug out one of the monitors, just to see if it'll change anything at all. Also because your DirectX was blamed, this is a pretty good place to dig in.
Nice catch,
Frederik.