Solved BSOD Windows 7, random

[MicroMister]

Hey guys,

My custom built pc, which I have had for a few months, crashed twice randomly tonight. The first it just black screened and my music came out as some white noice, and the second i got a BSOD. No new software or hardware within at least this week, and no backups or restore points (yeah, i know, i've been busy). No real idea why yet, but i have the dump files:
https://dl.dropboxusercontent.com/u/30269671/010614-25630-01.dmp
https://dl.dropboxusercontent.com/u/30269671/WER-435242-0.sysdata.xml

Any help would be appreciated, thanks

EDIT: Sorry, I'll use the diagnostic tool, missed that

Diagnostic tool: https://dl.dropboxusercontent.com/u/30269671/SF_06-01-2014.zip

 

[koolkat77]

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff8801078a697}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8801078a697

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  6

LAST_CONTROL_TRANSFER:  from fffff8000348b169 to fffff8000348bbc0

STACK_TEXT:  
fffff800`00ba4d28 fffff800`0348b169 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`03489632 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`1078a697 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0517dff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiUpdateCurrentIsrFrameTime+0x8f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f
fffff880`1078a697 ff1563290000    call    qword ptr [dxgmms1!_imp_KeQueryPerformanceCounter (fffff880`1078d000)]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

Followup: MachineOwner
---------

Please follow the quote:

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

4. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

• Piriform - Speccy
• CPUID - HWMonitor

 

[MicroMister]

Thanks, haven't had any more as of now

I'll wait another day then mark this as solved