Question

Computer rebooting during IE surfs - gives error message about IP address

Asked by: gleasoninc

I will be surfing the internet and my computer reboots.  When it comes back up, there is an error message in a "Microsoft Windows" box.  It has some BCCode errors at the top (BCCode: 100000d1 etc ending in Product: 256_1).  
The reporting details say:  This error report includes:  information regarding the condition of Microsoft Windows when teh problem occured, the operating system version and computer hardware in use, and the Internet Protocol (IP) address of your computer.

It is doing a dump to a WERab64.dir00 subdirectory in the temp subdirectory under the locall settings of my documents and settings.

Does anyone know what is causing this or how I can fix?

Thanks!

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-07-28 at 05:45:18ID24605915
Topic

Windows XP Operating System

Participating Experts
3
Points
500
Comments
16

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. reboot when surfing
    hi, my computer config is: Celeron 366 128M Ram Voodoo 3 2000 15G IBM HDD 10/100 Lan Card Recently I found my computer run slowly because I installed so much software. So I wanted to clean up my harddisk. Firstly I backup some important data at my d: (which is one of the p...
  2. Surf Internet ?
    Like this . I had winXp as my os and 1 Lan card for connecting my pc with my internal server. Now that pc also been install with 1 external modem. The problem is when the time i surf the internet the lan connection will be cut down. why it happening like this ? for your ...
  3. win2k crashes/reboots when surfing internet
    I just fdisked/formated a dual processor computer, installed win98, and upgraded to win2k. I then immediately went to microsoft.com for windows updates and security patches. However I can only surf so long - after downloading a URL or two, the machine will flash to a Blue S...
  4. Slow surfing -- intermittently.
    The problem is the recent intermittent occurrence, on my desktop computer, of very slow surfing with normal measured upload and download speeds. The normal speeds, 1192 kbps download and 210 upload, were measured during the perceived slow surfing period (and took a while to...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: astralcomputingPosted on 2009-07-28 at 06:02:30ID: 24960188

Check your event logs. This is usually due to third party software or driver problems. You IE may have been corrupted. Run sfc /scannow and have your windows disk handy. Run anti-malware software like malware bytes to check if malware or spyware is installed.

A good guide to stop errors is here: http://aumha.org/a/stop.htm

If it goes all the way to a reboot, you probably have a serious problem with drivers or software. If it is recreatable inside internet explorer, try a third party browse like firefox to diagnose if it is a kernel problem or an internet explorer problem.

 

by: KnightsmanPosted on 2009-07-28 at 06:08:52ID: 24960236

Also might be a drivers issue.  Right click on your My Computer, click on Properties, and then go to the advanced tab.  Click on settings under startup and recovery and disable automatically restart.

should cause the "blue screen of death"  Write down the error that comes up, should help us troubleshoot some more.


Also, not sure if this works, but found this on another site:
http://www.techspot.com/vb/all/windows/t-46328-The-Blue-Error-Of-Death-AGAIN-100000d1.html

 

by: noxchoPosted on 2009-07-28 at 07:32:18ID: 24961057

Look for minidumps and post them here. Rebooting means that your system got BSOD. In right click on My Computer - Properties - Advanced - Startup and Recovery uncheck the restart automatically. And since then you will be able to get BSOD and message on it.
Minidump will give us chance to track the problem causing dll or driver.

 

by: gleasonincPosted on 2009-07-31 at 11:26:35ID: 24991201

OK.  Thanks for the tips.  I did as suggested and got the BSOD.

Here's the info:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
(blah, blah)
STOP: 0x000000D1 (0x00001B860, 0x00000002, 0x00000001, 0x8837732AC)
(may have miscounted on some of the zeros!)

 

by: noxchoPosted on 2009-07-31 at 11:51:30ID: 24991392

Good. Now look for minidump and post it here. Here is the steps of minidump finding: http://www.pchell.com/support/minidumps.shtml
You will need to change the extension of the file to picture one to attach it here.

 

by: noxchoPosted on 2009-07-31 at 11:54:44ID: 24991412

This will narrow the search to definite cause of the problem and let us effectively fix it.
I would suspect problem cause by:
Firewall
WLAN\network driver
Antivirus

 

by: gleasonincPosted on 2009-08-05 at 12:45:38ID: 25027296

I downloaded and also downloaded the symbol set when the minidump gave errors on the symbol set.  However, downloading the symbol set did not help.

Here is what seems to be the meat of what I can see from the most recent one:

Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Aug  5 14:27:11.112 2009 (GMT-4)
System Uptime: 0 days 3:10:30.178

Here's another one:

Loading Dump File [C:\WINDOWS\Minidump\Mini010808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Jan  8 11:32:36.848 2008 (GMT-4)
System Uptime: 10 days 18:08:39.300
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {88f2d008, d63, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for SYMTDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
*** WARNING: Unable to verify timestamp for netbt.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
*** WARNING: Unable to verify timestamp for rdbss.sys
*** ERROR: Module load completed but symbols could not be loaded for rdbss.sys
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : SYMTDI.SYS ( SYMTDI+4e10 )

Followup: MachineOwner

 

by: noxchoPosted on 2009-08-05 at 12:54:42ID: 25027396

Good info. The cause of the problem is SYMTDI.SYS.
Do you have any Symantec product installed? If not then there is virus in your system.
Look this link: http://securityresponse.symantec.com/avcenter/security/Content/2007.07.11d.html
and here: http://www.file.net/process/symtdi.sys.html

 

by: gleasonincPosted on 2009-08-05 at 13:30:24ID: 25027788

Thanks!  Great, I see that.   What about the latest dump (referenced at the top) that says:

Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Aug  5 14:27:11.112 2009 (GMT-4)
System Uptime: 0 days 3:10:30.178

 

by: gleasonincPosted on 2009-08-05 at 13:31:20ID: 25027797

Also, yes, I do use Symantec.  Do you recommend uninstall/reinstall?

 

by: noxchoPosted on 2009-08-05 at 14:03:36ID: 25028067

The first part of the dump is not important. It failed to gather info about all files.
According to first link I gave you I would update to latest version of Symantec and also scan the PC for rootkits, viruses etc. BTW, Symantec antivirus sometimes misses viruses so I used to test with two antiviruses the laptop of my user to detect more than 22 viruses there while Norton 2009 was on it.

 

by: gleasonincPosted on 2009-08-07 at 05:39:23ID: 25042010

Ok, did everything as above and still did not correct problem.   Also found out that the original message "*** WARNING: Unable to verify timestamp for ntoskrnl.exe" has to do with the network adapter, so updated drivers on that also.

DId not help.  I also found out that even though Ioaded the symbol set, I had to set the symbol set path inside the windbg program. So I did that too.

Here's the latest one:

Loading Dump File [C:\WINDOWS\Minidump\Mini080709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug  7 08:23:37.692 2009 (GMT-4)
System Uptime: 0 days 18:21:42.842
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {bacc8018, 2, 0, 887400ad}

Unable to load image RtkHDAud.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
Probably caused by : portcls.sys ( portcls!CPortWaveCyclic::Notify+e )

Followup: MachineOwner

 

by: gleasonincPosted on 2009-08-07 at 06:37:51ID: 25042517

Got the same crash again, but hit the hyperlink for analyze and got this:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini080709-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug  7 09:26:09.507 2009 (GMT-4)
System Uptime: 0 days 1:02:02.931
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {6c3a82ed, 2, 1, 89784dad}

Unable to load image RtkHDAud.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
Probably caused by : portcls.sys ( portcls!CPortWaveCyclic::Notify+e )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 6c3a82ed, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 89784dad, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  6c3a82ed

CURRENT_IRQL:  2

FAULTING_IP:
+28
89784dad dfb4b801000000  fbstp   tbyte ptr [eax+edi*4+1]

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b89cea3b to 89784dad

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
805512b0 b89cea3b 8968e5a0 805513fc b8a30a64 0x89784dad
805512bc b8a30a64 89c677d8 8968e5a0 b8b43d6c portcls!CPortWaveCyclic::Notify+0xe
805513fc 8050232b 8055c0c0 ffdff9c0 ffdff000 RtkHDAud+0x3fa64
80551428 80545e7f 8055c4c0 00000000 0003a2bb nt!KiTimerExpiration+0xb1
80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61
80551450 80545d64 00000000 0000000e 00000000 nt!KiIdleThread0
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND:  kb

FOLLOWUP_IP:
portcls!CPortWaveCyclic::Notify+e
b89cea3b 5d              pop     ebp

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  portcls!CPortWaveCyclic::Notify+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: portcls

IMAGE_NAME:  portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025ccc

FAILURE_BUCKET_ID:  0xD1_portcls!CPortWaveCyclic::Notify+e

BUCKET_ID:  0xD1_portcls!CPortWaveCyclic::Notify+e

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

 

by: noxchoPosted on 2009-08-08 at 10:11:26ID: 25050924

Ok, looks like new problem - Audio controller.
Uninstall this device drivers via Device Manager and try to surf internet. Is there any error?

 

by: gleasonincPosted on 2009-09-04 at 09:30:08ID: 31608704

That was a winner!  Thanks!

 

by: noxchoPosted on 2009-09-04 at 09:45:59ID: 25261304

Glad to hear it worked for you.
Take care.

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...