Windows 7 Windows 7 home premium Bsod. Ntoskrnl.exe + dxgmms1.sys

[Violet5100]

Hello, I'm having a bsod issue with my PC that has been bugging me for a long while now. Apparently Ntoskrnl.exe continues to appear in all of my Bsod mini-dumps and is almost always paired with another exe or system file. This particular pair has shown up several times, And seems to happen whenever I leave my PC running on something for anywhere between 5 minutes to 18 hours. This issue started randomly about a month ugo and since then I've reinstalled my entire OS from scratch and even changed the HDD out to reinstall windows. It's an old computer, But it's been able to keep up thus far and I don't want to lose it to some crap windows issue.

Heres some info.

OS: Windows 7 home premium
Processor: AMD Athlon II x2, 3.10GHz
RAM: 8GB
System type: 64bit
Display: Built in ATI Radeon HD 4200

I'll attach the mini-dump report as well.

I'm hoping that this issue can be resolved quickly, simply, And hopefully without me lossing my mind to 50+ bluescreens a week...

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88002f1a9e0, 0, 0, fffff88003f1f4c6}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessIsrCompletedPacket+46 )

Followup: MachineOwner

Hi,
the above dump file is blaming the graphics system for the cause of the bsod. Most likely driver related and I can see your gpu drivers are quite old. This part of the dump file:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64

Tells me that your missing a critical service pack which may or may not have some bearing on the issue in question. In any case you really need to have that installed as it also contains security updates which as I've mention are critical.

Windows Update readiness Tool:
Link Removed
Some users get issues when trying to install the service pack. If that happens run the above Tool.

Windows 7 Service Pack One:
Link Removed
After you click on the downloads button you'll see a list. You want either the very top download, which is an iso file meaning you'll have to burn it to disk or the second to last download which is an .exe file meaning you should be able to just click it and go... (once it's downloaded of course). It's up to you.

Drivers
atikmdag.sys Thu Jun 30 04:59:27 2011: AMD GPU drivers. Unfortunately these chips are now unsupported but AMD does have a legacy driver created in 2013:
Link Removed

avgidsha.sys Wed Jun 18 20:03:31 2014: AVG AV known on occasion to cause the odd issue. If the bsod persists consider removing AVG and installing MSE for the interim (it's very stable):
http://windows.microsoft.com/en-GB/windows/security-essentials-download

Rt64win7.sys Thu Apr 21 19:15:33 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet please update:
Link Removed
Second download down.

xusb21.sys Thu Aug 13 23:10:17 2009: XBox USB wireless controller BSOD issues in Win7 with 2009 driver please update:
http://support.xbox.com/en-US/xbox-one/accessories/controller-pc-compatibility

Post any new dump files.

 

[Violet5100]

Alright. I've done the steps above and will be waiting to see if another Bsod occurs.

Thank you for a prompt response and help on this subject. I didn't expect to get much help, Or just linked to one of the other threads that I've read over a hundred times in my research on this issue.

Strange thing is that I went and downloaded/updated all my drivers AND installed Win7-SP1 before I posted here. Infact, I double checked that I had downloaded it from windows updates but apparently it didn't work before.

Anyway, Thank you again for the help and I'll keep you upto date on the state of things here.

...Just to be sure, Would you please look over this mini-dump as well and tell me if it has the same issues as stated above? It was an earlier mini-dump from the one I posted first and I'd appreciate some crossed information on the issues I've been having. Again, Just to be absolutely sure about the matter. You have NO IDEA how much I never want to see this Bsod again. Ever.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 3e7d, fffff70001080009}

Probably caused by : win32k.sys ( win32k!memmove+bd )

Followup: MachineOwner

Hi Violet,
The above Bugcheck means memory corruption but drivers can cause this error as well as bad RAM. See how you go for now but if you do get another bsod please post the dump file and we'll go from there..

 

[Violet5100]

Well, thus far I've not had anymore bsod errors, so I think you got it. Thank you so much for all your help!

 

[kemical]

Thanks Violet.. Good luck for the future and you can always post back if need be..

 

[Violet5100]

We have an issue again. I think I may have fixed it myself with some debugging of my own, But just to check to see if my theory is correct, Here's the dump file.

I'm almost 90% sure it was my video drivers again. I had an update from windows and all of a sudden the whole system crashed with the same fuzzy glitching that happened before, As well as a few other key signs that it was the same sort of Bsod.

Another thing that happened is that I can no longer access anything on my bios screen. If I hit any key upon start up, Such as choosing safe mode or anything of that nature, It all locks up until restart.

How fun...

I would love it if you could check to see if it is the same issue as before, Or something of the sort. It COULD be AVG still, As I've been waiting to see if it does funk with stuff, And I'm willing to go back to Avast if need be. I like Avast more then AVG anyway, As AVG's user interface looks like something out of a Hasbro toy. Heh.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002db690e, fffff88007e3eab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+173 )

Followup: MachineOwner

Hi Violet,
sorry to see issue's cropping up again. This Bugcheck can be caused by gpu drivers passing bad data and can also be linked to possible memory issues too. I'm pretty sure this is your system but there doesn't seem any recent updates on the support page:
Link Removed

Violet did you try and remove the original Windows update that started the issue or is it still installed?

Drivers
atikmdag.sys Thu Jun 30 04:59:27 2011: AMD GPU drivers. Unfortunately these chips are now unsupported but AMD does have a legacy driver created in 2013:
Link Removed

avgidsha.sys Wed Jun 18 20:03:31 2014: Link Removed AV known on occasion to cause the odd issue. If the bsod persists consider removing Link Removed and installing MSE for the interim (it's very stable):
http://windows.microsoft.com/en-GB/windows/security-essentials-download

Rt64win7.sys Thu Apr 21 19:15:33 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet please update:
Link Removed
Second download down.

xusb21.sys Thu Aug 13 23:10:17 2009: Link Removed USB wireless controller BSOD issues in Win7 with 2009 driver please update:
Link Removed

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

 

[Violet5100]

I did, and I've not had any bsod after the update was undone. I went ahead and opt out of auto-updating, so it won't happen again. Although, the fact that I cant access my bios anymore is really getting to me in a bad way.

 

[kemical]

Violet try using the keyboard in a different USB slot or if that doesn't work try a different keyboard. Do you have anything else plugged into the USB slots like a printer? If so try removing.

 

[Violet5100]

I've tried using a range of keyboards and the only other thing I've plugged in is a mouse.

On a side note, I'm also currently dealing with a cuple unrelated (or hopefully unrelated) hardware issues. It's mostly cooling issues that have been cropping up with my chip set. Shouldn't effect the bios though. I've delt with the issue in the past about a week after getting the original prefab setup and after my windows reinstall 2 weeks ugo it was *seemingly* ok untill my last bsod. I don't know how the two are related, cause at first I thought it was hardware damage due to overheating...

 

[kemical]

You could also try PS/2 or check the bios settings for a setting which enables legacy USB devices. Another thing to try is clearing the bios. Easiest way I guess is remove the Bios battery for 30seconds or so.