BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys


  1. Posts : 9
    Windows 7 Home Premium 64-bit SP1
       #1

    BSOD ntoskrnl.exe UPDATE4** fail memtest...kinda**


    Hi,
    to make things easier for you,below is the Bug Check String, Driver, and crash address
    • SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0
    • MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0
    • SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0
    • NTFS_FILE_SYSTEM___________Ntfs.sys_______ntoskrnl.exe+75bc0
    • IRQL_NOT_LESS_OR_EQUAL____ntoskrnl.exe____ntoskrnl.exe+75bc0


    (unrelated:how could I make nice table above?)

    I have searched the forum.

    Problem 1: BSOD randomly, usually graphics related. eg, flash games in chrome, graphics related software (Mathematica).

    Problem 2: I use an internet usb 3G device to connect to internet. Every morning the device will not connect to internet and computer will hang on shutting down screen when I restart. I have to manually turn off and back on again. I think this may be a dying capacitor on motherboard that needs 2 boot's to get excited.

    Problem 3: Chrome "aw snap" happens regularly and is usually flash content related, even ad banners seem to cause it from time to time. I have reinstalled chrome, checked plugins etc etc no luck. Internet explorer runs stable,but for example in flash games it seems to momentarily freeze and then catch up with itself again. These are moments where I think chrome would have crashed.

    Things I've done:

    1) SFC scan. All's well.

    2) Memtest. I did 1 pass, it took an hour, everything fine. Will put it on over night tonight.

    3)Checked for latest drivers. Also have latest BIOS. Checked win update.

    4)Ran Intel Burn, everything ok.
    (max stress, over 13Gb RAM, 1 run, 10min, max temp 68...thank you Noctua NH-C12P..this is with quiet adaptor too lol)

    5)Ran malwarebytes, found nothing toxic

    6)Ran SSDlife Free, 98% health SSD seems fine.

    7)Bought a new motherboard, assuming that the current one is going bad. I haven't switched over to it yet and thought I should investigate a little further before I do. ie, bad RAM? CPU? Power Supply? SSD?

    CPU seems fine, RAM passed test but will test further.

    My own "opinion" until today was that there is a fault on motherboard probably with usb hardware.

    Now I realise that it could be the power supply but I have no way to test this bar buy a new one.

    My analysis: 1)bad motherboard or 2)bad PSU

    Either way, not getting away with cheap fix methinks.

    **************UPDATE****************

    I enabled verifier.exe using this:
    Driver Verifier - Enable and Disable

    Windows crashes just before going to desktop. I had to boot last known config to get up and running again.

    IE, I CAN RELIABLY CREATE BSOD USING VERIFIER.EXE WITH GIVEN INSTRUCTIONS

    So I am going to try focusing on drivers loaded at startup by process of elimination. Is there a quick way to find out which one? Below is the Check String, Driver, and crash address for the BSOD's when using verifier.exe

    IRQL_NOT_LESS_OR_EQUAL___________ntoskrnl.exe___________ntoskrnl.exe+75bc0
    DRIVER_IRQL_NOT_LESS_OR_EQUAL___RNDISMPX.SYS_________RNDISMPX.SYS+719a

    **************UPDATE 2****************

    If I choose 3 or more non Microsoft drivers in verifier.exe I get BSOD, different check strings, but always at the same address. Also computer seems more unstable since engaging with verifier.exe.

    I feel I have given a thorough evaluation based on information in this forum and would appreciate feedback from those with more expertise than I.

    **************UPDATE 3 ****************

    Another Memtest gave 61 errors on pass 1. Questions:
    1)any chance poor power supply can cause this?
    2)anyone have experience increasing voltage to make this go away?
    3)would bad RAM explain all my problems?
    4)ok fine.....i'll go through RAM and the slots and find the bad one....sigh....major sigh.....positively tragic sigh.......................


    **************UPDATE 4 ****************

    Started with slot 0 with 1 stick of RAM. Did memtest, but had an idea. I turned on verifier.exe with all 3rd party drivers selected and my theory was to replicate the BSOD I got earlier at startup. Went through each slot, each RAM, combo's of RAM, and then to add insult to injury with all 4 sticks in , exactly same as before, no BSOD. Life is tough....

    So maybe RAM wasn't properly seated all this time, or maybe I need to test the RAM properly. Anyway, I will leave it run memtest tonight all night.
    Last edited by lapetus; 04 Nov 2014 at 18:09.
      My Computer


  2. Posts : 9
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #2

    **************UPDATE 5 ****************




    The sequence of events went as follows.
    RAM test 1 pass was passed. Verifier.exe caused immediate BSOD on windows start when activated. Trying to hunt down drivers revealed any combo of 3 or more drivers gave BSOD at startup. Randomly decided to recheck RAM. Failed memtest after 27 minutes pass 1. Found one RAM stick that passed after one pass slot0. Got fed up of waiting for other slot's. Devised a plan to use verifier to check the RAM by seeing which combo's of RAM sticks gave BSOD on startup. All combo's passed. And now verifier does not give BSOD on any setting. Began to hate life. Cheered myself up with prospect of sleep. Put all 16 Gb RAM in properly and ran mentest for 18 hours, 6 passes. No error. Still no verifier.exe errors when enabled. Wrote this update.


    If RAM failed after 27min one test, and then after swapping around a retest of 18 hours has no error, one would presume the RAM may be ok. Equally, I believe one could say the RAM is suspect. So, if the test is failed it really doesn't tell us anything except there is a problem somewhere. But we know there is a problem since we have BSOD!!! If I hadn't rerun the test I wouldn't question the RAM.

    So the question is: how do I categorically ensure that a stick of RAM is good? Is memtest on RAM with an alternative working computer enough?



    In summary:

    I ran memtest for 18 hours, which was 6 passes. No problems detected. Using verifier.exe with protocols given on this forum I no longer get BSOD.

    Currently my hypothesis is that the RAM was never seated correctly, or given that it takes a bit of force to insert correctly into motherboard, the flexing has at least temporarily defused whatever fault was causing my BSOD. Tenuous I know. But I really have no other explanation other than something somewhere on the motherboard or power is failing, or even the RAM.
      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 22:41.
Find Us