Solved Random BSOD - Windows Update Related - 10/May/2016

[marcosd2]

Hello, everyone.

My Windows 7 Pro is genuine and have been working OK for a long time until today precisely at 20:30h GMT -03:00.

The notebook was idle, I was away for 30 minutes and when I came back it had a message saying: "Windows' been not properly shutted down". Ten minutes later a BSOD (IRQL_NOT_LESS...) occurred. And then random BSOD (DRIVER_IRQL_NOT..., tcpip.sys, ntoskrnl, etc) occurred.

Since I didn't change ANYTHING (hardware or software), I tried to run Windows Update to solve the problem. Then I noticed svchost.exe was with high memory usage and went back to normal when I stopped Windows Update service.

This is what I did to stop (so far, 13 hours) the BSOD:
- Downloaded and installed this KB (https://www.microsoft.com/en-us/download/details.aspx?id=51853);
- services.msc > Windows Update > Disabled, and;
- Control Panel > Windows Update > NEVER check for updates.

The last time i successfully ran Windows Update was 09/Feb/2016.

What do I do? I read that many people are having issues with Windows 7 Updates. I don't want Windows 8 or 10, I like 7 and have NO reason to upgrade.

I attached the DM Log Collector in this message.

Thanks in advance.

 

[axe0]

It looks like you've cleaned up your system and thus removed all relevant data from the BSODs.

Currently the only thing I can suggest is to ensure your network drivers are up to date.

I don't want Windows 8 or 10, I like 7 and have NO reason to upgrade.

I would recommend to stay with Windows 7, Dell doesn't provide drivers for Windows 10, if any problem would occur in Windows 10 you would need to clean reinstall Windows 7 because most problems I see are due to drivers + an incompatible system isn't what anyone wants and downgrading using the provided ways often leads to more problems.

 

[marcosd2]

This is how I apparently solved my issue:

• updated ALL outdated drivers using DriverEasy (I know it's not recommended but it really honours the name - it was very easy to do the task)
• did exactly this: http://www.sevenforums.com/tutorials/91738-windows-update-reset-21.html#post3237652
• after restarting the computer, Windows Update found updates
• I installed only security ones and explicitly HID all those Telemetry Undercovered Lies related.

So far it's OK, let's see how it goes during a few days of normal usage.

Thanks for your time.

 

[axe0]

Driver update programs don't only install outdated programs, but also Windows drivers which can only be updated through Windows Update. Those I've seen using driver update programs had to either reinstall Windows or use a backup/restore point to recover from the changes those programs had made, it is strongly adviced against the use of them.

FYI, most of the drivers you need are provided by the motherboard manufacturer (or all of them with laptop manufacturer), it shouldn't be that hard but you have to do something for it to do it properly.

 

[marcosd2]

Suddenly, after several days of normal usage under the same environmental temperatures, the computer froze/screen got 'messed'/etc clearly indicating that it was something related to the VGA.

Via Safe Mode: I tried to uninstall the video driver using Display Driver Uninstaller and I got a BSOD. After a reset, I finally made it. I installed the video driver manually (downloaded from NVIDIA website) and the problem kept appearing.

THEN, this is what I did to apparently solve the problem as it seems to be a particularity of my notebook/hardware/VGA:

• NVIDIA GeForce GT 540M crash problem - Forums - World of Warcraft

I found the same suggestion everywhere (even on Dell forums) saying that this is the ONLY way to solve the issue.
​

I hope this solve it definitely. I don't like the idea of underclocking (even if it's just a little bit) but what can I do?

This is how I set the software: http://i.imgur.com/nKdPAKX.png and http://i.imgur.com/Gusl4h0.png.
​

• I also had to do this: http://i.imgur.com/Pbpflc1.pnghttps://www.youtube.com/watch?v=Zj6QfkTi1AY

 

[axe0]

Glad to hear you solved it

 

[marcosd2]

To FINALLY solve the issue I did what's explained in THIS POST.

Absolutely not recommended for those under warranty or don't know what they're doing.

 

[axe0]

Good to hear your issue is solved