Jump to content

HDD-activity led blijft branden, pc blokkeert en start opnieuw op???


Jan Ambers
 Share

Recommended Posts

HDD-activity led blijft branden, pc blokkeert gaat uit en start opnieuw op, zomaar zonder schaamte; en alsof er niks gebeurd is???

 

Ik heb SpybotS&D erop losgelaten(v1.6.2): niks gevonden...

Scan gedaan met Avast-Ativir: niks gevonden??? crazy

Welk beest zou er nu in m'n vlooiencircus een thuis gevonden hebben, en er zich tot mijn grote ergernis amuseren???

confused

Link to post
Share on other sites


al eens in taakbeheer gaan kijken ??

M7 Sat 801-Technomate 5600 ci-usb - Pace dsr8141/22 - Smartwi=rip - 1x disc triax 88 thuis - 1x disc hirsman 64 camping - duo lnb's astra1-3 + nog een hoop antiek

Lokatie's hoevenen & blier (belgië)

Link to post
Share on other sites

schijf testen lijkt me idd het beste.

 

En kun je nog meer vertellen? Waar was je mee bezig? Gebeurt het constant op hetzelfde punt? Gebeurt het net zo snel met een koude als warme PC? etc.

Weet je wat erger is dan een worm in je appel?

Een halve worm in je appel...

Link to post
Share on other sites

Zet sowieso "automatisch opnieuw opstarten" uit:

Rechts klikkn op mijn computer->eigenschappen -> geavanceerd -> opstart en herstelinstellingen -> vinkje weghalen.

 

Dan start hij niet meer opnieuw op, indien het tenminste het gevolg is van een of andere fout. Dan kun je de foutmelding lezen.

 

Link to post
Share on other sites

Vinke is idd weggehaald... vraag meaf waar jullie die wijsheid toch vandaan halen???

Smerige is wel dat het o zo random gebeurt!

Soms nooit gedurende 14 dagen, soms 2x bij surfen 'smorgens en gans de dag niks meer, en dan 'savonds weer ne keer???

Elke keer, blijft HDDled branden en is de muis cursor weg en krijg ik die niet terug en plots rebooten alles dan terug normaal...???

Als ik de netschakelaar af en aan zet duurt het soms! wel een tijdje dat ie met zijn windows scherm blijft aanstaan en de blauwe blokjes maar blijven voorbij schuiven en plots gaat ie verder.

Behalve de antivirus gaan er geen backbround programma's!(voorzover ik het weet!)

Link to post
Share on other sites

Deze morgen opnieuw opgestart en 2x een geblokkeerd systeem!

Kwam wel voor met IE7, nog niet gehad met Opera, en nog niet gehad met enig ander programma.

 

Blauwscherm met melding:

Probleem in Windows: Bad pool caller

raade aan om soft en HW te herinstalleren...Merci!

2de keer:

Probleem in Windows: IRQL_NOT_LESS_OR_EQUAL

Link to post
Share on other sites

Error Message:

 

IRQL_NOT_LESS_OR_EQUAL

 

Explanation:

 

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

 

User Action:

 

This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If you encounter this error while upgrading from Windows NT 4.0 or earlier, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools. For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You should also run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Disable sync negotiation in the SCSI BIOS, check the cables and the SCSI IDs of each device, and confirm proper termination. For enhanced integrated device electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave/stand-alone setting. Remove all EIDE devices except for hard disks. If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.

 

 

Weet je wat erger is dan een worm in je appel?

Een halve worm in je appel...

Link to post
Share on other sites

BAD_POOL_CALLER is a stop error message that is caused because of problems with the memory management. The error is seen when the computer is started up and displays the blue screen of death and gives the following message: “A problem has been detected and windows has been shut down to prevent damage to your computer”.

 

BAD_POOL_CALLER. stop: 0×000000c2 (0×000000043, 0xc2528000, 0×00000000, 0×00000000) ”

 

Each of these stop error parameters is for a different problem. There is a list of more than thirty such causes that can give you this error message. If the stop error is consistent every time the system is rebooted, the following method will be effective in solving the problem:

 

* The hardware and RAM should be checked initially.

* Boot the system once again using the OS setup CD, or use a boot setup that has a GUI like BartPE.

* With RunScanner it is possible to use a memory test tool.

* Select a single account

* If all the accounts open then the system registry hive might be the problem.

* Locate the hive damaged and rename it, do not delete it.

* Create another hive from the backup or from the restore point.

* Initially uses the latest one and keep checking the restore points that come later.

* Avoiding harvesting any replacement hives from the hard drive booted Windows.

* After which compare the hives for differences.

 

This is one of the ways of fixing BAD_POOL_CALLER errors. Another method is to reinstall the OS but occasionally shows a disk read error or an error on the same lines. Switching the computer off for a minute or more and then switching it on can solve it since the error is only a slight glitch in the system operation.

 

The BAD_POOL_CALLER is seen for the first time after installing a hardware or software it is recommended that the computer be restarted. If it doesn’t solve the problem, the installation of the hardware or software should be checked for correction. The manufacture should also be contacted if there are any Windows updates required to correct the error. If the problem persists the installed hardware and software should be disabled, and the BIOS memory options like caching or shadowing should be disabled too. The safe mode can be used as well to remove or stop components.

 

To enable the safe mode just press F8 when the machine is being restarted and select it from the Advance Startup options and correct the problem. The installation of the graphics card is another reason the BAD_POOL_CALLER error shows up. A simple reinstallation of the driver can solve the problem. Microsoft has also acknowledged that the BAD_POOL_CALLER Stop 0xC2 error pops up when trying to print a document that contains a corrupt font.

 

A hot fix is available at www.support.microsoft.com, where the telephone number can be acquired to contact support. The call to the support team is charged except if the support team has resolved that the update will solve the problem. The error message with relation to this parameter of the BAD_POOL_CALLER error is seen only in the Win2000 Professional, Server and Advanced Server Operating Systems.

 

 

Weet je wat erger is dan een worm in je appel?

Een halve worm in je appel...

Link to post
Share on other sites

Krijg meer het gevoel dat het je geheugen is nu.

 

Zitten er 2 Dimmen in? Moet je er eens de 2e uithalen. Kijken of hij het dan nog doet. En zo ja, ze omdraaien en nogmaals proberen.

Weet je wat erger is dan een worm in je appel?

Een halve worm in je appel...

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

Lees alvorens je verder gaat onze Terms of Use en Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.