I had fairly frequent BSOD when running window 7 and never had a resolution in 7forum. Tested memory and stressed drivers. I switched to windows 10 and everything went well for quite a while. I now have very frequent BSOD and it seems to have started since the last 10 update. Got a message DRIVER_IRQL_NOT_LESS_OR_EQUAL (ndis.sys). Posting zip files from last week or so. Any help greatly appreciated.
Scott
Update your installation to the most recent version 10586.Code:OS Version: 10.0.10240 N/A Build 10240
Is the tool you used from the Windows 7 Help Forums? If so, download the tool from BSOD - Posting Instructions - Windows 10 Forums next time you need to run it. There are changes with Windows 7 and Windows 8/8.1/10 regarding the data that is collected.
Thank you axe0. I have gotten the new dm log collector. Sorry about that, but yes, it was the windows 7 collector. I tried at one point to get the 10586 build, but had trouble with it. Can't remember now what it was, but will try again.
Thanks again.
Scott
After updating to 10586 version I had another error. Attached is the log using the new collector.
Scott
Update your BIOS to F7 and run driver verifier after updating Malwarebytes, the sound drivers and chipset drivers.
GIGABYTE - Moederbord - Socket 1150 - GA-H81M-HD3 (rev. 1.0)
Warning
Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Hi axe0,
FYI - I had trouble with the BIOS like you gave. I was able to download and extract everything, but windows would let me run it. Got it done using GIGABYTE's @BIOS tool.
Also updated Malwarebytes, and the drivers you noted.
Started driver verifier according to tutorial. Had a meltdown with error - Attempted_Write_to_readonly_memory... Log attached.
Thanks for all your help.
Scott
No driver flagged when a crash is caused by driver verifier often results in hardware problems.
Based on the crash type, result of driver verifier and below (write access fault), I'd say your memory is faulty.Code:DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
You could test your memory using MemTest86+ to verify it, although it isn't always correct when it shows no errors, read carefully the instructions if you do.
Code:2: kd> !pte 8000000000900121 VA 8000000000900121 PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000020 PTE at FFFFF68000004800 contains 07B000017A3FE867 contains 0000000000000000 pfn 17a3fe ---DA--UWEV not valid WARNING: noncanonical VA, accesses will fault !
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
Hi axe0,
This makes a lot of sense. I suspected memory when I had problems in windows 7, but extensive testing did not show a problem. I will take the memory back to where I purchased it and make this as solved.
Thanks again!
Scott
Quote
