BSOD While Running Flash or Games


  1. Posts : 5
    Win7 Home Premium x64
       #1

    BSOD While Running Flash or Games


    Hi I've been having this problem for some time now. It was fixed at one point but it came back and I have no idea what is the cause. I have done a full reinstall of all of my system.

    Is Windows 7 . . .
    - x64
    - upgrade from Vista x64
    - retail upgrade version

    - June 2009
    - format complete reinstall
      My Computer


  2. Posts : 5
    Win7 Home Premium x64
    Thread Starter
       #2

    I updated my chipset drivers and I received a different error related to MOM.exe. I'm not really sure how to run hardware tests on video cards which I would like to run even though I still believe it to be a software issue.
      My Computer


  3. Posts : 5,705
    Win7 x64 + x86
       #3

    Are you using a PS2 mouse? If so, please uninstall it in Device Manager and then reboot to see if it's detected properly. If you're not using a PS2 mouse, then disregard this.

    Please check Windows Updates to ensure that you have all available updates.

    OLDER DRIVERS PRESENT IN THE DUMP FILES
    - Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system.
    - DO NOT use Windows Update or the Update Drivers function of Device Manager.
    - Windows Update exceptions may be noted below for Windows drivers:
    Code:
    
    iaStorV.sys                      Wed Apr 08 12:57:17 2009 (49DCD76D)
    MpFilter.sys                     Tue Sep 14 20:19:28 2010 (4C901110)
    ElbyCDIO.sys                     Thu Dec 17 17:25:16 2009 (4B2AAFCC)
    e1y60x64.sys                     Mon Aug 18 17:45:05 2008 (48A9ED61)
    VClone.sys                       Sun Aug 09 17:25:45 2009 (4A7F3ED9)
    AtihdW76.sys                     Wed Nov 17 07:02:04 2010 (4CE3C43C)
    MpNWMon.sys                      Tue Sep 14 20:19:30 2010 (4C901112)
    NisDrvWFP.sys                    Tue Sep 14 20:20:25 2010 (4C901149)
    atikmpag.sys                     Thu May 27 12:25:36 2010 (4BFE9D00)
    AtiHdmi.sys                      Thu May 06 05:20:39 2010 (4BE289E7)
    atikmdag.sys                     Thu May 27 12:47:58 2010 (4BFEA23E)
    
    http://www.carrona.org/dvrref.html#iaStorV.sys
    http://www.carrona.org/dvrref.html#MpFilter.sys
    http://www.carrona.org/dvrref.html#ElbyCDIO.sys
    http://www.carrona.org/dvrref.html#e1y60x64.sys
    http://www.carrona.org/dvrref.html#VClone.sys
    http://www.carrona.org/dvrref.html#AtihdW76.sys
    http://www.carrona.org/dvrref.html#MpNWMon.sys
    http://www.carrona.org/dvrref.html#NisDrvWFP.sys
    http://www.carrona.org/dvrref.html#atikmpag.sys
    http://www.carrona.org/dvrref.html#AtiHdmi.sys
    http://www.carrona.org/dvrref.html#atikmdag.sys

    Here's the full gamut of hardware tests:
    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)
    Then, if the above tests pass, I'd try these free stress tests:
    FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    - Click "Quit" to exit
    Prime95 download site: Free Software - GIMPS
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    This won't necessarily crash the system - but check the output in the test window for errors.
    The Test selection box and the stress.txt file describes what components that the program stresses.
    More details on the use of this test: Torture test your CPU with Prime95
    Two other video stress tests (may be more stressful than FurMark):
    Video Memory stress Test - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / VMT
    Artifact Locator - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / Artifact Locator
    Sorry, but I don't read the language that this website is made in.
    If the hardware tests don't find anything, then try running Driver Verifier according to these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sat Feb 19 21:05:33.974 2011 (UTC - 5:00)
    System Uptime: 0 days 0:12:47.003
    Probably caused by : win32k.sys ( win32k!xxxGetInputEvent+d0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  MOM.exe
    FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxGetInputEvent+d0
    Bugcheck code 00000050
    Arguments fffffa80`ffb0e934 00000000`00000001 fffff800`02ad4980 00000000`00000005
    SystemManufacturer = Gateway
    SystemProductName = DX4820
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sat Feb 19 17:47:44.405 2011 (UTC - 5:00)
    System Uptime: 0 days 0:06:11.434
    Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  SearchProtocol
    FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpAllocateKeyControlBlock+72
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`02db4606 fffff880`06b5ba70 00000000`00000000
    SystemManufacturer = Gateway
    SystemProductName = DX4820
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sat Feb 19 17:17:54.860 2011 (UTC - 5:00)
    System Uptime: 0 days 1:38:26.889
    Probably caused by : win32k.sys ( win32k!SetWakeBit+5e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_0x50_win32k!SetWakeBit+5e
    Bugcheck code 00000050
    Arguments fffff900`0181eba6 00000000`00000001 fffff960`001bb4e2 00000000`00000002
    SystemManufacturer = Gateway
    SystemProductName = DX4820
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Fri Feb 11 21:25:44.562 2011 (UTC - 5:00)
    System Uptime: 0 days 3:07:43.216
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
    BUGCHECK_STR:  0x1a_41284
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
    Bugcheck code 0000001A
    Arguments 00000000`00041284 00000000`0dccd001 00000000`00003f61 fffff700`01080000
    SystemManufacturer = Gateway
    SystemProductName = DX4820
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb  5 13:29:11.134 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:15.788
    BugCheck D1, {ffffba8067f93256, 2, 1, fffff80000888dda}
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_nt!KiPageFault+260
    Bugcheck code 000000D1
    Arguments ffffba80`67f93256 00000000`00000002 00000000`00000001 fffff800`00888dda
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
      
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

ฉ Designer Media Ltd
All times are GMT -5. The time now is 20:41.
Find Us