0x00000050 and BSOD SYSTEM_SERVICE_EXCEPTION BSODs (and occassional di


  1. tch
    Posts : 2
    Windows 7 Ultimate x64
       #1

    0x00000050 and BSOD SYSTEM_SERVICE_EXCEPTION BSODs (and occassional di


    I keep getting a 0x00000050 as well as SYSTEM_SERVICE_EXCEPTION errors on my sister's PC from time to time (can't really pinpoint doing anything at the time of crashes). And if it doesn't crash, occassionally the graphics driver will crash with the following message but Windows 7 will keep runing after displaying this error in the taskbar:
    "Display driver intel graphics accelerator drivers for windows 8 stopped working"

    I'm a bit surprised by this error, even though I am actually running Windows 7 Ultimate x64 SP1, not Windows 8.

    I stupidly installed some drivers for an MSI board I mistook for this (it had been BSODing quite regularly before I made that silly mistake) and have since uninstalled all those (I think), and largely up-to-date with the appropriate Asus B75M-A drivers but the crashes keep happening.

    Is the display driver causing these issues? I have done a memory test and that has come back fine with no errors.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    If all are free from errors, uninstall LogMeIn.

    Let us know the results.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffffffffffffe, 0, fffff80002c6932c, 0}
    
    
    Could not read faulting driver name
    Probably caused by : hardware ( nt!NtFreeVirtualMemory+57c )
    
    Followup: MachineOwner
    -----------------------------------------------------------------------
    BugCheck 1000007E, {ffffffffc0000005, fffff80002c8ccfb, fffff880057f7428, fffff880057f6c80}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiWaitForSchedulerEvents+1bc )
    
    Followup: MachineOwner
    ---------------------------------------------------------------------------
    BugCheck 3B, {c0000005, fffff80002fe7ece, fffff8800abf9ff0, 0}
    
    Probably caused by : memory_corruption ( nt!MiUnmapViewOfSection+12e )
    
    Followup: MachineOwner
    ---------------------------------------------------------------------------
    BugCheck 50, {fffff8004b9228b1, 8, fffff8004b9228b1, 5}
    
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43801 )
    
    Followup: MachineOwner
    ------------------------------------------------------------------------
    BugCheck 3B, {c0000005, fffff80002caff07, fffff880050baad0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!SwapSplayLinks+77 )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. tch
    Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Hi,
    Memtest showed up some bad RAM with both DIMMs in (only have 2 x 4gb DIMMs).

    The system doesn't crash after taking the bad DIMM out, but the good DIMM does produce *one* error in Prime95 doing the "Blend" test with it being the only DIMM in the first slot. After 2 hours, it produced a "FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file." error. Can that be ignored? It's not a gaming system at all. I will get the owners of the PC to test it out over a few days to confirm, but it was crashing daily with both DIMMs in.

    The bad DIMM generated errors right away when ran by itself in the same, first slot so I'm pretty sure that's the problem.

    The Fumark test had no issues (ran it at a lower resolution to get higher FPS).
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    As you can identify the faulty DIMM, dont use it.

    Also, Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
      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 00:29.
Find Us