Windows 10 Anniversary Update – BSOD

Topic

New Reply

Hi All,

Are any of you experiencing numerous BSODs (both Blue and Black) with Windows 10 Anniversay Update?

I’ve had more BSODs with Windows 10 than I ever had with Windows 7:(

Among the errors reported, that I noted down:

[*]IRQL_NOT_LESS_OR_EQUAL
[*]SYSTEM_SERVICE_EXCEPTION
[*]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
[*]and possibly others.

I’ve had these 3 in the last 5 days:(::(

In passing, I getting these issues on a Lenovo Thinkpad W541, with 16GB RAM, a 240GB SSD and 1TB HDD running an Intel i7-4910Q CPU @2.90GHz with Windows 10 Pro 64 bit fully updated (last night).

Any clues as to the possible causes.

Cheers

Trevor

Reply | Quote

Replies

Have you checked*Lenovo for driver updates?

Have you run any hardware tests?

--Joe

Reply | Quote

Hi Joe,

Hardware is fully up to date according to Lenovo Thinkpad System Update Scanner.

What hardware tests do you suggest?

Cheers

Trevor

Reply | Quote

With at least 3 different BSOD types, I’d suggest running memtest86+ from a bootable USB stick, for a full 7+ passes per memory stick individually, keep the sticks paired with their original slots for the first tests.

If one stick fails but the other passes, test the failing slot with the known good stick.

These tests will take a long time, I suggest setting them up to run overnight or during work time. If you see any errors during the test, you can stop and continue testing the other stick, or test the ‘bad’ slot with the known good stick.

Reply | Quote

Thanks for the suggestion Satrow.

I ran MemTest86+ over both memory sticks (16GB RAM) many times (lost count:confused:) and no errors found – Passes all round:)

So, still no clue as to the cause of my BSODs, which incidentally do not appear to be related to what I doing or running at nay particular time.

Cheers

Trevor

Reply | Quote

Try this procedure to gather more info, Trevor, attach the zip back here and we can check through that, there may be further clues as to the source(s).

Reply | Quote

Try this procedure to gather more info, Trevor, attach the zip back here and we can check through that, there may be further clues as to the source(s).

Hi Satrow,

Thanks for your offered assistance. I’m attaching the following files:

[INDENT]

[*]SysnativeFileCollectionApp.zip
[*]20161219 PerfMon Report Thinkpad W541 – TRB.zip
[*]20161219 Thinkpad W541 – TRB – System Information Report.zip
[*]20161219 Response to Questions.TXT

[/INDENT]

I hope you can find some clues as to the cause of my BSODs.

Cheers

Trevor

Reply | Quote

It’s possible that the AU has installed one of its own drivers that doesn’t sit well with your system.

If you can boot up into Safe Mode and you don’t get any BSODs in that mode, then you can look at the drivers that aren’t loaded in that mode.

Go into Device Manager/View/Show hidden devices – expand Display and then Sound, right click on each and select Properties then click on Driver to check the date of the driver.

If it looks like they are recent then you could try a Roll back, but to physically check if you have a choice of drivers for each device, then right click on the device – select Update Driver Software – Browse your computer – Let me pick…

If it lists all drivers then scroll down to the applicable but if it takes you to those for that device and if there’s an earlier dated driver, click on that and then on Next to install.

If you have say a Realtek audio adapter, Windows can change that to its own MS HD and while Windows doesn’t like it by issuing you with a warning, you can opt to install the Realtek one and then you will be able to use the Realtek HD Audio Manager to set up your audio.

I found that the AU had updated my Realtek wireless adapter and while it worked, the graph that it produced in inSSIDer3 was like broken teeth on a saw – so back that went to an earlier Win 7 one.

Reply | Quote

Thanks, Trevor, you did fine. The BSOD Collection App. collected the info. that was there but it looks like CCleaner is set to auto-remove most of the useful stuff

Which leaves me with very little to work with, no dumps to analyse, almost no Windows Error Reporting logs,… you have a number of Programs and several running 3rd party drivers that I’m unfamiliar with and the only possible BSOD implicated driver I noticed, wasn’t loaded during the collection.

Let’s try to get some crash dumps recorded without CCleaner removing the evidence – easiest way will be to uninstall CCleaner during troubleshooting, then use the computer as normal until you have a crash or two happen. If you can fiddle with the crash dump settings so that you collect Minidumps and don’t overwrite, that will be a start.

One thing that did leap out of the Event logs was a huge number of errors from MBam’s Chameleon, which I think is the rootkit driver – that needs to be looked into, the MBam forums are the best place for that, they have their own collection routine to run but you can add the EvtxSysDump.txt from the zip file to those if you want.

They also have a BSOD section, usasma will likely deal with you if you create a topic there once you have a minidump or more, he’s much more experienced than I and is likely to have some experience with the software/drivers that I don’t. There would be very few occasions, if any, when I’d be tempted to back my analysis against John’s, he’s good. He can also cross reference/work with the main MBam team, should the issue actually involve their software. Link each topic to the other to make it easier for them.

Link back here, if you would, I’ll keep a lookout there too.

Reply | Quote

That jakst.va_sys is a Sound Card Emulator – is it listed in Device Manager ?

If it is then right click on it and see if it has a Disable option, but you haven’t said if you get the same problems in Safe Mode with Networking where this driver wouldn’t be loaded.

If it doesn’t have a Disable option then create a restore point and use the Uninstall option and then see if you get the same problems.

CCleaner has a box you can uncheck for Memory Dumps under the Windows tab.

Reply | Quote

Thanks to Sudo15 and Satrow for their suggestions.

Since my last post on 19 December I haven’t suffered a BSOD, so it seems that whatever I’ve done at your suggestion (which includes a BIOS update from Lenovo), or MS has with an uncontrolled and unidentified update, has resolved my issue – I hope forever. Looks like I’ll just have to wait and see. If the problem returns I’ll return to this thread with details.

Thanks again,

Cheers

Trevor

Reply | Quote