Random BSODs, Crashes - Windows 7 x64

K

Klepton

Active member
Joined
Feb 11, 2016
Posts
43
Hello. I've been getting several BSOD occurrences lately. Last week, I got three of them in one day. One while PC was idling, and other two while surfing the net. The computer is also frequently becoming unresponsive to the point where nothing works and I have to force shut it off by holding the Power button until it turns off. Most of the times it happens a while after I start the Chrome browser and "Restore" the previous pages. Additionally, I still have a few Windows Updates that fail installation. My original thread started in the Windows Update section of this forum, but I was sent here after I reported the BSOD occurrences.

· OS - Windows 10, 8.1, 8, 7, Vista ? Windows 7 Home Premium SP1
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? Windows 7 Home Premium
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
· Age of system (hardware) 8/10/2010
· Age of OS installation - have you re-installed the OS? No

· CPU Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
· Video Card Intel G45/G43 Express Chipset (Dell)
· MotherBoard - (if NOT a laptop) Not sure. I ran Speccy and under Motherboard section, it states "bad allocation"
· Power Supply - brand & wattage (if laptop, skip this one) Not sure

· System Manufacturer Dell
· Exact model number (if laptop, check label on bottom) Inspiron 560

· Laptop or Desktop? Desktop


*** Note - When running Speccy, it states "bad allocation" under CPU, RAM and Motherboard sections! ***




 

Attachments

Hi. . .

The lone dump listed Zone Alarm as the probable cause.

I suggest that you make sure you have the most recent version installed or better yet - uninstall it.

Uninstallers (removal tools) for common Windows antivirus software—ESET Knowledgebase

It is very likely that Zone Alarm's firewall is preventing the Windows Updates from installing.

I also think that you'll find the system much more "fluid" after the removal of Zone Alarm.

Regards. . .

jcgriff2

Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\022616-30778-01.dmp]
Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600
Debug session time: Fri Feb 26 10:11:18.757 2016 (UTC - 5:00)
System Uptime: 0 days 8:35:05.443
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : NETIO.SYS ( NETIO!StreamOptionalSeparateDisconnectFromData+f )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_NETIO!StreamOptionalSeparateDisconnectFromData+f
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0174c62f fffff880`009d1f28 fffff880`009d1780
BiosVersion = A03    
BiosReleaseDate = 05/05/2010
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 560  
MaxSpeed:     2500
CurrentSpeed: 2493
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
 
Last edited:
Ok, the following is what I've done since my last post:

1) Shortly after my initial post my computer became unresponsive again and I had to force shut it down.
2) After restarting, I re-launched Chrome and restored the pages.
3) I ran "Driver Verifier" following the instructions on Step 6. of the Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista.
4) After I rebooted, I don't know whether Driver Verifier ran and completed or is still running.
5) I updated my system's BIOS from A03 to A06.
6) After checking my thread, I removed Zone Alarm from my system per your suggestion. I did not find a specific uninstaller for Zone Alarm in the Uninstallers (removal tools) for common Windows antivirus software—ESET Knowledgebase
link you provided, so I used Revo Uninsaller to remove any folders, files and registry items left behind after uninstalling.


What do you mean by "The lone dump"? Does that mean that there is only record of one BSOD? I've received many, at least half of which I took a picture of the Info displayed on the screen as follows:

https://www.dropbox.com/s/cribtaithlwnxbn/2016-02-18%2014.20.54.jpg?dl=0
Dropbox - 216-2-21 19.4.5.jpg
Dropbox - 216-2-21 2.51.43.jpg
Dropbox - 216-2-21 21.9.59.jpg
https://www.dropbox.com/s/ybkrimo6y89ac54/2016-02-26 09.11.57.jpg?dl=0

Additionally, what do you make of Speccy reporting "bad allocation" under the CPU, RAM and Motherboard sections?

Should I also Run HDD Diagnostics and Test RAM according to "Step 6. While waiting for a reply - " of the aforementioned posting instructions?
 
Hi. . .

Yes... "lone dump" -- meaning 1. There was only one dump file in the attached zip file.

Are you running an app like CCleaner that deletes dump files?

The BSOD screenshots were revealing. One of them contained a bugcheck 0x101 - a CPU hang. 0x101s often indicate bad CPUs, but not always.

If you have an Intel CPU, run the Intel test - https://www.sysnative.com/forums/ha...stress-testing-intel-cpu-test.html#post145238

If AMD, run Prime95 - https://www.sysnative.com/forums/ha...-stress-testing-intel-cpu-test.html#post28390

You can also run Prime95 on Intel.

The other BSODs in the screenshots all named the Microsoft networking related driver NETIO.sys as the probable cause. This may mean that your networking drivers are involved or that some app (like Zone Alarm) was "phoning home" at the time of the BSOD. My guess is the latter.

However, be sure that both Ethernet + wifi drivers are updated. The only sure way to do that is to look the drivers up in Device Manager, find them in the Driver Reference Table (DRT), check the update site for updated drivers.

DRT - Driver Reference Table

You can see if Driver Verifier is running or not by bringing up an Admin CMD prompt; type/paste verifier /query

If info returns - Driver Verifier is running. If not, you'll see a message like this:
Code: 
2/29/2016, 9:20:08 PM
No drivers are currently verified.

I do not know much about Speccy or why it would report "bad allocation".

Please forget about step #6 for now - concentrate on the CPU test + wifi and Ethernet driver updates. Even if using only wifi, be sure to update Ethernet anyway because even though not in use, the Ethernet driver is loaded into RAM. Vice-versa with Ethernet use and not wifi.

I hope that all of this turns out to be precautionary and that Zone Alarm turns out to be the lone culprit. Zone Alarm could very well have been involved with the 0x101 (CPU hang) BSOD. I have seen these 3rd party Internet Security Suites damage many Windows installations over the years (NOT physical hardware damage). They harness a great deal of power because they jump so many levels (user mode + kernel mode) and have the power to bring very powerful systems like core i7s to a crawl.

If I missed any of your questions, please let me know.

Regards. . .

jcgriff2
 
Apologies for triple posting, but I'm just trying to tie up loose ends.

I Googled Speccy "bad allocation" - Speccy "bad allocation" - Google Search

There are others that have reported this error, but Pirform (Speccy's author) has not satisfactorily answered.

Pirform is also the apparent author of CCleaner. I have found posts asking about the same error (exact wording as well) in CCleaner.

Pirform is also the author of Recuva (data recovery tool). This post from 2007 lists the upgrades/fixes in Recuva v1.08.174 - one of which is a "bad allocation" error message:

Recuva v1.08.174
•Added image preview feature.
•Redesigned find box.
•Fixed sorting by state issue.
•Better handling of the cluster array (bad allocation issue).
Click to expand...
Recuva v1.8.174 - Announcements - Piriform Community Forums

From all of the above, I would have to say that the "bad allocation" error message is some kind of bug in the Speccy software. Exactly what conditions in a system must exist to invoke the message - I do not know.

Your case is the first that I've ever heard of re: Speccy and I would conclude at this time that it is benign.

That's all the information that I was able to find on it.

Regards. . .

John
 
Ah yes, I use CCleaner and I just confirmed that I have "Memory Dumps", "Windows Log Files" and "Windows Error Reporting" checked when it analyzes/cleans.

Hopefully, I don't have a bad CPU. I ran the Prime95 Hardware Stress Testing + Intel CPU Test and it PASSed all tests.

I had actually Googled the NETIO.sys a couple of weeks ago after I first noticed that message in a BSOD. I read that it might deal with the Network Adapter drivers so I updated my Ethernet adapter driver at that time. This PC does not have a Wireless card.
I used the Driver Reference Table you suggested to reference my Ethernet driver and found an even new one (by a couple of months). I've updated my Ethernet driver to the latest one now.

It appears that Driver Verifier is running, since I get a long list of drivers and info when I type verifier /query in an elevated CMD prompt. How do I know when it finishes?

I'm really surprised that ZoneAlarm caused all these problems. I only installed it because I read a review about it being one of the top Free Firewalls for 2016.
 
jcgriff2 said:
p.s. Did you get the Windows Updates installed after the removal of Zone Alarm?
Click to expand...

There were some new updates that were successfully installed the last time I rebooted (after I uninstalled Zone Alarm). However, there are still 3 Important Updates that keep failing installation even now.

jcgriff2 said:
Apologies for triple posting, but I'm just trying to tie up loose ends.

I Googled Speccy "bad allocation" - Speccy "bad allocation" - Google Search

There are others that have reported this error, but Pirform (Speccy's author) has not satisfactorily answered.

Pirform is also the apparent author of CCleaner. I have found posts asking about the same error (exact wording as well) in CCleaner.

Pirform is also the author of Recuva (data recovery tool). This post from 2007 lists the upgrades/fixes in Recuva v1.08.174 - one of which is a "bad allocation" error message:

Recuva v1.08.174
•Added image preview feature.
•Redesigned find box.
•Fixed sorting by state issue.
•Better handling of the cluster array (bad allocation issue).
Click to expand...
Recuva v1.8.174 - Announcements - Piriform Community Forums

From all of the above, I would have to say that the "bad allocation" error message is some kind of bug in the Speccy software. Exactly what conditions in a system must exist to invoke the message - I do not know.

Your case is the first that I've ever heard of re: Speccy and I would conclude at this time that it is benign.

That's all the information that I was able to find on it.

Regards. . .

John
Click to expand...
No apologies needed. It is great that you are very responsive and thorough. In the Windows Update section, the person helping me out with SFC errors took up to 5 days for a response, so I welcome this change.
Thanks for your research on Speccy. Hopefully it is a benign occurrence as you believe.
 
Reboot a few more times and see if those 3 Windows Updates make it in. Sometimes a few reboots are needed.

If no success on installing the Windows Updates, I'll have to send you to the Windows Updates forum here. I know they now have more staff, so you should get a pretty quick turn-around.

It was my pleasure to investigate the Speccy error message. It was rather intriguing as well.

I'm not sure what to tell you to look for at the end of Driver Verifier because it will most likely continue in perpetuity - continuing to check the same drivers over and over.

Just let it run for at least 24 hours minimum. Turn sleep OFF if need be.

Zone Alarm and the other 3rd party Internet Security Suites (like Norton, McAfee, KIS, COMODO, etc...) have caused problems in Windows systems ever since Vista when the user and admin tokens changed. I run ESET NOD32 antivirus + Windows Firewall and have never had a security issue. The Windows Firewall really is a good firewall.

Regards. . .

John

EDIT: glad to hear that the CPU tests passed. My guess is that Zone Alarm may have caused that BSOD as well.
 
Last edited:
Well, I've rebooted 3 times, each time waiting for the system to automatically detect the Windows updates and give me the option to "Install updates then shutdown computer" when clicking on the Start->Shut down button.
Each time I shut down it tried to install the updates before shutting down. When booting back up, the same updates would appear after some time. Checking the update history, I see that the updates failed to get installed during each shut down.
The 4th time I booted up, I didn't wait for the system to automatically detect the updates. Instead, I manually started Windows Update and selected to install the updates without shutting down. Unfortunately, the updates once again failed.

I'm fine with going back to the Windows Update section of the Forum to try to resolve these Windows Update issues, but are we done here as far as the Random BSOD, Freezes, etc. are concerned?

I'll let the Driver Verifier run another day, but I'm assuming I will have to eventually stop it? Also, if I don't get a VERIFIER_ENABLED BSOD occurrence does that mean it did not detect any problems with my current drivers?

I'm currently using Avast Antivirus and am sticking with the Windows Firewall as well going forward.
 
Thanks again for all your help John! I hope not to have to come back here, but if I do I know you'll do your best to solve any further issues...
 
P.S. Did you overlook the following questions:

I'll let the Driver Verifier run another day, but I'm assuming I will have to eventually stop it?
Also, if I don't get a VERIFIER_ENABLED BSOD occurrence does that mean it did not detect any problems with my current drivers?
 
If Driver Verifier has been running for more than 36 hours, you can now stop it.

verifier /reset from an Admin CMD prompt; re-boot your system.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top