Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Ton]

Until a few days ago I didn't have any problems at all playing all kind of files (dvd, mkv's, blu-ray's etc.). But the last few days it happened twice that, in the middle of playing a dvd and playing a mkv, I got a blue screen. The movie stopped playing and Windows (7 Professional 64 bit, FWIW) rebooted after which I could choose to start it normally. After restarting normally everything was fine again and I could watch until the end.
What could be the cause of this ? Could it have to do with MC 17 or is it more probably a hardware or Windows issue ?
Both files were on the same hard disk, if this is of interest.

[JimH]

A blue screen is a hardware or driver problem.

[wewilli1]

I agree with Jim.  It's unlikely that MC or any other application caused the BOD.  It is very likely that there is a hardware or driver problem.

[Ton]

Thanks for the replies.
I did not change any drivers lately and, as I wrote above, I didn't have any problems before.
Yesterday I could watch a blue-ray of 2 hours and all went well.
Does this make it probably a hardware problem and do you have any idea in which direction I have to search then ? Or can it be anything ?

[InflatableMouse]

Many things can cause a STOP error and it will be impossible to track it down without more info.

I can try and help you track it down but it probably won't be easy.

Start by locating c:\windows\minidump and see if you have any recent files in there. If not, we need to adjust your system settings to have Windows create a minidump file and wait for it to bluescreen again.

In the meantime, go to start/run, type eventvwr and find System under Windows Logs. Browse to the date/time of the last STOP error you received and find the event message for it. Open it (double click), use the Copy button to place it in the clipboard and paste the contents here in a reply.

If you have a few recent minidump files, go to osronline.com and upload one. Place the entire results contents here between [ code ][ /code ] tags.

Hope you manage, apologies I'd explain better but I gotta run.

[Ton]

Thanks InflatableMouse for your help.
I had 2 minidump files, one for each crash. I uploaded the last one to  osronline and this is the result. ( I hope I do this the right way).

Code: [Select]

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`01a5e000 PsLoadedModuleList = 0xfffff800`01ca2670
Debug session time: Sun Nov  4 17:35:43.117 2012 (UTC - 5:00)
System Uptime: 0 days 0:37:20.695
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8800438168b

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  7

LAST_CONTROL_TRANSFER:  from fffff80001adc569 to fffff80001adcfc0

STACK_TEXT: 
fffff800`019a2d28 fffff800`01adc569 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`019a2d30 fffff800`01adaa32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`019a2e70 fffff880`0438168b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0c6a8fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiUpdateCurrentIsrFrameTime+0x8f


STACK_COMMAND:  kb

FOLLOWUP_IP:
dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f
fffff880`0438168b ff156f290000    call    qword ptr [dxgmms1!_imp_KeQueryPerformanceCounter (fffff880`04384000)]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

Followup: MachineOwner
I also found an "Error" log and a "critical" log a few seconds after the "error" log.
Because I don't know how to post them (also with the tags ?) I have attached both as a txt file. If that is not correct , please let me know how to do it the right way.
Ton

[InflatableMouse]

http://support.microsoft.com/kb/842465

Looks like we don't have to go driver hunting It's most likely an overheating or damaged cpu problem as I don't believe you would need a microcode update (don't ask).

You'd need CPU-Z, RealTemp or CoreTemp and Prime95.

Unpack and/or install.

The following procedure **may** permanently damage your pc!

Start CPU-Z, RealTemp or CoreTemp (or both). Place the windows so they are visible and make note of the temperatures and distance to TJ Max. Basically this last one is your headroom.

Start Prime95. It will ask to Run a Torture Test. Basically this will run an infinite test calculating prime numbers on all cores. The way it does it maximizes the amount of power your cpu will consume and generate a lot of heat. If cooling is insufficient, your pc may crash (stop error/bsod), lockup or make a calculation fault but continue to run. It may damage your cpu too if it gets too hot and doesn't crash/reboot/lockup. You need to pay attention to the temperatures and stop it before that happens.

So, the reason you need realtemp/coretemp visible is because if your temperatures rise and TJ Max crawls closer to zero, you can stop Prime95 before bad stuff happens. DONT CLOSE Prime95, it actually minimizes it and it continues to run in the background (Yes this is really stupid, I know). You need to choose menu Test/Stop and choose stop all workers, then click OK. Or, maybe quicker is right click the green icon in the notification area and choose Stop or Exit. You may want to cancel the Torture window and make yourself familiar with the Test menu and the right click icon before you actually start the test. If you do you can restart the test by choosing Options/Torture test. This pops up the same window again.

Obviously, if you decide to continue, I'm not responsible for any damages as a result.

Choose to run In-Place large FFTs, leave the rest and click OK.

Several things can happen:
- Nothing. Prime95 runs for 24 hours, temperatures are good, no faults, no crashes. Considering the bugcheck code you got, I think this is unlikely.

- It crashes/reboots/hangs. If it didn't overheat, your CPU has an issue. It may be damaged, have too low voltage or possibly an incorrect BIOS setting. It needs to be investigated.

- It makes a calculation fault (icon in a thread window will turn red). If your temperatures are good, then your CPU has a problem. It may be damaged, have too low voltage or possibly an incorrect BIOS setting. It needs to be investigated. If this happens in a few minutes you may choose to let it run to see what the temperatures will do after a few hours.

- It overheats, shuts down or crashes/hangs your pc. Whatever you do, DONT SHUT OFF YOUR PC OR PULL THE PLUG! This is important. If you do, your fans stop rotating and your CPU is left shimmering in its own heat. If you must, push the reset button. Fans will almost always speed up to a maximum and your pc tries to reboot. If it doesn't, wait a minute with the fans at maximum and then shut it off or reset it.

Assuming you are not overclocking (are you?), assuming your BIOS is set at defaults and you've not changed anything (have you?)  you *may* have a faulty power supply. If its unable to provide stable voltage to your CPU it may cause blue screens or cause calculation errors. This is something we need to investigate when we know the results if you decide to continue to do this.

Generally, Prime95 is fairly safe but please do pay attention. The temperature meters support alarms. If you need to pee or fetch a beer, configure an alarm and choose a safe threshold. You can test the alarm by setting a threshold lower than the current temperature.

Let me know if you have any questions.

[Ton]

Thanks again for your elaborate help.
I will probaly do the tests tomorrow. But how long should I run Prime95, when it will does not crash, reboot etc. within a short time ?
And do I need CPU-Z AND Real Temp or CoreTemp ?

[InflatableMouse]

Well considering you got the blue screens within the playtime of a movie, I would expect Prime to fail within a few hours. If it doesn't, run it 6 to 8 hours or as long as you can. Overclockers consider their system (CPU) >99% stable when it passes the 24 hour mark. But to run it overnight you need to either have your bed next to your pc so the alarm wakes you up, or be confident enough that cooling is absolutely sufficient.

You don't actually NEED cpu-z but either CoreTemp OR RealTemp is required.

I use CPU-Z to watch the frequency and voltage fluctuations. I forgot to explain that. Not very important unless you need to start troubleshooting.

[Ton]

Prior to running Prime95 I checked the (Noctua) cooler of my cpu (Intel Core 2 Q6600) and saw that it had collected rather much dust. (Could this have been the culprit ?). I cleaned it first with a brush and a brush.

Meanwhile I have Prime 95 running for about 2 1/2 hours and everything goes fine until now. No crashes, faults etc.
The maximum reached temperatures for the 4 cores until now are: 59, 58, 54 and 54 C respectively.
TJ Max was automatically set to 100 C in CoreTemp and RealTemp as well.

So apparently there is no overheating until now ?
My BIOS settings are default btw.

[InflatableMouse]

Sounds good. 60C is a very decent temperature for 2,5 hours of full load with Prime.

Since you cleaned it out there is no way to tell if that was the issue, but let it runs for a few more hours. If nothing happens, just watch some move movies in the coming weeks until it happens again. If it happens again, upload the minidump like before and check whether the its the same one (or post it here I'll have a look) and we'll pick up from there.

If it stays away, the dust may have been the culprit.

[Ton]

Thanks again.
After 4 hours of Prime 95 still no problems !
Have watched another movie and that went well as well.
If/When it happens again I will report back. I hope of course it will stay away