blue screen

Forums › Desktop computing › blue screen

fundanglr

170 posts

Master Geek

#173323 19-May-2015 16:05

i used who crashed me and got this, can anyone interpret it

On Tue 19/05/2015 1:46:30 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\051915-32385-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E1D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800854DE1D, 0xFFFFF880061FB6A8, 0xFFFFF880061FAF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Dynamic

3866 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1307859 19-May-2015 16:08

I would google

dxgmms1.sys blue screen

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

Referral links to services I use, really like, and may be rewarded if you sign up:
PocketSmith for budgeting and personal finance management. A great Kiwi company.

xpd

Geek @ Coastguard NZ
13765 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#1307860 19-May-2015 16:10

Either a driver fault or your video could be on its way out..... to my eyes anyway.

Update Windows, video card driver and see what happens.

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree

fundanglr

170 posts

Master Geek

#1307871 19-May-2015 16:24

ive got a reasonably new gtx660 card, ive just changed motherboards to an I3 board, without reinstalling windows so might be some conflicts i guess just did a fresh driver install of the nvidea software so hoping it helps

xpd

Geek @ Coastguard NZ
13765 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#1307877 19-May-2015 16:43

If swapped motherboards, do a WIndows repair or even a fresh install.

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree

Athlonite

1828 posts

Uber Geek
Inactive user

#1307905 19-May-2015 18:16

fundanglr: ive got a reasonably new gtx660 card, ive just changed motherboards to an I3 board, without reinstalling windows so might be some conflicts i guess just did a fresh driver install of the nvidea software so hoping it helps

You'll need to do an clean install of windows then going from one mobo to another will always lead to problems if you don't do a clean install of windows from the same mobo to another of the same make model is all good but never from one mobo to a different one

Lias

5589 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1307909 19-May-2015 18:31

Athlonite:
fundanglr: ive got a reasonably new gtx660 card, ive just changed motherboards to an I3 board, without reinstalling windows so might be some conflicts i guess just did a fresh driver install of the nvidea software so hoping it helps

You'll need to do an clean install of windows then going from one mobo to another will always lead to problems if you don't do a clean install of windows from the same mobo to another of the same make model is all good but never from one mobo to a different one

Not really. Windows 7 and above handle you changing the hardware pretty well most of the time. I mean a clean install is a nice to have, but not always necessary these days by any means.

I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup.

JWR

821 posts

Ultimate Geek

#1307932 19-May-2015 19:04

fundanglr: i used who crashed me and got this, can anyone interpret it

On Tue 19/05/2015 1:46:30 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\051915-32385-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E1D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800854DE1D, 0xFFFFF880061FB6A8, 0xFFFFF880061FAF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

It is pretty much the same as final text says.

The device driver dxgmms1.sys (default location c:\windows\system32\drivers\dxgmm1.sys) generated an unhandled eror i.e. unexpected (obviously) and the Operating System took over at that point and printed your blue screen.

Dxgmms1.sys is part of the DirectX software of the system. But, isn't the actual graphics driver.

The line - 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800854DE1D, 0xFFFFF880061FB6A8, 0xFFFFF880061FAF00)

Gives the code number of the error - 0x1000007E. The next line - Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M is a text code of the same error.

The remainder of the error code line i.e. numbers in brackets are parameters for the error. i.e.

(0xFFFFFFFFC0000005 - The exception code that was not handled

0xFFFFF8800854DE1D - The address where the exception occurred

0xFFFFF880061FB6A8 - The address of the exception record

0xFFFFF880061FAF00 - The address of the context record).

It is nothing to worry about unless it keeps happening. Then it might indicate your OS files are corrupted.

It isn't a hardware failure since it isn't happening in any code that is directly accessing hardware.

It is just one of those bugs that any large piece of software has.

It will probably never happen again and will probably be patched in Windows updates some day.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

fundanglr

170 posts

Master Geek

#1307953 19-May-2015 19:23

thanks bud, im glad i got a clear answer. i recently put an I3 board in , and windows did all the appropriate driver installs but im guessing some of the old crap still lingers , i didnt want to do a fresh install as ive got too much on there but if i have to i have to i guess. PM me if you like, i could learn a lot from your expertise!

sahilchraya

19 posts

Geek
Inactive user

#1353710 28-Jul-2015 19:32

Try system recovery DVD if you got it..
Can try booting up in safe mode and uninstall required driver.
or Need a fresh OS install.