Mededeling

Collapse
No announcement yet.

Diverse keren een blauw scherm

Collapse
This topic is closed.
X
X
 
  • Filter
  • Tijd
  • Show
Clear All
new posts

  • Diverse keren een blauw scherm

    Goedenavond

    De PC van mijn moeder geeft constant een blauw scherm
    Ik heb al een aantal drivers ge-update maar steeds zonder resultaat.
    Het gaat om een packard bell istart 8300 aio.draaid op windows 7 home premium 32bits

    de onderstaande meldingen zijn vanaf september.
    de afgelopen week was het elke dag wel raak.

    Kan iemand mij helpen??





    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Thu 21-11-2013 15:40:32 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112113-18002-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
    Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC0562400, 0xFFFFFFFF86D373D0, 0x0)
    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 Thu 21-11-2013 15:40:32 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
    Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC0562400, 0xFFFFFFFF86D373D0, 0x0)
    Error: MEMORY_MANAGEMENT
    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.
    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: ntkrpamp.exe .
    Google query: ntkrpamp.exe MEMORY_MANAGEMENT



    On Thu 21-11-2013 8:45:48 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112113-20451-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xBDECE)
    Bugcheck code: 0xBE (0xFFFFFFFF99102D94, 0x4C210021, 0xFFFFFFFFA5F9DBF4, 0xB)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    file path: C:\Windows\system32\win32k.sys
    product: Besturingssysteem Microsoft® Windows®
    company: Microsoft Corporation
    description: Multi-User Win32-stuurprogramma
    Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
    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 Tue 19-11-2013 19:56:53 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111913-24710-01.dmp
    This was probably caused by the following module: rdyboost.sys (rdyboost+0x1BA3)
    Bugcheck code: 0xA (0xFFFFFFFFE9200008, 0x2, 0x1, 0xFFFFFFFF82AE732E)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\rdyboost.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: ReadyBoost Driver
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 Tue 19-11-2013 16:00:20 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111913-87329-01.dmp
    This was probably caused by the following module: fltmgr.sys (fltmgr+0x20DF4)
    Bugcheck code: 0x19 (0x20, 0xFFFFFFFF85C97B40, 0xFFFFFFFF85C98988, 0x9C97B3C)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Besturingssysteem Microsoft® Windows®
    company: Microsoft Corporation
    description: Microsoft Bestandssysteemfilterbeheer
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 Tue 19-11-2013 14:49:30 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111913-26254-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xAD317)
    Bugcheck code: 0xC5 (0x730077, 0x2, 0x0, 0xFFFFFFFF82B77985)
    Error: DRIVER_CORRUPTED_EXPOOL
    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 system attempted to access invalid memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 Wed 13-11-2013 15:34:13 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111313-28314-01.dmp
    This was probably caused by the following module: usbport.sys (USBPORT+0x430D)
    Bugcheck code: 0xD1 (0xFFFFFFFF80200000, 0x2, 0x8, 0xFFFFFFFF80200000)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\usbport.sys
    product: Besturingssysteem Microsoft® Windows®
    company: Microsoft Corporation
    description: Poortstuurprogramma voor USB 1.1 en 2.0
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 11-11-2013 11:19:46 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111113-22651-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x120C6B)
    Bugcheck code: 0xC2 (0x7, 0x109B, 0x5B004F, 0xFFFFFFFFA8BA08E8)
    Error: BAD_POOL_CALLER
    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 current thread is making a bad pool request.
    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 Thu 7-11-2013 12:44:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110713-19266-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
    Bugcheck code: 0x4E (0x99, 0x1E5C0, 0x3, 0x97E05)
    Error: PFN_LIST_CORRUPT
    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 page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Tue 15-10-2013 15:40:47 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101513-26691-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
    Bugcheck code: 0x1A (0x41287, 0x140F524, 0x0, 0x0)
    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.




    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    15 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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:

    ntkrpamp.exe

    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.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

  • #2
    Begin met geheugencontrole. Klik op Start → Systeembeheer → Hulpprogramma voor geheugencontrole

    Open opdrachtregel met administratorrechten * Start op in veilige modus *.

    Comment


    • #3
      Welk programma heb je gebruikt om de dumpfiles uit te lezen? Je startpost geeft veel informatie, waarvoor dank.
      De dumpfiles duiden op systeembestanden en dat duidt vaak op hardwareproblemen.

      Begin met de geheugentest die Dorado je adviseert. Daarnaast: zijn er nog andere problemen met de pc? Loopt deze ook vaak vast, maken de ventilatoren veel geluid of is hij overdreven traag?


      Het rapaille dat per Przewalskipaard arriveerde bij het feeëriek gesitueerde etablissement - komma -

      "Verwar de waarheid niet met de mening van de meerderheid"

      Comment


      • #4
        Heel erg bedankt voor jullie reacties.

        Het programma wat we gebruikt hebben is WhoCrashed
        PC is niet traag maar geeft elk dag wel 1 a 2 keer een blauw scherm.
        geheugentest heb ik uitgevoerd en heeft geen problemen gevonden.
        hieronder de laatste dumpfiles.

        is er ook een mogelijkheid om de grafische kaart te testen??
        Of heeft de pc te weinig intern geheugen waardoor het vastloopt??



        System Information (local)
        --------------------------------------------------------------------------------

        computer name: ELS-PC
        windows version: Windows 7 Service Pack 1, 6.1, build: 7601
        windows dir: C:\Windows
        Hardware: ISTART 8300 AIO, Packard Bell BV,
        CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ AMD586, level: 15
        2 logical processors, active mask: 3
        RAM: 2952060928 total
        VM: 2147352576, free: 1939091456




        --------------------------------------------------------------------------------
        Crash Dump Analysis
        --------------------------------------------------------------------------------

        Crash dump directory: C:\Windows\Minidump

        Crash dumps are enabled on your computer.

        On Wed 27-11-2013 15:34:39 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112813-22245-01.dmp
        This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
        Bugcheck code: 0xA (0x29, 0x2, 0x1, 0xFFFFFFFF82AB21CA)
        Error: IRQL_NOT_LESS_OR_EQUAL
        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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
        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 Wed 27-11-2013 15:34:39 GMT your computer crashed
        crash dump file: C:\Windows\memory.dmp
        This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
        Bugcheck code: 0xA (0x29, 0x2, 0x1, 0xFFFFFFFF82AB21CA)
        Error: IRQL_NOT_LESS_OR_EQUAL
        Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
        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: ntkrpamp.exe .
        Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL



        On Tue 26-11-2013 9:01:08 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112613-40092-01.dmp
        This was probably caused by the following module: win32k.sys (win32k+0xCC53A)
        Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B734C1, 0xFFFFFFFF96A7D9D4, 0x0)
        Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
        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 a kernel-mode program generated an exception which the error handler did not catch.
        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 Tue 26-11-2013 8:34:49 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112613-26036-01.dmp
        This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
        Bugcheck code: 0x50 (0xFFFFFFFFBBA0000F, 0x0, 0xFFFFFFFF82AD3D65, 0x2)
        Error: PAGE_FAULT_IN_NONPAGED_AREA
        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 invalid system memory has been referenced.
        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 Mon 25-11-2013 8:56:38 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112513-21621-01.dmp
        This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
        Bugcheck code: 0xA (0x43F129C, 0x2, 0x0, 0xFFFFFFFF82ACBDA3)
        Error: IRQL_NOT_LESS_OR_EQUAL
        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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
        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 24-11-2013 9:18:43 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112413-23306-01.dmp
        This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
        Bugcheck code: 0x4E (0x99, 0xA0BB7, 0x2, 0x1)
        Error: PFN_LIST_CORRUPT
        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 page frame number (PFN) list is corrupted.
        This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sat 23-11-2013 16:41:37 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112413-22666-01.dmp
        This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
        Bugcheck code: 0x1A (0x41284, 0x9C5E001, 0x2854, 0xFFFFFFFFC0802000)
        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 Thu 21-11-2013 15:40:32 GMT your computer crashed
        crash dump file: C:\Windows\Minidump\112113-18002-01.dmp
        This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
        Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC0562400, 0xFFFFFFFF86D373D0, 0x0)
        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.

        Comment


        • #5
          oja het intern geheugen is 3gb

          Comment


          • #6
            Weet iemand een oplossing??

            Comment


            • #7
              Ik heb ook met de pc bsod gehad. de harde schijf was bijna ten einde. Ik raad je aan om je harde schijf te controleren met bv HD tune of Crystaldiskinfo of mogelijk heeft de fabrikant van je harde schijf een diagnostisch tool om je harde schijf te controleren. Maak ook een back up van de harde schijf op een externe schijf. Misschien nog garantie op de pc?

              succes

              Comment


              • #8
                Download HWINFO & kies de 32- of 64bitsversie al naargelang je windowsversie is & installeer het programma.
                (Hier kan vastgesteld worden of je OS 32 of 64bits is.)

                Klik na installatie op Run, daarna 2x op Close → Save Report → Short Text Report.
                Post deze resultaten in je volgende bericht.

                Open opdrachtregel met administratorrechten * Start op in veilige modus *.

                Comment


                • #9
                  Wegens gebrek aan feedback zet ik dit topic op de status opgelost.

                  Open opdrachtregel met administratorrechten * Start op in veilige modus *.

                  Comment


                  • #10
                    Gebrek aan tijd

                    Wegens gebrek aan tijd omdat ik de afgelopen weken veel gewerkt hebt ben ik er nog niet aan toe gekomen om de harde schijf te testen.

                    Vanaf woensdag ben ik een aantal dagen vrij en ga dan de test uitvoeren.

                    Bedankt voor de reacties :-)

                    Comment


                    • #11
                      Hallo Kelly en bedankt voor je terugkoppeling!
                      We zetten de vraag opnieuw "beantwoord" (niet opgelost) voor je.


                      Het rapaille dat per Przewalskipaard arriveerde bij het feeëriek gesitueerde etablissement - komma -

                      "Verwar de waarheid niet met de mening van de meerderheid"

                      Comment


                      • #12
                        Goedemiddag

                        met HWINFO deze gegevens gevonden.

                        Computer: Packard Bell BV ISTART 8300 AIO
                        CPU: AMD Athlon 64 X2 4000+ (Brisbane, BH-G1)
                        2100 MHz (10.50x200.0) @ 2099 MHz (10.50x200.0)
                        Motherboard: Packard Bell BV
                        Chipset: nVidia nForce 630a (MCP68)
                        Memory: 3072 MBytes @ 299 MHz, 5.0-5-5-15
                        - 1024 MB PC5300 DDR2-SDRAM - Micron Tech. 8HTF12864AY-667E1
                        - 1024 MB PC5300 DDR2-SDRAM - Micron Tech. 8HTF12864AY-667E1
                        - 512 MB PC5300 DDR2-SDRAM - Micron Tech. 4HTF6464AY-667E1
                        - 512 MB PC5300 DDR2-SDRAM - Micron Tech. 4HTF6464AY-667E1
                        Graphics: NVIDIA nForce 630a - GeForce 7025 [NEC]
                        NVIDIA GeForce 7025, 256 MB SDRAM
                        Drive: ST3360320AS, 351.6 GB, Serial ATA 3Gb/s
                        Drive: ASUS DRW-2014S1, DVD+R DL
                        Drive: MagicISO Virtual DVD-ROM, DVD+R DL
                        Sound: NVIDIA MCP67/68 - HDA Controller
                        Network: NVIDIA MCP67/68 - Ethernet Controller
                        OS: Microsoft Windows 7 Home Premium Build 7601

                        Comment


                        • #13
                          Heb je de geheugentests uitgevoerd?

                          Open opdrachtregel met administratorrechten * Start op in veilige modus *.

                          Comment


                          • #14
                            ja heb ik gedaan geen problemen gevonden

                            Comment


                            • #15
                              Harde schijf getest
                              ook geen problemen

                              Comment

                              Working...
                              X