[DVCnerfherder]

Good morning.

 

I have an older dual-boot Dell laptop running Ubuntu 16.04.2 LTS and Windows 7 64-bit Professional.  I last used the Windows partition on Saturday night without issue, but when booting it this morning (Monday) I consistently get a BSoD appearing after 10 minutes of its booting, regardless of whether or not I actually log in.  Here are a few observations:

 

- Ubuntu is showing no issues at all, so it's not likely hardware related

- Windows 7 is fine in Safe Mode (i.e. no BSoD)

- Windows 7 running normally generates a BSoD after 10 minutes - every time

 

When I was using the computer on Saturday I did not install or upgrade any components or software.  At this point I'm not sure if the problem is something with Windows or if I've picked up a virus.  I am running Avast Free V17.2.2288 with virus definitions 170320-0 released at 02:54 this morning but not installed on my system until 9:39.  I'm not sure this is the problem because I got my first BSoD this morning before the virus definitions were updated.

 

I restored the system from an automatic restore point generated last Wednesday but that has made no difference.

 

At this point I'm not sure whether to post here or in the malware forum but I thought I'd start here because I see no indication that it's a malware infection.

 

Thanks in advance.

 

 

[Advertisements]

Get Process Explorer

 

http://live.sysinter...com/procexp.exe

Save it to your desktop then run it (Vista or Win7+ - right click and Run As Administrator).  

 

View, Select Column, check Verified Signer, OK

Options, Verify Image Signatures

 

 

Click twice on the CPU column header  to sort things by CPU usage with the big hitters at the top.  

 

Wait a full minute then:

 

File, Save As, Save.  Note the file name.   Open the file  on your desktop and copy and paste the text to a reply.

 

 

See if you can get Who Crashed to work:

 

 

http://www.resplendence.com/downloads

Then click on Download free home edition 

 

where it says:

 

WhoCrashed 5.51

Comprehensible crash dump analysis tool

for Windows 10/8.1/8/7/Vista/XP/2012/2008/2003 (x86 and x64)

 

Right click on the downloaded files and Run As Admin.  Once you agree to the terms and Install it then Finish it should open Who Crashed.  Click on Analyze.  Once it finishes scroll down to the bottom and copy the report and paste it into a reply.

 

 

Get the free version of Speccy:

 

http://www.filehippo...download_speccy (Look in the upper right for the Download

Latest Version button  - Do NOT press the large Start Download button on the upper left!)  

Download, Save and Install it.  Tell it you do not need CCLEANER.    Run Speccy.  When it finishes (the little icon in the bottom left will stop moving), 

File, Save as Text File,  (to your desktop) note the name it gives. OK.  Open the file in notepad and delete the line that gives the serial number of your Operating System.  

(It will be near the top,  10-20  lines down.) Save the file.  Attach the file to your next post.  Attaching the log is the best option as it is too big for the forum.  Attaching is a multi step process.

 

First click on More Reply Options

Then scroll down to where you see

Choose File and click on it.  Point it at the file and hit Open.

Now click on Attach this file.

 

 

 

[RKinner]

Get Process Explorer

 

http://live.sysinter...com/procexp.exe

Save it to your desktop then run it (Vista or Win7+ - right click and Run As Administrator).  

 

View, Select Column, check Verified Signer, OK

Options, Verify Image Signatures

 

 

Click twice on the CPU column header  to sort things by CPU usage with the big hitters at the top.  

 

Wait a full minute then:

 

File, Save As, Save.  Note the file name.   Open the file  on your desktop and copy and paste the text to a reply.

 

 

See if you can get Who Crashed to work:

 

 

http://www.resplendence.com/downloads

Then click on Download free home edition 

 

where it says:

 

WhoCrashed 5.51

Comprehensible crash dump analysis tool

for Windows 10/8.1/8/7/Vista/XP/2012/2008/2003 (x86 and x64)

 

Right click on the downloaded files and Run As Admin.  Once you agree to the terms and Install it then Finish it should open Who Crashed.  Click on Analyze.  Once it finishes scroll down to the bottom and copy the report and paste it into a reply.

 

 

Get the free version of Speccy:

 

http://www.filehippo...download_speccy (Look in the upper right for the Download

Latest Version button  - Do NOT press the large Start Download button on the upper left!)  

Download, Save and Install it.  Tell it you do not need CCLEANER.    Run Speccy.  When it finishes (the little icon in the bottom left will stop moving), 

File, Save as Text File,  (to your desktop) note the name it gives. OK.  Open the file in notepad and delete the line that gives the serial number of your Operating System.  

(It will be near the top,  10-20  lines down.) Save the file.  Attach the file to your next post.  Attaching the log is the best option as it is too big for the forum.  Attaching is a multi step process.

 

First click on More Reply Options

Then scroll down to where you see

Choose File and click on it.  Point it at the file and hit Open.

Now click on Attach this file.

 

 

 

[DVCnerfherder]

Although I spent several hours troubleshooting this morning, I may have been a little hasty in my original post.  Just for fun, I disabled the Avast shields on my laptop and my BSoD issue disappeared.  So I started viewing the Avast forums page and it appears that the problem is, in fact, related to the virus definitions that were distributed this morning.  Avast is aware of the problem and will be distributing new definitions as of 5pm CET time today.

 

RKinner, thank you for your lengthy reply but I'm afraid this may have all been for nothing.

 

I will hold off marking the topic resolved until I see the updated virus definitions.

[DVCnerfherder]

Best Answer

Updated virus definitions have resolved the issue.

[Channeal]

Thank you very much for posting your problem and solution, DCVnerfherder. I have had the same problem today and spent ages trying to find out what was going on. Came on here a minute ago to try to get some help and spotted your post My Avast has updated now - and lo and behold the problem is solved!!!!!!

 

Many thanks,

 

Chris.