Sometimes when I play flash games on the web or play tetris the laptop screen would suddenly go black and the bsod would appear. It only happened when I am surfing on the web and using firefox.
I appreciate any help that you can provide.
Welcome to SevenForums
Problematic Software:
Zone Alarm contributes in BSODs. Avira is not very stable on some systems. Please uninstall both using the relevant uninstallers by searching in google. OR, use the free version of Revo Uninstaller (uninstall in Advanced Mode).Code:Start Menu\Programs\Avira Public:Start Menu\Programs\Avira Public Start Menu\Programs\Avira\Avira Desktop Public:Start Menu\Programs\Avira\Avira Desktop Public Start Menu\Programs\Check Point Public:Start Menu\Programs\Check Point Public Start Menu\Programs\Check Point\ZoneAlarm Public:Start Menu\Programs\Check Point\ZoneAlarm Public
Recommended antivirus program for Windows 7 based on stability compared to others:-
- Microsoft Security Essentials - Free Antivirus for Windows
- Malwarebytes - The Free version
- Good and Free system security combination.
Run a full scan with both (separately) once downloaded, installed and updated.
You have only one .dmp file and see the usual causes for it:
After making the above changes to your computer, run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Let us know if the computer is stable or not.
Then test your ram sticks.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Let us know the results and further BSODs if anyThe goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
Following is for information purpose only;
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050033, 406f8, fffff880044085aa} Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessIsrCompletedPacket+12a ) 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: fffff880044085aa Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 9 LAST_CONTROL_TRANSFER: from fffff80002e85569 to fffff80002e85fc0 STACK_TEXT: fffff800`00ba4d28 fffff800`02e85569 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx fffff800`00ba4d30 fffff800`02e83a32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00ba4e70 fffff880`044085aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff880`096eb000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x12a STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidSchiProcessIsrCompletedPacket+12a fffff880`044085aa e8a13a0000 call dxgmms1!VidSchiUpdateContextRunningTimeAtISR (fffff880`0440c050) SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgmms1!VidSchiProcessIsrCompletedPacket+12a FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 FAILURE_BUCKET_ID: X64_0x7f_8_dxgmms1!VidSchiProcessIsrCompletedPacket+12a BUCKET_ID: X64_0x7f_8_dxgmms1!VidSchiProcessIsrCompletedPacket+12a Followup: MachineOwner ---------
Quote