Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Getting BSODs more frequently


  • Please log in to reply
9 replies to this topic

#1 ddibowski

ddibowski

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:40 PM

Posted 02 March 2017 - 02:46 PM

I am running Windows 7 Home Premium 64 bit on a Dell Inspiron 530 desktop.  The original OS was Vista.  I purchased a full retail version Windows 7.  The exact time of installation I can't find but it was spring or summer of 2016.  I have had the PC for about 9.5 years. 
 
The CPU is Intel® Core™2 CPU 6320 @ 1.86GHz.  
 
The mother board is 
Manufacturer Dell Inc.
Product 0RY007
Chipset Intel G31/G33/G35/P31/P35
Southbridge Intel 82801IR (ICH9R)
 
I can't find the power supply info.  Do you want me to open it up?
 
I leave my PC running most nights.  It used to be occasionally I would wake it up in the morning and could tell the PC had rebooted over night.  Occasionally I would have a message displayed showing problem details.  I assumed it crashed overnight.  
 
It seems to be happening more frequently now.  I know with the PC being 9 years old I am on borrowed time.  But I was wondering if you could find some other reason for these crashes.  
 
My files were too big to attach.  Here are the links
 
 
 
Thanks for your help.
 


BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:09:40 PM

Posted 02 March 2017 - 03:10 PM

Hi!

Many of your dumps blamed your Netgear/Broadcom drivers:

*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
Probably caused by : scmndisp.sys ( scmndisp+16d1 )
*** WARNING: Unable to verify timestamp for bcmwlhigh664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwlhigh664.sys

Unfortunately, these wireless USB devices do not function very well and often cause BSODs, especially when the drivers are old:

0: kd> lmvm scmndisp
start             end                 module name
fffff880`014d5000 fffff880`014df000   scmndisp   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\scmndisp.sys
    Image name: scmndisp.sys
    Timestamp:        Wed Jan 17 02:48:03 2007 (45ADD4B3)
    CheckSum:         00008B81
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm bcmwlhigh664
start             end                 module name
fffff880`09efd000 fffff880`09fcd000   bcmwlhigh664 T (no symbols)           
    Loaded symbol image file: bcmwlhigh664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwlhigh664.sys
    Image name: bcmwlhigh664.sys
    Timestamp:        Thu Nov 05 19:27:07 2009 (4AF36D5B)
    CheckSum:         000D82D4
    ImageSize:        000D0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

However, in the "raw stack trace", we see an avast! driver:

fffff880`009ddea8  fffff880`04172d47Unable to load image \SystemRoot\system32\drivers\aswbidsdrivera.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswbidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for aswbidsdrivera.sys
 aswbidsdrivera+0x21d47

There's a high chance that avast! is conflicting with your networking drivers. With that being said, please uninstall avast!, run their cleaning tool, and replace your antivirus with Microsoft Security Essentials. Next, is it possible to physically remove the USB networking device from the system? If not, reinstall the drivers.


Edited by bwv848, 02 March 2017 - 04:13 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 ddibowski

ddibowski
  • Topic Starter

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:40 PM

Posted 02 March 2017 - 03:54 PM

Thanks for your quick response.

 

Just so I am clear I should permanently switch to MS Security Essentials instead of Avast, not just for debugging.  

 

And when you say "Next, is it possible to physically remove the USB networking device from the system?" - do you mean permanently and use a Ethernet cord instead.  That would be no - so I should find updated drivers for network device?



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:09:40 PM

Posted 02 March 2017 - 04:07 PM

Sorry for not making myself clear. For now, all I would do is remove avast! and replace it with Microsoft Security Essentials.THEN, if issues persist reinstall the USB networking drivers.


Edited by bwv848, 02 March 2017 - 04:08 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 ddibowski

ddibowski
  • Topic Starter

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:40 PM

Posted 11 March 2017 - 09:54 PM

I uninstalled Avast and installed MS Security Essentials on the 3rd.  My system crashed once on Wed, twice on Friday and once this morning.  I decided to install the Netgear driver.  It has crashed three times since.  

 

I let Pandora play while I am working on my PC and have noticed the music dragging occasionally.  It did this before I started this case but not as much or as noticeable as it is now.  

 

I thought it was a good idea to install the drivers.  When I moved from Vista to 7 I did not think about the drivers for Netgear wireless device.  So the drivers I had were the original when I had to switched to a wireless setup several years ago.  The driver now is 5.100.148.5.  

 

Can take another look to see what might causing these crashes?  Do I need to send you what I sent when I started the case?

 

Thanks



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:09:40 PM

Posted 11 March 2017 - 10:42 PM

I will need to have a look at the latest memory dumps. Ergo, please run the Sysnative File Collection App again. Sorry if I don't get back to you tomorrow as I have a lot of personal things going on and don't have much time this weekend.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 ddibowski

ddibowski
  • Topic Starter

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:40 PM

Posted 12 March 2017 - 10:01 AM

Here are links to a new Sysnative and another perfmon in case you need it.

 

https://www.dropbox.com/s/p7njealf7ucbcb5/SysnativeFileCollectionApp_20170312.zip?dl=0

 

https://www.dropbox.com/s/6re0jk6q4s79w9u/perfmon_20170312.zip?dl=0

 

I appreciate your time.

Thanks



#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:09:40 PM

Posted 12 March 2017 - 08:59 PM

Greetings,

ALL the latest dumps are STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION bugchecks:

0: kd> .bugcheck
Bugcheck code 000000C4
Arguments 00000000`000000e0 00000000`00000000 00000000`00000001 00000000`00000000
*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
1: kd> lmvm scmndisp
start             end                 module name
fffff880`09d69000 fffff880`09d73000   scmndisp T (no symbols)           
    Loaded symbol image file: scmndisp.sys
    Image path: \SystemRoot\system32\DRIVERS\scmndisp.sys
    Image name: scmndisp.sys
    Timestamp:        Wed Jan 17 02:48:03 2007 (45ADD4B3)
    CheckSum:         00008B81
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

that blame your USB networking device driver, which I presume you've updated (even though it's ten-years-old). Note that the driver is probably not even compatible with Windows 7 — Windows 7 was released in 2009!

Anyway, can you stop running Driver Verifier for now? We don't need it any more, and it's causing "unnecessary" BSODs.


Edited by bwv848, 12 March 2017 - 09:00 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#9 ddibowski

ddibowski
  • Topic Starter

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:40 PM

Posted 13 March 2017 - 11:03 AM

Just to be clear when I started this case I did have an old driver for the network adapter.  But Saturday I installed a driver that I think is compatible with Win 7.  Here is part of the release notes that came with it.  

 

WNA3100 Software Version 2.2.0.4 (Supports Win8/8.1)

Software Included 
 Genie : WNA3100_SW_V2.2.0.4_Setup_Genie.zip 
Standalone : WNA3100_SW_V2.2.0.2_Setup_STALONE.zip 

Versions Included
Software release version: 2.2.0.2 
Win 8/8.1 32/64 bits driver version: 5.100.148.5
Win 10 32/64 bits driver version: 5.100.148.5
Win 7 32/64 bits driver version: 5.100.148.5
Win Vista 32/64 driver version: 5.100.148.5
Win XP/XP x64 driver version: 5.60.180.11

 

Even though the bold heading indicates Win 8, the website indicated this choice was the one to use for Win 10 and I could see Win 7 entry listed in the release notes.  There was an dowload on the website for Win 8 with the same bold heading in the release notes.  I suspect they just did not update the heading,  You can see there is a Win 10 driver in here.  

 

All this is to say I think I do have a driver that is compatible from Win 7.  In Device Manager it shows the driver is 5.100.148.5 with the date 2/10/2015.  

 

I had to google Driver Verifier since I was not familiar with it.  Once I got into it I realized several weeks ago I got into it accidentally when I was doing something else (and I don't remember what I was doing).  Somehow I must have turned it on.  I have turned Driver Verifier off now.  I can tell Pandora is playing much more smoothly now.  

 

I am feeling pretty good about this.  If you don't have any other suggestions, what I would like to do is let this run for a few days to see if I have any more crashes.  I'll let you know either way.

 

Thanks for your help

 

Note:Lost the boldness for "(Supports Win8/8.1)" in the heading of the releaase notes when I posted my reply.


Edited by ddibowski, 13 March 2017 - 11:06 AM.


#10 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:09:40 PM

Posted 13 March 2017 - 11:20 AM

You're welcome.

For some reason the DriverQueryV.txt file from the Sysnative Report says that scmndisp.sys dates back from 2007...

General NDIS Protocol  General NDIS Protocol  Kernel        Boot       Running    OK         TRUE        FALSE        4,096      12,288     0      1/17/2007 2:48:03 AM   C:\Windows\system32\DRIVERS\scmndisp.sys         4,096
 
The info is from Sunday, so I'm not sure what is happening here, BUT since your system is running fine now, we shall leave it as it is.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users