ntoskrnl.exe+75169 -- Seemingly Random, Frequent BSODs


  1. Posts : 11
    Windows 7 Professional x64
       #1

    ntoskrnl.exe+75169 -- Seemingly Random, Frequent BSODs


    Hi all!

    I decided to upgrade both of my dell optiplex 755 machines with an Intel 530 SSD (240GB) and clean install Windows 7 64-bit. Setup went smoothly. However, after all updates and drivers were installed, I started getting random, frequent BSOD crashes, with nearly all of them pointing to ntoskrnl.exe+75169. I don't think I've ever even encountered a blue screen back when I used my old HDD. I suspected bad RAM at first, but Memtest showed no errors after running for 14 hours (each stick). I know it has something to do with the SSD, but I just can't figure it out Dump info attached!


    Unfortunately, one of my machines (which already experienced many BSODs) is in a different city and I can't access it at the moment. I have just finished the second machine and just got my first BSOD. Ideally, I would like to have several BSODs so I cant establish some kind of pattern, but maybe we can make progress by checking out the first BSOD since most of them will probably be identical anyway. Thank you so much!!


    They are configured basically the same:

    Core 2 Quad 9550
    8GB RAM (4 x 2GB)
    HIS Radeon HD 7750
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    There are no .dmp files present in the ZIP file.

    Do this:
    1. Check if there are .dmp files in C:\Windows\Minidump
    - if "Yes", use 7ZIP and upload them here in your next reply
    - if "No", follow steps 2 to 3 below

    2. Enable .dmp file creation: (Small dump file / minidump is fine)
    Dump Files - Configure Windows to Create on BSOD

    3. Run Driver Verfiier as explained here:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
      My Computer


  3. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #3

    Oops -- just realized I had moved the .dmp file to my desktop before running the dm log collector. I moved it back to the original minidump folder, and now everything should be in the zip file. I will be running the driver verifier for the next 24 hours and post back on here.

    In the meanwhile, can anyone help me out in figuring out the .dmp files? Thanks guys!
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    Upload the new ZIP file that contains the .dmp files.
      My Computer


  5. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #5

    Here you go!
      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 05:49.
Find Us