More BSOD issues

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by JamesJR, Aug 23, 2010.

  1. JamesJR

    JamesJR New Member

    Joined:
    Aug 23, 2010
    Messages:
    14
    Likes Received:
    0
    One of several issues im facing is my BSOD issue. I have replaced memory but still getting the bsod. I'm at my witts end, please help.

    os:win7 pro (64-bit)
    cpu:intel core 2 duo e6300
    mem:4gb

    I'm also running XP w/ split partition, which is running flawlessly. I've had win7 for awhile now and have yet to get it to run reasonably well.
     

    Attached Files:

  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Code:
    061710-23462-01.dmp
    BugCheck CA, {b, fffffa8002168a20, 1, 0}
    Probably caused by : pci.sys
    PNP_DETECTED_FATAL_ERROR (ca)
    PnP encountered a severe error, either as a result of a problem in a driver or a problem in PnP itself. 
    MODULE_NAME: pci
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  X64_0xCA_B_IMAGE_pci.sys
    
    The PNP_DETECTED_FATAL_ERROR bug check has a value of 0x000000CA. This indicates that the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver. Check your p&p devices.




    Code:
    061910-15974-01.dmp
    BugCheck CA, {b, fffffa8001e1c8d0, 1, 0}
    Probably caused by : pci.sys
    PNP_DETECTED_FATAL_ERROR (ca)
    PnP encountered a severe error, either as a result of a problem in a driver or a problem in PnP itself.
    MODULE_NAME: pci
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  X64_0xCA_B_IMAGE_pci.sys
    
    The PNP_DETECTED_FATAL_ERROR bug check has a value of 0x000000CA. This indicates that the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver. Check your p&p devices.






    Code:
    082010-20202-01.dmp
    BugCheck 7F, {8, 80050033, 6f8, fffff80002a9198e}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault).
    MODULE_NAME: nt
    PROCESS_NAME:  svchost.exe
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    support.microsoft.com/kb/842465

    This problem occurs if one or more of the processors in the computer:
    • Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
    • Are damaged or defective.
    • Are operating outside their specified ranges for temperature, power, or other conditions.





    Code:
    082010-21278-01.dmp
    BugCheck 1000007E, {ffffffffc0000005, fffff80002aa44a1, fffff88002fee0e8, fffff88002fed950}
    Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    PROCESS_NAME:  KHALMNPR.exe
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    MODULE_NAME: nt
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+15
    A hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG.  This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG.  This will let us see why this breakpoint is happening.
    khalmnpr.exe - Logitech Mouse Utility, a process installed alongside Logitech mice which allows for advanced configuration and diagnostics of their range of multimedia products. This program is a non-essential process, but should not be terminated unless suspected to be causing problems.


    Run memtest86 overnight. If turns out memory related, run your system with 1 stick of ram, then replace it with the other sticks you have, until you identify which one causes the problem.




    Code:
    082310-21949-01.dmp
    BugCheck 24, {1904fb, fffff88006dec538, fffff88006debda0, fffff80002adbc9c}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireFcbWithPaging+13b )
    NTFS_FILE_SYSTEM (24)
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    MODULE_NAME: Ntfs
    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireFcbWithPaging+13b
    
    NTFS_FILE_SYSTEM (24) <- triggered by the Ntfs.sys file which is a driver that enables a PC to read and write a hard drive formatted with the NTFS file system. How to solve it:

    - from the os or from the startup repair (with 7 dvd in drive) -> command line, type chkdsk /r and wait for the operation to complete.



    ~~~~~~


    Your drivers are up to date enough, but you may want to update the following if newer versions are available:


    ax88772.sys Wed Jun 10 05:18:09 2009
    ASIX AX88772/AX88772A Network Driver - USB2.0 Fast Ethernet Adapter - ASIX Electronics Corp.



    Pay some attention to these:

    atikmdag.sys Fri Apr 24 13:51:57 2009
    ATI Radeon Kernel Mode driver - update if you actually have an ATI card.



    dump_nvstor.sys Wed May 20 09:45:37 2009
    nvstor.sys Wed May 20 09:45:37 2009
    NVIDIA® nForce(TM) Sata Performance Driver - NVIDIA nForce(TM) SATA Driver - NVIDIA Corporation - update if you actually have NVIDIA hardware and if newer versions for these are available. Otherwise you shouldn't store them in your system.
     
    #2 cybercore, Sep 4, 2010
    Last edited: Sep 4, 2010
  3. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Update your Creative drivers.

    Uninstall AVG in safe mode using this tool found here, then install MSE in normal mode:

    AV Uninstallers - Windows 7 Forums

    Follow Cybercore's post too.

    When done with everything, if crashes persist, then please post a new dump so we can take it from there.
     

Share This Page

Loading...