BSOD after few hours of stop


  1. Posts : 6
    Windows 7
       #1

    BSOD after few hours of stop


    Hi all, first post here for a help to resolve this problem:
    everytime i boot the pc after a stop (of 6 hours or more) i have this blue screen before windows start, if i reboot all goes right until another stop of 5 or 6 hours.
    Yesterday i have changed my Mother Board (AsRock P55 Pro) with Gigabyte G55A-UD7 and i have installed Windows 7 64 thinking that this could help but, incredible, same error.

    This is the message i have:

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.
    The problem seems to be caused by the following file: win32k.sys
    UNEXPECTED_KERNEL_MODE_TRAP
    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:
    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.
    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.
    Technical Information:
    *** STOP: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8,
    0xfffff96000127792)
    *** win32k.sys - Address 0xfffff96000127792 base at 0xfffff96000080000 DateStamp
    0x4a5bc5e0

    Can you help me to understand the problem?

    P.S.: Sorry for my bad english
      My Computer


  2. Posts : 6
    Windows 7
    Thread Starter
       #2

    here the link to my, Windows7_BSOD_jcgriff2, hope it can help

    Hotfile.com: One click file hosting: Windows7_BSOD_jcgriff2.zip
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    fringuello said:
    here the link to my, Windows7_BSOD_jcgriff2, hope it can help

    Hotfile.com: One click file hosting: Windows7_BSOD_jcgriff2.zip
    Having problems downloading from hotfile. Please upload it here using the attachment icon on the reply form. It is shaped like a paperclip

    ken


    EDIT: BTW that bug check is Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
      My Computer


  4. Posts : 6
    Windows 7
    Thread Starter
       #4

    ...and i did a registration too to hotfile ...sorry, don't saw it,
    here the attachment
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    fringuello said:
    ...and i did a registration too to hotfile ...sorry, don't saw it,
    here the attachment

    These two are fairly straight forward. Memory corruption.

    To verify this and test your memory Please:

    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.

    Let us know if you need assistance with this

    Ken


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\072310-16816-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50
    Debug session time: Fri Jul 23 01:31:40.599 2010 (GMT-4)
    System Uptime: 0 days 0:00:17.551
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff96000127792}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff96000127792
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002c80469 to fffff80002c80f00
    
    STACK_TEXT:  
    fffff880`02f6ade8 fffff800`02c80469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02f6adf0 fffff800`02c7e932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02f6af30 fffff960`00127792 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!ResStrCmp+0xa
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
    4 errors : !win32k (fffff9600012718f-fffff96000127c8f)
    fffff96000127180  7d  00  33  75  12  66  41  83  7d  02  32  75  0a  49  83 *45 }.3u.fA.}.2u.I.E
    ...
    fffff96000127280  24  3c  eb  82  66  83  ff  2a  75  1f  45  8b  07  49  83 *47 $<..f..*u.E..I.G
    ...
    fffff96000127400  83  3d  11  2b  23  00  2a  75  14  b9  3f  00  00  00  4c *0b .=.+#.*u..?...L.
    ...
    fffff96000127c80  8b  cc  e8  c5  14  02  00  40  8a  d7  49  8b  cc  ff  15 *cd .......@..I.....
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  STRIDE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    Followup: memory_corruption
    ---------
      My Computer


  6. Posts : 6
    Windows 7
    Thread Starter
       #6

    i have Memtest86 bootable, i'll try it tomorrow, what do you expect to see with it?
      My Computer


  7. Posts : 6
    Windows 7
    Thread Starter
       #7

    another 2 BSOD with different description, here the new Windows7_BSOD_jcgriff2
      My Computer


  8. Posts : 6
    Windows 7
    Thread Starter
       #8

    i found the problem: a 2gb module of ram! the memtest86 didn't be usefull! the test (for 8 hour) was ok, then i tried to boot with one module of ram (1/4) and all goes right, i tried all the modules and i found the bad one, tnx zigzag
      My Computer


  9. Posts : 13,354
    Windows 7 Professional x64
       #9

    Thanks for reporting back. Glad you got it figured out.

    Interesting that Memtest failed. It is usually pretty reliable.
      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 05:46.
Find Us