Solved BSOD Mult. Times per Day 'netio.sys' and Driver IRQ Noted

[pwscott]

Hi, thanks for looking! I have a well-maintained Win7 machine. Am seeing multiple BSODs and then reboots per day. Happens when machine is idle or occasionally in use. Noted in one of the BSOD screens that it mentioned Driver IRQ and netio.sys I think.

Recent changes include when Norton 360 was expiring I uninstalled it and tried FortiClient from Fortinet. I got too many false positives so I reinstalled Norton 360 and then couldn't uninstall FortiClient- had to use Microsoft repair tool to uninstall it.

Also recently updated Nvidia driver with clean install.

Not sure either is related but giving you all the background I can.

THANKS!! Hope to get great help and follow your suggestions closely.

Phil

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[pwscott]

Thank you. I have merged that Create a Small memory dump (Minidump) File on BSOD and will reboot.

Update to follow.

 

[pwscott]

Just had first crash since last post. Here is DM Log Collector file. Working in attaching Mini Dump (which was captured).

 

[pwscott]

Unable Upload Mini Dump file "070815-66940-01.dmp" ??

When I try and upload the Minidump file from c:/windows/minidump I get:

Upload Errors
070815-66940-01.dmp:
Invalid File

File is 348KB.

How do I work around that? I could put it on Google Drive e.g.??

 

[Arc]

Just do it: :ar: Blue Screen of Death (BSOD) Posting Instructions

 

[pwscott]

OK...gather I needed to ZIP the file...here is the Minidump...prior post contained the DM Log Collector file as a ZIP.

 

[Arc]

The Crash dump blames SoundTap.

BugCheck 1000007E, {ffffffffc0000005, fffff88005c8c1e0, fffff88010725748, fffff88010724fa0}

[COLOR=Red]Probably caused by : stdriver64.sys[/COLOR] ( stdriver64+131e0 )

Followup: MachineOwner
---------

That is ....

stdriver    [COLOR=Red]Sound tap driver[/COLOR] Upper Class Filter Driver v2.0.0.0   [COLOR=Red] c:\windows\system32\drivers\stdriver64.sys [/COLOR]   Kernel Driver    Yes    Manual    Running    OK    Ignore    No    Yes

Indicating to some NCH Software.

• Driver Reference Table - stdriver64.sys

And, the driver is old.

    Image name: stdriver64.sys
[COLOR=Red]    Timestamp:        Fri Mar 18 05:47:45 2011[/COLOR] (4D82A4A9)

Either update to that NCH Software product or uninstall it.

Another very serious thing .... you are running that poor computer with 29 startup items. That is an extreme example of bad computing, and you are calling various issues and instability by doing it. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Report us for any further BSOD after doing these.

 

[pwscott]

Thank you for the detailed reply and advice. I have upgraded from the older NCH Application, Debut V 1.64 to Debut V 2.xx
I also used CCleaner to turn off almost all of the startup items you pointed out. I'm not sure I'm ready to mark this solved yet, but I think it probably will be resolved by this.

Thanks again! Will check back in here.

 

[pwscott]

Further Help Needed- Older Driver STDRIVER64.SYS remains

Hi. So two more BSODs here. Let me recount what I've done...I think I need help on how to get rid of this older driver and may be a suggestion on software instead of NCH Debut for capturing video on screen such as webcams etc.

So I looked at the Debut SW and found I was running, as 'Arc' said, a pretty old version of this video capture SW from NCH called Debut. I had V 1.64 I think, and they offered paid upgrades to their latest at 2.12 I believe...So I looked for NCH or Debut in the the uninstall area under Control Panel > Progs and Features, but neither showed up there...So I looked in the Start Menu under NCH for an uninstaller and there also was none.

So I went ahead and bought the upgrade and ran its installer...my hope/expectation was it would load a newerr version of this driver.....it upgraded Debut to latest and I confirmed that and it ran fine....but apparently the old driver is still in the location where it was...I did try running CCleaner and scanning the registry and fixing all but that had no bearing it seems.

I guess <?> that means either NCH still use that old driver that is causing me crashes in their latest,....or I need a better way to get rid of the old driver. I really like the Debut SW and have used it for years to record webcasts and online discussions and webcams etc with audio into MP4 files....I kinda hate to give it up...may be there is an awesome replacement for it??

Anyway...I've looked in c:\windows\system32\drivers\ and that same driver remains there with the same 2013 file date...

STDRIVER64.SYS 8/19/2013 102KB

(BTW there is no new minidump file in c:\windows\minidump after these latest two BSODs or I would have attached it.)

May be there is an uninstall tool I need to run? I very much appreciate your good help and suggestions with getting away from this crash-causing driver and into another solution for recording from screen!

Thank you.

 

[Arc]

Hi. So two more BSODs here.

Whenever you report a BSOD, do it alongith the report following the Blue Screen of Death (BSOD) Posting Instructions. We need to see the revised situation.

 

[pwscott]

Here is the DM Log Collector ZIP file...Does the fact that there is no minidump file indicate that I need to redo the process you outlined here also- or is this ZIP what you need?? :

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.​

 

[Arc]

No BSOD was there after 7/9/2015 10:47 AM.

7/9/2015 10:47 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070915-56082-01.dmp
C:\Users\Phil\AppData\Local\Temp\WER-108373-0.sysdata.xml
C:\Users\Phil\AppData\Local\Temp\WERE3C9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Phil\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_085d1a05

Analysis symbol:
Rechecking for solution: 0
Report Id: 070915-56082-01
Report Status: 4

The data also says that the problem driver is not updated.

[COLOR=Red]3/17/2011[/COLOR] 8:17:45 PM   C:\Windows\system32\DRIVERS\[COLOR=Red]stdriver64.sys[/COLOR]

If there is no feasible update, uninstall your NCH software. See how it goes.

EDIT: Well, ** You uninstall CCleaner till your issue is solved. It is cleaning the dumps.

 

[pwscott]

Thanks for your reply- responses/comments below inline:

"No BSOD was there after 7/9/2015 10:47 AM."

Two BSODs happened, one last night 7/8 and the other very early this AM on EST. Neither of them was apparently logged. Nonetheless, they happened. I was sitting right at the screen and saw it go BSOD. INDENT]


"...The data also says that the problem driver is not updated.
Code:
3/17/2011 8:17:45 PM C:\Windows\system32\DRIVERS\stdriver64.sys..."

Yes, that's right. Hence the title of my post 2 hours ago that was titled 'Further Help Needed- Older Driver STDRIVER64.SYS remains' I did uninstall all NCH SW, and of course rebooted, scanned the reg as I said w/CCleaner, but that driver remains apparently. Would like help getting rid of it please. May be there's a super-uninstaller program to try??


"If there is no feasible update, uninstall your NCH software. See how it goes."

As I said, I bought the NCH update to the latest version, installed it, it didn't update the STDRIVER64.SYS driver file, and I got two subsequent BSODs after trying the upgrade. So, yes, I'd say it's not feasible....so I uninstalled it as best I could...did so from Control Panel > Progs and Features....but it's still an issue.

Thanks for what I can do next to get rid of this.​

 

[pwscott]

I'm still hoping for a little help resolving this please. I continue to have the occasional BSOD crash siting the STDRIVER64.SYS left behind by the NCH Debut screen cap software. Can someone please tell me how I should get rid of the remnants of that program...do I need some super-un-installer program? Can I just delete or rename that driver directly (that seems like a bad diea to me).

Thanks for any follow up that will help me put this to bed.

 

[Layback Bear]

Just a few recommendation.

***Before completing this let Arc respond to my post to make sure my recommendation will not cause him problems.***

1. Complete Arc post #8 using msconfig. not a another program.

2. Don't use any cleaners of any kind until your problem is solved or Arc instructs you to.

3. What ever anti virus programs you have used with this computer verify they are gone by using their online removal tool.

4. At least for now install MSE.

Microsoft Security Essentials - Microsoft Windows

 

[pwscott]

Completed Arc's Post #8.....all progs disabled in startup by msconfig.

Norton 360 still starts and reports all OK, updated and protected.

 

[Arc]

I thank you so much, Jack.

I cannot check the dumps anymore, there are some mishaps there, but as pwscott is saying that the STDRIVER64.SYS is still involving in the BSODs, I would suggest him to uninstall the NCH software that he has installed.

Please be aware that it is a suggestion based on your statement only, not based on my analysis.

 

[pwscott]

Getting Rid of STDRIVER64.SYS and related BSODs

Thank you but please know I HAVE UNINSTALLED the NCH SW. That STDRIVER64.SYS file remains and when I get a BSOD the white text on the BS notes casued by and names that driver. After trying NCH's newer update, I ran their uninstaller, but it left that driver file still on my system apparently.

I am looking for a way to get rid of the remnants of the NCH Software please. Do I need a program like RevoUninstaller Pro??

Or may be Advanced Uninstaller Pro??

I'm not sure why the crash dumps aren't viewable any more? Is there anything I should be doing differently?

Many thanks Arc and Jack for your patience with me and with this issue.

 

[pwscott]

Also found this searching for solutions:

How do I remove Debut Video Capture Software?

Interesting mostly because it seems to show a lit of the drivers etc that the NCH SW installs.