Yell07-11-2007 Geen internet- Nieuw ipadres gekregen en hierdoor was het  internet niet meer bereikbaar, dns lookups leken niet meer te werken, pingen was niet mogelijk maar er was wel verbinding.

Zet in de router het Translate public ip to multiple internal pcs handmatig op het nieuwe ip adres.

 

Yell05-03-2007 PREFERED MASTER BROWSER ELECTION
Mijn thuis server geeft steeds problemen en internet loopt steeds vast van wege melding 8001, 8032, 8021.
Dit komt waarschijnlijk door de printserver die erbij is gekomen. Deze voert strijd met de server wie de master browser mag zijn (Who gives a sh*t). In ieder geval heb ik geen zin in dit gekeuvel tussen computers zeker niet als mijn internet daarme foetsie is.

Also was haben wir gemacht:

Je kunt de computer browser service op handmatig zetten of:

1. Click Start, click Run, type Regedt32, and then click OK.
2. Locate the following registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\ 
3. Change the value to of MaintainServerList to No. (dat was eerst YES)(en nu toch weer no)
4. Restart the computer.
Windows NT and Windows XP

en:

Setting the IsDomainMaster parameter entry to True or Yes makes that computer a Preferred Master Browser
which has priority over other computers in master browser elections.
 Whenever a preferred master browser starts, it forces a browser election.
 Any computer running Windows NT Workstation or Windows NT Server can be configured as a preferred master browser.
If no other condition prevents it, the preferred master browser will always win the election.
Set the parameter in the following registry path:
Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Services\Browser\Parameters
Type: REG_SZ
Name: IsDomainMaster
Value: True (Dat was eerst FALSE)

How to check if your server is winning the election:  Restart the Computer Browser service and check the System event logs.  It should state that an election was forced (Event ID 8015) because the start of a Windows 2000 server Master Browser.

(Die melding verschijnt helemaal niet.)

Eens kijken of dit helpt!Wink

 

Videokaart probleem:

 


108
The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.


Memory errors or Bad memory causes the stuck in infinite loop error. The infinite loop can happen intermittently whilst playing CPU intensive games but less often when playing pure 3D games - for example my system ran GTA san andreas and got stuckin a loop

Yet this memory would cause system freezes whilst running GTA san andreas and intermittently and less frequently during normal use of the system. The error device driver got stuck in an infinite loop suggests a problem with the device itself or the device driver programming would suggest in this case device driver incorrectly programmed due to errors in the memory.

The problem can also happen with good memory that is running out of sync with the CPU under XP but is fine under Windows 98 - but it is always a memory related problem despite the error message pointing to the graphics card see this post for more info:
-------
 I had it big time with my GF3 Ti200/GF4 Ti4600 and a
motherboard I had awhile back--an Abit KT7.  The problem was that my ram bus
did not like being clocked to 133MHz. As I recall (it's been awhile) I
started seeing the infinite loop error right after going to WinXP.  The
problem was actually being caused by the fact that WinXP did not like VIA's
setup of a 133 ram bus on top of a 100Mhz fsb. Setting the ram bus to
synchronous operation with the FSB completely eliminated the problem for me.
Turned out it had nothing to do with the videocard per se, but rather had to
do with the way WinXP works versus the way Win9x works regarding 3D games
(didn't have the problem with Win9x.)

So in your case the problem is somewhere in your ram subsystem.  That's the
reason ATI could do nothing for your card under warranty--there's nothing
wrong with the card--believe it or not. I would recommend setting your
frontside bus to 100Mhz and just simply running a few games and so on to see
if you get the error. If you don't, then as you'll see that the problem
occurs when raising your fsb speeds, you will probably find out that your
ram isn't running correctly at 133MHz and that's where the culprit actually
is.  Bad ram, especially generic DDR, is right up there with inadequate
power supplies in being the most common of current computer problems.


What surprised me the most when I found this out (through my own efforts)
was that the initial diagnosis that XP made that it was a videocard driver
problem, was not actually the *root* cause of the problem--which was
actually problems in the system ram area that looped to indirectly include
the videocard driver. No wonder the "infinite loop" problem was so difficult
for so many to track down and solve--XP had us all running in circles
attending to our videocards when the source of the problem was somewhere
else.
)
---------------------
I have since found that having APIC mode enabled in the BIOS can cause the system to infinite loop more often then it should however having BAD RAM can always cause infinite loop regardless of BIOS settings but I believe disabling APIC mode is the first step in resolving this issue.


As per M293078, this issue can occur when the display driver is caught in an infinite loop, typically waiting for the video hardware to become idle. This usually indicates a problem with the video hardware or with the display driver not being able to program the hardware correctly.


If ths event occurred together with event 1003 (source: system, type: error). I reseated the video card, set the Virtual memory to 0 and then reboot, delete the pagefile.sys file and then set the virtual memory back to normal. This resolved the problem.


Install the latest video driver updates from the hardware manufacturer.  This issue is usually caused by installing a driver from Windows Update. 

 7026 
The following boot-start or system-start driver(s) failed to load:
black

Click Start, Run (Type) Regedit [Enter]
Navigate to:
HKey_Local_Machine\System\CurrentControlSet\Servic es

Expand that key, underneath will be the Services/Drivers for
the PC. Check the alphabetical listing and see if you can find
a "Black" or similar. If found, Left Click it to show the details
in the Right Pane. Locate a Key named Start and modify it's
value to 4 and disable it from starting up.


Plaats een reactie
Bekijk reacties
Go to top

  




Free website & domain name provided by blogje.eu . C.M.S. & templates © Universalis . Hosted & powered by Shopje © 2003 - 2021 .
Laatst gewijzigd: 2007-11-07 Hits: