BSOD need help on analysis thank you


  1. Posts : 4
    windows 7 64bit
       #1

    BSOD need help on analysis thank you


    need your help sirs. very much appreciated
      My Computer


  2. Posts : 4
    windows 7 64bit
    Thread Starter
       #2

    newer minidump files. thanks
      My Computer


  3. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #3

    STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

    Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

    Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
    STOP 0x0000001A: MEMORY_MANAGEMENT

    Usual causes: Device driver, memory, kernel
    There is an exception code ffffffc000005, which suggest memory corruption. Please download third party called memtestx86, burn it to CD using http://isorecorder.alexfeinman.com/W7.htm, and let it run for at least 7 passes.

    Run system file check:
    SFC /SCANNOW Command - System File Checker

    Do you overclock anything?

    Code:
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
    
    Followup: MachineOwner
    ---------
    BugCheck 1E, {ffffffffc0000005, fffff80002d9885b, 0, ffffffffffffffff}
    
    Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceClose+48 )
    
    Followup: MachineOwner
    ---------
    BugCheck A, {fffffa7fffffffd0, 2, 1, fffff80002ad41e3}
    
    Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+4d3 )
    
    Followup: MachineOwner
    ---------
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
    
    Followup: MachineOwner
    ---------
    BugCheck 1A, {5002, fffff780c0000000, 724b, ff6e41fffffffe}
    
    Probably caused by : udfs.sys ( udfs!UdfCommonRead+b1b )
    
    Followup: MachineOwner
    ---------
    BugCheck 3B, {c0000005, fffff80002bbd90d, fffff88006c2d870, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
    
    Followup: MachineOwner
    ---------
    Run check disk too:
    Disk Check

    That's some generic things to try

    Let us know if you need help

    Tuan
      My Computer


  4. Posts : 4
    windows 7 64bit
    Thread Starter
       #4

    thank you for your quick reply. does memtestx86 run on 64bit windows 7? i have 2-2gb kingston ram which was newly bought this week, since i thought it could might as well be my old ram.
    already removed my video card since it was showing "display driver stopped responding and has recovered"
    its starting to look like my motherboard's busted. it was newly purchased last march. could my processor and or hardisk have something to do with these events?

    no overclocking that i know of. i will try out your suggestions thank you.
      My Computer


  5. Posts : 140
    Windows 7 Home Premium 64bit
       #5

    You run it outside of windows. You restart and either boot it from a disc or usb.
      My Computer


  6. Posts : 4
    windows 7 64bit
    Thread Starter
       #6

    Davidxtux said:
    You run it outside of windows. You restart and either boot it from a disc or usb.
    would it work on a 64bit windows? thanks
      My Computer


  7. Posts : 140
    Windows 7 Home Premium 64bit
       #7

    It doesn't matter which version of windows you are using. You boot it from either disc or usb before windows has loaded.

    Burn it to disc or copy to usb. Make sure bios settings are set to boot from either disc or usb before hdd. After restart press f8 and select boot from disc or usb then run it from there.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:26.
Find Us