BSOD -A Device Driver Attempting to Corrupt the System Windows 7

Page 2 of 2 FirstFirst 12

  1. Posts : 12
    Windows 7 x64
    Thread Starter

    Anyone can help?

    I got another one. IRQL_NOT_LESS_THAN_EQUAL or something
      My Computer

  2. Posts : 12
    Windows 7 x64
    Thread Starter

    Why is nobody helping?
      My Computer

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

    Hi EyeBallPaul.

    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

    Let us know the results.
    BugCheck 50, {ffffffffffffff85, 1, fffff800030d1908, 0}
    Could not read faulting driver name
    Probably caused by : hardware ( dxgkrnl!DxgkWaitForVerticalBlankEvent+53f )
    Followup: MachineOwner
    BugCheck 19, {20, fffff8a00b52a8f0, fffff8a00b52af00, 5610048}
    *** WARNING: Unable to verify timestamp for Unknown_Module_fffff880`01260000
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff880`01260000
    Unknown module 'Unknown_Module_fffff880_01260000' found on stack, using vad to reload module.
    !vad_reload -1 0xfffff88001260000
    Unable to get LeftChild of nt!_MMVAD_SHORT at fffffa8004bebcd0
    Probably caused by : memory_corruption
    Followup: memory_corruption
      My Computer

Page 2 of 2 FirstFirst 12

  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 17:15.
Find Us