OngoingWalnut

Hi. My Vista rig has recently been crashing to two bluescreens at seemingly random intervals. The first BSoD states:

"A wait operation, attach process, or yield was attempted from a DPC routine."

and the other BSoD states:

"NSDriver.sys
The driver is attempting to access memory after it has been freed."

I looked on google for NSDriver.sys, and it's apparently part of Ad-Aware 2007, so I've uninstalled that as of now, which has (as far as I can tell) stopped that blue screen from appearing. However, I'm still getting the first "DPC routine" BSoD occasionally.

Does anyone have any suggestions?
Thank you.
Sincerely,
Kingsley

OngoingWalnut

Here is the bluescreen message:

jcgriff2

Hi Kingsley. . .

Welcome to the Tech Support Forum - Vista Support!

Nice picture.

Good work by un-installing Ad-Aware 2007. Now we need to see if the driver causing the 0x000000b8 bugcheck will reveal itself so that the program it belongs to can be un-installed.

There should be mini dump files located in c:\windows\minidump. Please gather them all, zip them up and attach to your next post along with a msinfo32 NFO file. Bring up an Elevated command prompt by clicking on START, type cmd.exe into the start search box, right-click on cmd.exe, select Run as Administrator, type msinfo32.exe, hit enter, when the System Information viewer comes up, save it as an NFO file - this is a must!

Also, from that same Elevated command prompt screen, type the following to execute the Vista System File Checker/Repair utility program, sfc:

sfc /scannow

Let it run - depending on your system, it may be 10 min or an hour.

Regards. . .

jcgriff2

.

OngoingWalnut

Hi jcgriff2. Thank you for helping me!
Before I saw your message, I tried installing Vista Service Pack 1, but the bluescreen came back up shortly after and the automated windows repair system (startup repair utility I believe it was) system restored me back to pre-sp1 install.

Here are all the minidumps, plus the NFO file, and the sfc log. The command windows says "Windows REsource PRotection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log...The system file repair changes will take effect after the next reboot." which I shall do now. :)

Attached Files

Kingsley - Minidumps, Sysinfo, and log.zip (243.6 KB, 1 views)

jcgriff2

Hi. . .

I picked up the file - but have question or 2 -

Have you gotton any more BSODs since the system Restore? Is the NFO file pre-sfc?

Regards. . .

jcgriff2

OngoingWalnut

Hi jcgriff2,
1. Since the system restore and following your instructions, I haven't encounted any more BSODs...yet.
2. The NFO is pre-sfc. Here's the post-sfc if it helps. =)

Thanks,
Kingsley

Attached Files

Post-sfc SystemInformation.zip (75.1 KB, 1 views)

jcgriff2

Hi. . .

I picked up the new file - thanks.

When you attempted installation of SP1, did it come to you via Windows Updates or did you download it and try to install yourself?

Are your Windows updates set on automatic?

jcgriff2

OngoingWalnut

Hi jcgriff2,
I downloaded Service Pack 1 at work and installed it on this home computer - the dialup access I have here doesn't take to large files easily. (Especially when the download gets cut off from a BSOD!)

Yes, my Windows Update says it is set to Install Updates Automatically.
(However, according to the 'available updates', there are apparently three important MS Office updates and two misc optional updates "waiting" to be downloaded and installed.) :/

OngoingWalnut

Update - I received the same BSOD again last night. :(

jcgriff2

Hi. . .

I started processing the dumps and it appears that your (WinDDK) Conexant Systems softK56 modem driver HSX_CNXT.sys is the probable cause of the 0x000000b8 BSODs. It may need to be updated - contact the manufacturer of your PC or go to their web site to see if updated driver(s) are available.

Also, I noticed that you are running !Avast. I have seen many a BSOD caused by this product, but am unsure of the version you are running.

I would suggest that you boot-up in SAFEMODE w/Networking - tap the F8 key repeatedly during boot-up. Test your Internet connection while in SAFEMODE and see if BSODs continue. This would tell us whether antivirus is interfering as opposed to the modem driver being the actual problem.

Regards. . .

jcgriff2

.

OngoingWalnut

Alright, thank you! I tried the SAFEMODE w/Networking, but when I attempted to launch my dialup connection, windows said it "cannot be found". It also doesn't show up in network connections while in safe mode w/networking.

I tried making a new dial-up connection to see if this was just an oddity with that single connection, but when I tried, Windows could not detect a dialup modem at all.

I've since started windows normally and have tried hunting down the Conexant Systems drivers from Hewlett-Packard's (my computer manufacturer's) website. Doesn't look like much luck there, but the Conexant Systems website seems to have some generic drivers. http://www.conexant.com/support/md_driverdownload.jsp
Would you suggest downloading one of these?

Re: Avast, I'm running version 4.8 Home edition. I used to run AVG, which admittedly I liked better. :P

jcgriff2

What bothers me about the site - the link you provided - is that I don't see any drivers for Vista - only XP.

Has this been running OK within Vista - and for how long?

Regards. . .

jcgriff2

.

OngoingWalnut

Hi jcgriff2,
Rather than install those website drivers, I tried rolling back my modem driver, and the BSOD's don't appear anymore! The only possibly worrisome side effect seems to be this:

Do you think I should leave this driver non-functional? I'm somewhat worried to ask windows to remedy it, considering the BSODs might return. o.o

Thank you so much for the continued support!
Sincerely,
Kingsley

jcgriff2

Hi. . .

I will ask a hardware expert to weigh in on the driver/device in question.

Regards. . .

jcgriff2

dai

just leave it
http://technet.microsoft.com/en-us/m.../cc194397.aspx