BSOD issues


  1. Posts : 7
    windows 7
       #1

    BSOD issues


    welp this here is my first time on this site i have been dealing with these issues since w7 was released on top of that my first copy of w7 was defective talk about bad luck I am going to reinstall again i will be waiting eagerly
    thanks in advance n all that jazz
    ps
    dont be to hard on me i just started chemo i try'd to read the "read before posting new thread"
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello !! Welcome to SF !!

    We really need the dump files to analysis BSOD. Didn't mean to be rude follow these instructions https://www.sevenforums.com/crashes-d...tructions.html

    - Captain
      My Computer


  3. Posts : 7
    windows 7
    Thread Starter
       #3

    i will as soon as i buy a new key board i literally destroied my key board LOL
      My Computer


  4. Posts : 7
    windows 7
    Thread Starter
       #4

    maybe the keyboard is the real issue...
      My Computer


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

    Please remove Norton antivirus/Symantec completely, I can see stop codes related to that
    Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    BUGCHECK SUMMARY:
    Code:
    BugCheck 3B, {c0000005, fffff960001176fa, fffff8800932fb90, 0}
    
    Probably caused by : win32k.sys ( win32k!RFONTOBJ::bMakeInactiveHelper+2e )
    
    Followup: MachineOwner
    ---------
    BugCheck 50, {fffff8a80476c008, 0, fffff80002d425d1, 5}
    
    
    Could not read faulting driver name
    Probably caused by : discache.sys ( discache!DisCreateObjectAttributeStore+ec )
    
    Followup: MachineOwner
    ---------
    BugCheck A, {fffffa8004a83090, 2, 0, fffff80002a7868b}
    
    Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+8b )
    
    Followup: MachineOwner
    ---------
    BugCheck 1A, {41284, fffff980082b6001, 3b5e, fffff780c0000000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
    
    Followup: MachineOwner
    ---------
    Regard,

    Tuan
      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 04:19.
Find Us