BSOD Windows Vista SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

[anoniem]

Hallo allemaal, Mijn Dell Inspiron 1720 wordt al sinds jaren geplaagd door blauwe schermen die in golven terugkomen. Pas geleden heb ik daarom besloten weer eens mijn laptop te formatteren. De eerste twee keren had ik toen echter grote problemen om de service packs en .NET Framework geïnstalleerd te krijgen. Pas bij de derde keer toen ik gelijk na het formatteren zelf zonder Windows Update de service packs geïnstalleerd heb alvorens iets anders te installeren ging het goed. Echter begonnen na zo'n twee dagen weer de BSODs en nu nog veel frequenter dan voorheen. De melding is de laatste dagen bijna altijd SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. Voorheen was het doorgaans BAD_POOL_CALLER, MEMORY_MANAGEMENT of IRLQ_NOT_LESS_OR_EQUAL. Aangezien het meeste op een probleem met RAM duidde heb ik Memtest86+ (tot wel 17 passes) en heb de diagnostische tests van Dell gedaan, maar er wordt geen enkele fout gevonden. Ik snap er niets meer van. Ik heb een .zip-bestand waarin alle minidumpfoutmeldingen en overige informatie over foutmeldingen staat dat ik met behulp van een programmaatje van een andere site gegenereerd heb. Ik zie hier alleen geen optie om dat hier toe te voegen. Mocht iemand me kunnen helpen, dan ben ik daar erg dankbaar voor, want ik weet hier eerlijk gezegd geen raad meer mee..

[anoniem]

Doe onderstaande: [url=http://www.resplendence.com/whocrashed]WhoCrashed introductie[/url] [url=http://www.softpedia.com/get/Antivirus/WhoCrashed.shtml]WhoCrashed beschrijving[/url] Download de [i:3c8923a740]free home edition[/i:3c8923a740] van [b:3c8923a740]WhoCrashed[/b:3c8923a740] naar je bureaublad via [url=http://www.resplendence.com/downloads]klik hier[/url] [img:3c8923a740]http://i65.servimg.com/u/f65/11/35/67/12/whocra10.png[/img:3c8923a740] en installeer het tool via klikken/dubbelklikken op "[b:3c8923a740]whocrashedSetup.exe[/b:3c8923a740]" Nadat 'WhoCrashed' is opgestart, klik je op de "[b:3c8923a740]Analyze[/b:3c8923a740]" knop. Selekteer nu de inhoud van het venster, kopieer dit en post het resultaat in je volgende post.

[anoniem]

[quote:48aa324bc1="Abraham54"]Doe onderstaande: [url=http://www.resplendence.com/whocrashed]WhoCrashed introductie[/url] Hallo, bedankt voor de snelle reactie. Is dit niet ongeveer hetzelfde als BlueScreenView? Nou ja, ik kan het ook nog een keer proberen... [url=http://www.softpedia.com/get/Antivirus/WhoCrashed.shtml]WhoCrashed beschrijving[/url] Download de [i:48aa324bc1]free home edition[/i:48aa324bc1] van [b:48aa324bc1]WhoCrashed[/b:48aa324bc1] naar je bureaublad via [url=http://www.resplendence.com/downloads]klik hier[/url] [img:48aa324bc1]http://i65.servimg.com/u/f65/11/35/67/12/whocra10.png[/img:48aa324bc1] en installeer het tool via klikken/dubbelklikken op "[b:48aa324bc1]whocrashedSetup.exe[/b:48aa324bc1]" Nadat 'WhoCrashed' is opgestart, klik je op de "[b:48aa324bc1]Analyze[/b:48aa324bc1]" knop. Selekteer nu de inhoud van het venster, kopieer dit en post het resultaat in je volgende post.[/quote:48aa324bc1]

[anoniem]

Het resultaat is als volgt (ik geef hier enkel de drie BSODs van vanmorgen weer, anders wordt het een beetje veel): On Mon 29-10-2012 8:07:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102912-03.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x16EDE) Bugcheck code: 0xC1 (0xFFFFFFFFC364CEE8, 0x0, 0x118, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\ntfs.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: NT-bestandssysteemstuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 29-10-2012 8:01:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102912-02.dmp This was probably caused by the following module: win32k.sys (win32k+0xCB473) Bugcheck code: 0xC1 (0xFFFFFFFFFA092B70, 0x0, 0x490, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 29-10-2012 7:56:46 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102912-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xA74EF) Bugcheck code: 0xC1 (0xFFFFFFFFFAB38F48, 0x0, 0xB8, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[anoniem]

Graag het hele log! Dus ook met de conclusie van WhoCrashed!

[anoniem]

OK, hier komt het. Genoemde drivers in de conclusie zijn echter allang van de computer, aangezien ik op aanraden van anderen McAfee al verwijderd heb. De BSODs worden er echter niet minder om. Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 29-10-2012 8:07:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102912-03.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x16EDE) Bugcheck code: 0xC1 (0xFFFFFFFFC364CEE8, 0x0, 0x118, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\ntfs.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: NT-bestandssysteemstuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 29-10-2012 8:07:26 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x16EDE) Bugcheck code: 0xC1 (0xFFFFFFFFC364CEE8, 0x0, 0x118, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\ntfs.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: NT-bestandssysteemstuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 29-10-2012 8:01:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102912-02.dmp This was probably caused by the following module: win32k.sys (win32k+0xCB473) Bugcheck code: 0xC1 (0xFFFFFFFFFA092B70, 0x0, 0x490, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 29-10-2012 7:56:46 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102912-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xA74EF) Bugcheck code: 0xC1 (0xFFFFFFFFFAB38F48, 0x0, 0xB8, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sun 28-10-2012 20:02:08 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-08.dmp This was probably caused by the following module: win32k.sys (win32k+0x1286AD) Bugcheck code: 0xC1 (0xFFFFFFFFAA38CFB8, 0x0, 0x48, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sun 28-10-2012 19:38:41 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-07.dmp This was probably caused by the following module: fltmgr.sys (fltmgr+0x2AB8) Bugcheck code: 0xC1 (0xFFFFFFFFB350EFA0, 0x0, 0x60, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\fltmgr.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Microsoft Bestandssysteemfilterbeheer Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sun 28-10-2012 14:24:25 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-06.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF) Bugcheck code: 0x1A (0x4000, 0xFFFFFFFF8DA4DE60, 0xFFFFFFFF80000000, 0x17DFED) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 28-10-2012 13:34:32 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-05.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF) Bugcheck code: 0xC1 (0xFFFFFFFFB37B4F68, 0x0, 0x98, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 28-10-2012 11:19:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-04.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF) Bugcheck code: 0xC1 (0xFFFFFFFFAE74EF68, 0x0, 0x98, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 28-10-2012 11:11:56 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-03.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x9614A) Bugcheck code: 0xC1 (0xFFFFFFFFC1696F00, 0x0, 0x100, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\ntfs.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: NT-bestandssysteemstuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sun 28-10-2012 10:35:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-02.dmp This was probably caused by the following module: mfehidk.sys (mfehidk+0x15A7E) Bugcheck code: 0xC1 (0xFFFFFFFFB79B2FE0, 0x0, 0x20, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys . Google query: mfehidk.sys SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION On Sun 28-10-2012 7:40:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102812-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0xB050B) Bugcheck code: 0xC1 (0xFFFFFFFF90BA4F78, 0x0, 0x88, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\ntfs.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: NT-bestandssysteemstuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sat 27-10-2012 15:38:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102712-08.dmp This was probably caused by the following module: fltmgr.sys (fltmgr+0x2AB8) Bugcheck code: 0xC1 (0xFFFFFFFFAF752FD8, 0x0, 0x28, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\drivers\fltmgr.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Microsoft Bestandssysteemfilterbeheer Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sat 27-10-2012 15:30:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102712-07.dmp This was probably caused by the following module: mfehidk.sys (mfehidk+0x5A542) Bugcheck code: 0xC1 (0xFFFFFFFFB8E02F90, 0x0, 0x70, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys . Google query: mfehidk.sys SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION On Sat 27-10-2012 14:59:02 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini102712-06.dmp This was probably caused by the following module: win32k.sys (win32k+0x1AB25B) Bugcheck code: 0xC1 (0xFFFFFFFFFAC8AFC0, 0x0, 0x40, 0x22) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION file path: C:\Windows\system32\win32k.sys product: Besturingssysteem Microsoft® Windows® company: Microsoft Corporation description: Multi-User Win32-stuurprogramma Bug check description: This indicates that the driver wrote to an invalid section of the special pool. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 40 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: mfehidk.sys mfefirek.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

[anoniem]

Heb je McAfee dus verwijderd? Heb je daarbij ook het speciale McAfee removal gebruikt? Zie daarvoor: http://www.chip.de/downloads/McAfee-Consumer-Product-Removal-Tool_49841374.html En welke antivirussoftware gebruik jij dan nu?

[anoniem]

Ja, McAfee is al weg. Ik heb ook de removal gebruikt. Ik heb vanmorgen ook nog specifiek naar de genoemde drivers gezocht, maar die zijn echt niet meer op de computer. Je kunt ook zien dat bij de laatste BSODs (na het verwijderen van McAfee) deze drivers ook niet meer genoemd worden, maar andere. Er staat nu Microsoft Security Essentials op.

[anoniem]

De BSODs begonnen ook al voor het installeren van McAfee, enkel heetten ze voorheen (weet niet of dat met McAfee te maken heeft) verschillend. De laatste dagen is het op één keer na enkel nog SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.

[anoniem]

Is het XP of Vista? Ook de drivers van Dell zelf opgehaald m.n. waar dringend bij staat? Test, disable de wifi netwerkkaart in apparaatbeheer, reboot, nog steeds dezelfde problemen?

[anoniem]

Is jouw Windows uptodate en voorzien van alle servicepacks? Heb je de antivirussoftware al een systeemscan laten doen? En doe ook het volgende: [b:74853b3a55]Welk programma[/b:74853b3a55]: CrystalDiskInfo [b:74853b3a55]Waarvoor/waarom[/b:74853b3a55]: controle van van SMART-gegevens van de harddisk(s) [b:74853b3a55]Moeilijkheidsgraad[/b:74853b3a55]: geen. [b:74853b3a55]Download CrystalDiskInfo[/b:74853b3a55] [url=http://crystalmark.info/software/CrystalDiskInfo/index-e.html][b:74853b3a55]hier[/b:74853b3a55][/url] [img:74853b3a55]http://www.imgdumper.nl/uploads4/4df870efec9f5/4df870efeba86-CrystalDiskInfo.png[/img:74853b3a55] Installeer het tool en start vervolgens CrystalDiskInfo [color=#FF0000:74853b3a55][b:74853b3a55]N.B. vink wel de meeliftende software uit, indien je niet wenst dat dit ook wordt geïnstalleerd.[/b:74853b3a55][/color:74853b3a55] Het tool leest daarop de SMART-gegevens van de aangesloten harddisks. Is de kleur Blauw - dan volledig gezond. Is de kleur Geel - dan zijn er problemen. Is de kleur Rood - dan de HD z.s.m. vervangen. Bij SSD's wordt ook de gezondheidstoestand van de SSD's vermeld (Health)