Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD when using VOIP software


  • Please log in to reply

#1
mo713

mo713

    Member

  • Member
  • PipPip
  • 77 posts

I'm using a win xp netbook (don't laugh). I use an Obi100 for most of my voip calls, but for changing numbers, settings, parameters and testing, I was using NCH Express Talk softphone. It worked beautifully, but the trial expired and I don't know how to reset it. I thought it didn't expire for non-commercial use...

So, I downloaded a few other softphones. The one that seemed to meet my needs the best was ZOIPER. I made a test call with localphone just fine. Then, I put in my callcentric credentials to a second account, and every time I try to dial out, I get a pretty instant BSOD. They are all different, but they always refer to an audio related system file. But ONLY on the Callcentric calls! (update: I got it to do the same thing on localphone, but not every time)

This never happened in NCH Express Talk. Also, I remember having a voice convo on Yahoo messenger a couple months ago, and after about 30 mins of successful talking, I got the same BSOD. But at least it worked for awhile.

 

Other helpful data:

 

I have a near-identical 2nd netbook which was tested with the same scenario and didn't crash.

 

The errors have been Driver IRQL net less or equal, driver corrupted expool, driver corrupted mmpool, kernel mode exception not handled.

 

The files it crashed on have included wdmaud.sys, sysaudio.sys avgtdix.sys, portcls.sys, and ntfs.sys (this one scares me!)

 

While all of the messages above are different, the crash ALWAYS has been related to running some type of audio talk software. This latest thing with zoiper can be made to happen every single time.

 

Where do I start?

 

 

If there is a better place to post this (or even a different site) please let me know.


  • 0

Advertisements


#2
Captain Lasky

Captain Lasky

    Member

  • Member
  • PipPip
  • 26 posts

 Hi mo713!  :D

 

I really can't tell if the VOIP Software is causing the BSOD but you must

 aid this problem so that you can use your computer proficiently  :yes:

 

 I hope this helps  :spoton:

http://pcsupport.abo.../stoperrors.htm


  • 1

#3
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

Thank you for the advice.

 

I'm still looking for specific troubleshooting walkthrus typical to other threads posted on here most of the time. I've had much success before with other problems where a member will offer detailed steps to find and solve the problem.

 

I will take a look at the link but would still like an intense procedure from one of the many experts on here.

 

I know that it can take a few days, so I am still hopeful and waiting :)


  • 0

#4
Captain Lasky

Captain Lasky

    Member

  • Member
  • PipPip
  • 26 posts

 Your welcome  :D

 

I hope you find the right solution for your problem :)


  • 0

#5
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

Anyone else able to dive into this? Please?


  • 0

#6
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,000 posts

Hello mo713

 

Download then run Speccy and post the resultant url for us please, details here

 

Next retrieve any dump files that you have from the time that the issue first started > c:\windows\minidump attach them to your next reply please.

 

I noted the presence of avgtdix.sys in your OP and suspect that the issue may be related to this, this is not 100% conclusive atm though.


  • 0

#7
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

http://speccy.pirifo...QbJyX3L16eGbmfc

 

 

Minidumps:

 

Here are screenshots that I copy/pasted from a blue screen viewer. They are in order from the latest to the oldest. The very last one happened with Yahoo messenger and the rest happened with Zoiper.

 

===========================================================================================

 

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: Ntfs.sys

DRIVER_CORRUPTED_MMPOOL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x100000d0 (0x8a400010, 0x00000002, 0x00000001, 0x8054e4c4)

*** Ntfs.sys - Address 0xf7b53e3c base at 0xf7b52000 DateStamp 0x48025be5

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA



A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: wdmaud.sys

DRIVER_CORRUPTED_EXPOOL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x100000c5 (0x3f800004, 0x00000002, 0x00000001, 0x805515a1)

*** wdmaud.sys - Address 0xa8621468 base at 0xa8621000 DateStamp 0x48025c3e


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: portcls.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x100000d1 (0x3f80000c, 0x00000002, 0x00000000, 0xa8efd7bc)

*** portcls.sys - Address 0xa8efd7bc base at 0xa8efc000 DateStamp 0x48025ccc

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: wdmaud.sys

KERNEL_MODE_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x1000008e (0xc0000005, 0x804e7e05, 0xa81a0b3c, 0x00000000)

*** wdmaud.sys - Address 0xa86e34d0 base at 0xa86e0000 DateStamp 0x48025c3e

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: sysaudio.sys

DRIVER_CORRUPTED_EXPOOL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x100000c5 (0x400d0727, 0x00000002, 0x00000000, 0x8055196d)

*** sysaudio.sys - Address 0xa945ceb8 base at 0xa945b000 DateStamp 0x48025beb

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: avgtdix.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x100000d1 (0x40000008, 0x00000002, 0x00000000, 0xa8d1c5a0)

*** avgtdix.sys - Address 0xa8d1c5a0 base at 0xa8d1c000 DateStamp 0x51660a6c

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: wdmaud.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x100000d1 (0xc2640008, 0x00000002, 0x00000000, 0xa859e700)

*** wdmaud.sys - Address 0xa859e700 base at 0xa859e000 DateStamp 0x48025c3e

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

 

 

 

 

 

QUESTION: How would I attach the actual files of the minidumps if I had to?

 

Regarding the avgtdix.sys, it is my belief that this is not the root cause, but a symptom, since this error only happened once, and EVERY blue screen error involved running a VOIP audio program of some sort, and other errors named audio-related files usually.


  • 0

#8
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,000 posts

Can we have the actual crash dumps please;

 

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom right of the dialogue input box 
 
Regarding the avgtdix.sys, it is my belief that this is not the root cause, but a symptom, since this error only happened once, and EVERY blue screen error involved running a VOIP audio program of some sort, and other errors named audio-related files usually.

 

 

AVG can be an absolute nightmare at the best of times but keep in mind that it is a security measure that can and will block what it may deem suspicious internet traffic ie VOIP,  it is also a hog on system resources and will make short work of your 1GB of Ram.

 

Consider removing AVG and installing either Avast or MSE and you may not only find that the issue is resolved but that your system is also a little bit quicker, AVG removal tool


  • 0

#9
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

Attached is the .zip file containing the crash dumps.

 

We can address the avg stuff later ;)

 

Just to note: I mentioned I have an almost identical 2nd machine, with avg also, and it does not crash.Attached File  Mini050914-01.zip   147.38KB   107 downloads


  • 0

#10
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,000 posts

Back up any important data on the HDD as a priority and then run Driver Verifier for at least 36 hours or until the computer crashes;

To access Verifier go to Start Run and type in “verifier” without the quotes.

135.png

The Driver Verifier Manager utility will open up, select the Create standard settings option.

136.png

In the next screen select Automatically select all drivers installed on this computer.

137.png

Click on OK and then restart the computer and see if it crashes, post back with an update when you can.


  • 0

Advertisements


#11
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

"Back up any important data on the HDD as a priority"

-----------------------------

 

What is "important data"? Do I need to backup my entire HDD? This may take some time for me to make this available.

 

What do you mean by "as a priority"? Will this mess up my HD or my OS?

 

 

 

"and then run Driver Verifier for at least 36 hours or until the computer crashes;"

-------------------------

Do I need to leave the computer alone and untouched for 36 hours?

If yes, this may take awhile until I can do this

 

If no, will this cause any trouble if I am working on my pc while this is running?


  • 0

#12
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,000 posts
What is "important data"? Do I need to backup my entire HDD? This may take some time for me to make this available.
 
What do you mean by "as a priority"? Will this mess up my HD or my OS?

 

 

Anything that you cannot do without or be able to replace should the HDD fail.

As a priority means as soon as you can, it will not mess anything up, it is a safety measure and again in case it is the HDD that has problems, you seem to be aware that Ntfs.sys could suggest a HDD issue but so could the more prevalent wdmaud.sys, both can also be caused by malware infection btw so you may need the help of the experts on those forums if we are unsuccessful here.

 

Do I need to leave the computer alone and untouched for 36 hours?

 

 

No, you can use the computer as you normally would.
 
If no, will this cause any trouble if I am working on my pc while this is running?

 

 

We are running Driver Verifier to hopefully force a BSOD caused by a particular driver, this can sometimes happen straight away and sometimes after many hours, it depends on when the driver concerned is actually called into use, drivers are not all automatically loaded when you boot up the computer.
 
Driver Verifier will not cause any other issues when it is running.

  • 0

#13
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

Sorry about the delay. I had to clear up some time to make a backup.

 

So, I have made the backup and am about to begin running the verifier.

 

I will report back with whatever happens.

 

Please confirm your status if you can (that you are still monitoring this thread).

 

Thanks :)


  • 0

#14
mo713

mo713

    Member

  • Topic Starter
  • Member
  • PipPip
  • 77 posts

Now the verifier is running after a reboot. I have 2 current questions.

 

1. I notice everything is running noticeably slower. Is this because of the verifier program?

 

2. How do I see where the verifier is running? I don't see it in task manager. And how do I shut it off when I'm done?


  • 0

#15
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,000 posts

DV will not cause the computer to noticeably slow down

 

You would not know DV was running unless you get a blue screen.

 

To disable driver verifier when done go to start, run and type in verifier /reset  Click on OK and you're done.

 

Tip

If you have something to add while waiting for a reply use the edit tab – bottom right of the dialogue input box and this will ensure that no information that you provide is overlooked (this can happen if your topic has more than one page)  


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP