Home > Event Id > Windows Xp Event Viewer System Error Category 102

Windows Xp Event Viewer System Error Category 102


Do you think that I have fixed them? Video card driver. Would it be the router drivers (unable to locate as yet) or my wireless card drivers? I will be turning both of these off tonightClick to expand... http://introbuilder.net/event-id/windows-xp-system-error-category-102-event-1003.php

TechSpot is a registered trademark. I see that other people have attached a zip of their minidmps, so I will do the same. Do I need to install new Memory? ---------------------------------------------------------------------------------------------------------------------------------------------- Gateway MX6426 Notebook AMD Turion 64 Mobile Technology ML-40 2.19GHz 960MB of RAM (54% Utilized) ...two 512MB DDR SDOMI 333MHz 80GB HDD BIOS: Sep 12, 2009 #10 waxdart TS Rookie Topic Starter I just had the pc freeze with no open applications at all. http://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/system-error-category-102-event-id-1003/13254e4e-6966-4a4e-8a86-264e929e6397

Event Id 1003 Windows Xp

System Error Category 102 Event 1003 Win XP Started by Unplugged09 , Oct 18 2010 04:54 PM Please log in to reply No replies to this topic #1 Unplugged09 Unplugged09 Members Set up the computer so that it does not automatically restart on system failure ..... gonna swing over to Mac soon!!!

  • I have done all kinds of checks etc and my ram checks were ok.
  • No installation required.
  • Please allow me to revive this topic.
  • Terms of Use Privacy Policy Licensing Advertise International Editions: US / UK India Login _ Welcome to TechSpot Why should I register?

Two minidumps crash at NDIS and probably it is caused by the faulty ram. BDR Jul 14, 2008 #5 Route44 TechSpot Ambassador Posts: 11,966 +70 Your error is 0xB8: ATTEMPTED_SWITCH_FROM_DPC These are generally caused by hardware issues (which often means driver issues). Please re-enable javascript to access full functionality. Event Id 1003 Office Software Protection Platform Service Then did a search for bcmw15.sys and came up empty.

Hardware failures are the most common cause and, of these, memory hardware failures are the most common. Event Id 1003 Windows Server 2003 Join thousands of tech enthusiasts and participate. Reseat the memory module to another memory slot. https://www.windowsbbs.com/threads/system-error-category-102-event-id-1003.94887/ by that i can judge that it isnt overheating.

Jan 24, 2007 #10 Blaine TS Rookie If your server supports print queues you may have a corrupt driver. Event Id 1003 Windows 7 Click here to Register a free account now! Login now. Generated Tue, 01 Nov 2016 22:23:25 GMT by s_wx1196 (squid/3.5.20) {{offlineMessage}} Store Store home Devices Microsoft Surface PCs & tablets Xbox Virtual reality Accessories Windows phone Software Office Windows Additional software

Event Id 1003 Windows Server 2003

Update the drivers. Both freezes seem to be network related thanks WD Sep 12, 2009 #11 Bobbye Helper on the Fringe Posts: 16,335 +36 I don't do the minidumps, but the Event Event Id 1003 Windows Xp Cookies Registration Notice Resolved System Error, Category 102, Event ID:1003 Discussion in 'Windows XP' started by cbvisser, 2010/08/31. 2010/08/31 cbvisser Inactive Thread Starter Joined: 2010/08/31 Messages: 6 Likes Received: 0 Trophy Event Id 1003 System Error Windows Server 2003 I suppose it is possible the applications I am using: MS Word, Endnote reference manager and online databases, are putting too great a load on the avail.

No, create an account now. http://introbuilder.net/event-id/windows-system-error-event-id-1003-category-102.php I have attached the latest minidump from todays crash as well as error details..... *************************** Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 2006/03/22 Time: Site Changelog Community Forum Software by IP.Board Sign In Use Facebook Use Twitter Need an account? Quick Links HelpWithWindows.com RoseCitySoftware.com Recommended Links Menu Log in or Sign up Search Search titles only Posted by Member: Separate names with a comma. %windir%\system32\drivers

Regards Howard Mar 22, 2006 #10 shaik TS Rookie error msg 1003 hi give me the solution for event ID 1003 . Actually update your system and get the latest drivers for all devices including your motherboard chipset drivers. Learn More. useful reference Clean the dust inside the computer case.

Couldn't sign you in, please try again. System Error 1003 Stay logged in Sign up now! If you accept cookies from this site, you will only be shown this dialog once!You can press escape or click on the X to close this box.

I see the errors are the same but this happens every time I click on something on the network!!!!

The only satisfactory way of testing RAM is to test the installed RAM in various configurations. The event viewer showed this: Product: Windows Operating System ID: 7022 Source: Service Control Manager Version: 5.2 Symbolic Name: EVENT_SERVICE_START_HUNG Message: The %1 service hung on starting. Thanks Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 8/31/2010 Time: 4:43:34 AM User: N/A Computer: CCVIEW Description: Error code 1000000a, parameter1 00000000, parameter2 00000002, Event Id 1003 Security-spp May 11, 2006 #9 Alkin TS Rookie cpc2004 said: Mini021806-01.dmp BugCheck D1, {e, 2, 0, e} Owning Process 860275f8 Image: WoW.exe Probably caused by : NDIS.sys ( NDIS!ndisMProcessDeferred+37 )Click to expand...

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Overheating of the card might explain the games freezing but the network problem remians. Log in with Facebook Log in with Twitter Log in with Google Your name or email address: Do you already have an account? this page Mini021506-08.dmp is inaccessible Mini021706-06.dmp is inaccessible Mini021706-07.dmp is inaccessible Mini021606-08.dmp BugCheck D1, {12, 2, 0, 12} Owning Process 86313a58 Image: WoW.exe Probably caused by : NDIS.sys ( NDIS!ndisMProcessDeferred+37 ) Mini021806-01.dmp BugCheck