BLUE SCREEN AFTER HIBERNATE

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by akeremis, Apr 20, 2011.

  1. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    hello to everyone

    i have a well known problem with my desktop pc but i can't find a well known solution so you are my last hope. every time it hibernates i see a blue screen and i have to restart.

    the pc is

    CPU INTEL CORE I5 25000 3.3GHZ 6MB
    MB GIGABYTE PH67A-UD3-B3
    PSU CM SILENT PRO 700W
    MEMORY DDR3 EXCELRAM 6GBKIT 1
    HD WD 1TB WD10EARS 64MB SATA2
    VGA PNY QUADRO VCQ600 1GBLP

    i'll apreciate any help.
    thanks
    View attachment minidumb.txtView attachment RAMMon - SPD Info.rar cpu-z spd tab. cpu-z memory tab.
     
  2. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    sorry for the spam. this is the complete printscreens for the memory slots

    memoryslots3&4. memoryslots1&2.
     
  3. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Kernel Inpage Error 7a - you should have attached the crash dumps from C:\Windows\Minidump.

    Set your memory according to the manufacturer's recommended rates.
     
  4. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    Dump File : 042011-41137-01.dmp
    Crash Time : 20/4/2011 6:56:40 μμ
    Bug Check String : KERNEL_DATA_INPAGE_ERROR
    Bug Check Code : 0x0000007a
    Parameter 1 : 00000000`00000020
    Parameter 2 : ffffffff`c000009d
    Parameter 3 : fffffa80`07e197c8
    Parameter 4 : 00000000`00000000
    Caused By Driver : Ntfs.sys
    Caused By Address : Ntfs.sys+2125
    File Description :
    Company :
    File Version :
    Processor : x64
    Computer Name :
    Full Path : C:\Windows\Minidump\042011-41137-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7600
    Dump File Size : 298.696


    this is the dump file.

    below is a pic from my ram. can you tell if the memory is set according to the maufacturer'e recomended rates? i also checked the bios and noticed that the ram's voltage is at 1.5 v but the ram in the logo says 1.65v. ramfoto.


    in gigabyte's page says that this motherboard has 4 x 1.5V DDR3 DIMM.is it possible that this is the cause of the blue screens?
     
    #4 akeremis, Apr 20, 2011
    Last edited: Apr 20, 2011
  5. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Memory - set it this way:

    Dram frequency - 1600 Mhz
    Timing/CAS Latency - 7-10-10-24
    Voltage - 1.65 v

    To set so, enable the XMP profile.


    What is the max. DDR frequency that the motherboard supports? If it has support for 1600 you should be fine.
     
  6. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    1. 4 x 1.5V DDR3 DIMM sockets supporting up to 32 GB of system memory
      * Due to Windows 32-bit operating system limitation, when more than 4 GB of physical memory is installed, the actual memory size displayed will be less than 4 GB.
    2. Dual channel memory architecture
    3. Support for DDR3 1333/1066/800 MHz memory modules
    4. Support for non-ECC memory modules
    no the motherboard doesn't support 1600 mhz. i guess i have to change the ram or the mobo?
     
  7. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Yes, change the RAM.
     
  8. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    will do. thank you very much.
     
  9. Yahel

    Yahel New Member

    Joined:
    Apr 22, 2011
    Messages:
    20
    Likes Received:
    0
    as you can see in the minidump the error comes from ntfs.sys, that means its error of the file system/hard drive. In combination with KERNEL_DATA_INPAGE_ERROR the most likely is that you have install windows 7 with IDE mode in you BIOS.

    Your Motherboard doesnt support native 1600Mhz, this doesnt limit the speed of your ram, with xmp and the right voltage you can adjust the rams in the correct speed of 1600mhz with no problem.

    1.5v is the minimum set of voltage, again that doesnt limit your current to than value. You can rise the voltage without problem at least at 1.7v. As you can see in the QVL of gigabyte many of the included rams have 1.65v.

    So my suggestion is to format you pc again in ACHI mode.
     
  10. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Even without seeing a few latest crash dumps, I quite agree that this might be bad RAM or bad HDD controller - since it reads:

    KERNEL_DATA_INPAGE_ERROR message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

    But if the HDD controller is faulty, would you expect it to fail in IDE mode and work well in AHCI?


    How can you get the memory at 1600 Mhz if there is no XMP in his bios, the maximum Dram value being 1333Mhz?
     
  11. Yahel

    Yahel New Member

    Joined:
    Apr 22, 2011
    Messages:
    20
    Likes Received:
    0
    i think that gigabyte supports xmp. If it doesnt, what will stop you for raising the Hz?

    In any case, now probably the rams running at 1333Mhz, what it will be the difference with native 1333Mhz rams?

    It think its hard error and ram. Even a Chkdsk (with /f /r switches) will solve the problem. Generally the hibernating is a software problem and rarely hardware.
     
  12. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    7a can be hardware, just as the error states - RAM or HDD controller, and that's why I think it is a good idea to set RAM to its recommended rates. A good idea to check the hdd with chkdsk and testing utilities like HD Tune. But generally when it is the hard disk controller fault, the I/O error status would be C0000185, 0xC000009C, 0xC000016A.


    Not all Gigabyte motherboards support XMP. If it does not support 1600Mhz, it's not possible to run sticks at that frequency. Unless the Dram is overclockable, but overclocking is not a very good idea when blue screens persist.


    If the blue screens occur occasionally and only on wake-up, and with an offset to a 3rd party driver, then yes, I agree with the above.
     
  13. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    thank you all for your interest in my problem. indeed, the blue screens occur occasionally and only on wake up from hibernate mode.

    i tested the ram with memtest for about 7 hours and it found no errors. i also checked the hard disk with disccheck and i'm running the hdtune now.

    what are the /f/r switches? also how can i see if my motherboard supports XMP?

    what exactly do you mean by " with an offset to a third party driver"? i'm not english speaking guy and i don't know what it means.


    i guess that the first thing i have to do is a format and a clear install off windows 7 in ACHI mode. then i have to test the pc with another set of rams (1333MHz, 1,5v) or to change the settings of the current rams. finally, how can i check the hdd for a bad controller?
     
    #13 akeremis, Apr 22, 2011
    Last edited: Apr 22, 2011
  14. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    the latest dump files are
    View attachment dumps.rar

    i also got an answer for an error from microsoft. i don't remember what exactly the error was about but the answer report was
    i uploaded this report because you wrote about hard disk errors.

    again, thank you all for your response.
     
  15. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Test your hard disk:

    (Under windows) HD Tune website

    (From bootable media) HD Diagnostic

    ~~~~~

    XMP - if your mobo doesn't have support for DDR1600, then most likely you don't have XMP in your bios.

    ~~~~~

    If possible, attach your crash dumps (C:\Windows\Minidump).
     
  16. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    these are the latset dump files

     
  17. Yahel

    Yahel New Member

    Joined:
    Apr 22, 2011
    Messages:
    20
    Likes Received:
    0
    Do you have any opened program before hibernate? Maybe your programs cant start again properly after hibernation and cause the BSoD.

    If it was a hardware problem you should have constant problem not occasionally, and not only with hibernation.

    As i said before the voltage and Hz is not a problem ether, your ram runs at 1333Mhz because your motherboard downgrades them, there will be no difference with native 1333Mhz. Im saying that because is no need to spend more money to have a new set of rams.

    Im running a C2Q in Asus P5E3 Deluxe (native 1333Mhz, 1.5v) with Crucial Ballistix 1600Mhz @ 1.75v for three years now
     
  18. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321

    Thanks for he update and for the crash dumps, but again, why did you attach just two? The more the better. Hardware for sure:



    Test the hard drive:

    HD Diagnostic



    Uninstall:

    WIBU-KEY Software Protection System
    WibuKey64.sys Wed Nov 22 07:09:49 2006

    AVG


    CRASH DUMPS

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DMP\042111-38173-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`03244e50
    Debug session time: Thu Apr 21 09:17:19.704 2011 (UTC - 4:00)
    System Uptime: 0 days 8:59:59.625
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa8007d4a770, fffffa8007d4aa50, fffff800033802d0}
    
    Probably caused by : csrss.exe
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8007d4a770, Terminating object
    Arg3: fffffa8007d4aa50, Process image file name
    Arg4: fffff800033802d0, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    
    PROCESS_OBJECT: fffffa8007d4a770
    
    IMAGE_NAME:  csrss.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: csrss
    
    FAULTING_MODULE: 0000000000000000 
    
    PROCESS_NAME:  csrss.exe
    
    EXCEPTION_RECORD:  fffff88006fb5b38 -- (.exr 0xfffff88006fb5b38)
    ExceptionAddress: 00000000779857bd
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 0000000002310fd8
    Attempt to write to address 0000000002310fd8
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000001
    
    EXCEPTION_PARAMETER2:  0000000002310fd8
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af0e0
     0000000002310fd8 
    
    FOLLOWUP_IP: 
    +3238663431356133
    00000000`779857bd ??              ???
    
    FAULTING_IP: 
    +3238663431356133
    00000000`779857bd ??              ???
    
    FAILED_INSTRUCTION_ADDRESS: 
    +3238663431356133
    00000000`779857bd ??              ???
    
    BUGCHECK_STR:  0xF4_C0000005
    
    STACK_TEXT:  
    fffff880`06fb50b8 fffff800`03403f62 : 00000000`000000f4 00000000`00000003 fffffa80`07d4a770 fffffa80`07d4aa50 : nt!KeBugCheckEx
    fffff880`06fb50c0 fffff800`033aba23 : ffffffff`ffffffff fffffa80`082aeb60 fffffa80`07d4a770 fffffa80`07d4a770 : nt!PspCatchCriticalBreak+0x92
    fffff880`06fb5100 fffff800`0333390c : ffffffff`ffffffff 00000000`00000001 fffffa80`07d4a770 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17666
    fffff880`06fb5150 fffff800`03076993 : fffffa80`07d4a770 fffff800`c0000005 ffffe40e`c92e3c81 fffffa80`082aeb60 : nt!NtTerminateProcess+0x20c
    fffff880`06fb51d0 fffff800`03072f30 : fffff800`030b1dbc fffff880`06fb5b38 fffff880`06fb58a0 fffff880`06fb5be0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`06fb5368 fffff800`030b1dbc : fffff880`06fb5b38 fffff880`06fb58a0 fffff880`06fb5be0 000007fe`fce8a300 : nt!KiServiceLinkage
    fffff880`06fb5370 fffff800`03076d82 : fffff880`06fb5b38 00000000`02350000 fffff880`06fb5be0 000007fe`fce8f024 : nt!KiDispatchException+0x53b
    fffff880`06fb5a00 fffff800`030758fa : 00000000`00000001 00000000`02350000 00000000`00000001 fffffa80`08566450 : nt!KiExceptionDispatch+0xc2
    fffff880`06fb5be0 00000000`779857bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`02310fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779857bd
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
    
    BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
    
    Followup: MachineOwner
    ---------
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DMP\042111-29374-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`0324be50
    Debug session time: Thu Apr 21 11:10:17.552 2011 (UTC - 4:00)
    System Uptime: 0 days 1:51:08.473
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {20, ffffffffc000009d, fffffa8007e657c8, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000009d, error status (normally i/o status code)
    Arg3: fffffa8007e657c8, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c000009d
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1
    
    LAST_CONTROL_TRANSFER:  from fffff800030b63fc to fffff8000307e740
    
    STACK_TEXT:  
    fffff880`033087e8 fffff800`030b63fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`07e657c8 : nt!KeBugCheckEx
    fffff880`033087f0 fffff800`03068637 : fffffa80`07e65760 00000000`c000009d 00000000`00000000 fffffa80`07e657f8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
    fffff880`033088b0 fffff800`0305b0b7 : fffffa80`04f1b680 fffffa80`04f1b6d0 fffffa80`05d30840 00000000`00000056 : nt!IopCompletePageWrite+0x57
    fffff880`033088e0 fffff800`03085b9d : fffffa80`04f1b680 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
    fffff880`03308960 fffff800`03081d4b : fffffa80`05ec9de0 fffffa80`06a718d0 fffff880`00000000 fffff880`0102f23f : nt!KiCommitThreadWait+0x3dd
    fffff880`033089f0 fffff800`03018abf : fffffa80`00000002 fffff880`03308ce0 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
    fffff880`03308ca0 fffff800`033217c6 : fffffa80`04f1b680 40ff0004`ff000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
    fffff880`03308d00 fffff800`0305cc26 : fffff880`02f64180 fffffa80`04f1b680 fffff880`02f6efc0 00000008`590015ff : nt!PspSystemThreadStartup+0x5a
    fffff880`03308d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4c5e0
    fffff800`030b63fc cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c5e0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd
    
    FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
    
    BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
    
    Followup: MachineOwner
    ---------
    
    
    
    




    DRIVERS

    Code:
    start             end                 module name
    fffff880`00fa8000 fffff880`00fff000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
    fffff880`02cdd000 fffff880`02d67000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`040cf000 fffff880`040e5000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
    fffff880`00dc4000 fffff880`00dcf000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
    fffff880`03f68000 fffff880`03f70000   AppleCharger AppleCharger.sys Mon Apr 26 23:54:05 2010 (4BD65FDD)
    fffff880`08f75000 fffff880`08f80000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
    fffff880`00c76000 fffff880`00c7f000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00c7f000 fffff880`00ca9000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
    fffff960`008e0000 fffff960`00941000   ATMFD    ATMFD.DLL    unavailable (00000000)
    fffff880`0850f000 fffff880`0853a000   AVGIDSDriver AVGIDSDriver.Sys Wed Mar 30 10:57:08 2011 (4D9344C4)
    fffff880`018f0000 fffff880`018fa000   AVGIDSEH AVGIDSEH.Sys Tue Feb 22 00:23:04 2011 (4D634838)
    fffff880`044c0000 fffff880`044cb000   AVGIDSFilter AVGIDSFilter.Sys Wed Feb 09 23:59:37 2011 (4D5370B9)
    fffff880`03f19000 fffff880`03f68000   avgldx64 avgldx64.sys Thu Jan 06 23:36:39 2011 (4D269857)
    fffff880`0195c000 fffff880`0196b000   avgmfx64 avgmfx64.sys Tue Mar 01 07:25:15 2011 (4D6CE5AB)
    fffff880`018e4000 fffff880`018f0000   avgrkx64 avgrkx64.sys Tue Jan 18 21:31:31 2011 (4D364D03)
    fffff880`02c39000 fffff880`02c98000   avgtdia  avgtdia.sys  Thu Feb 10 00:50:32 2011 (4D537CA8)
    fffff880`01974000 fffff880`0197b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`03f08000 fffff880`03f19000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
    fffff880`080c8000 fffff880`080e6000   bowser   bowser.sys   Wed Feb 23 00:15:06 2011 (4D6497DA)
    fffff960`006c0000 fffff960`006e7000   cdd      cdd.dll      unavailable (00000000)
    fffff880`01932000 fffff880`0195c000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00e35000 fffff880`00ef5000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
    fffff880`018b4000 fffff880`018e4000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00d03000 fffff880`00d61000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`010ea000 fffff880`0115d000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
    fffff880`040bf000 fffff880`040cf000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`044cb000 fffff880`044d4000   cpuz135_x64 cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
    fffff880`059f1000 fffff880`059ff000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`03eea000 fffff880`03f08000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
    fffff880`03edb000 fffff880`03eea000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
    fffff880`0189e000 fffff880`018b4000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`045cd000 fffff880`045ef000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
    fffff880`04400000 fffff880`0440c000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`04417000 fffff880`0442a000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`0440c000 fffff880`04417000   dump_msahci dump_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`0442a000 fffff880`04436000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
    fffff880`10ac7000 fffff880`10bbb000   dxgkrnl  dxgkrnl.sys  Tue Jan 25 23:22:56 2011 (4D3FA1A0)
    fffff880`0fe00000 fffff880`0fe46000   dxgmms1  dxgmms1.sys  Tue Jan 25 23:22:12 2011 (4D3FA174)
    fffff880`01078000 fffff880`0108c000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`0102c000 fffff880`01078000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
    fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`01864000 fffff880`0189e000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
    fffff880`0157f000 fffff880`015c9000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
    fffff880`040b2000 fffff880`040bf000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
    fffff800`035eb000 fffff800`03634000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
    fffff880`10bbb000 fffff880`10bdf000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
    fffff880`10bdf000 fffff880`10bf0000   HECIx64  HECIx64.sys  Tue Sep 21 12:59:04 2010 (4C98E458)
    fffff880`08f80000 fffff880`08f8c000   hiber_dumpata hiber_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`08f97000 fffff880`08faa000   hiber_dumpfve hiber_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`08f8c000 fffff880`08f97000   hiber_msahci hiber_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`059b4000 fffff880`059cd000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
    fffff880`059cd000 fffff880`059d5080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
    fffff880`059a6000 fffff880`059b4000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
    fffff880`08000000 fffff880`080c8000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
    fffff880`015e3000 fffff880`015ec000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
    fffff880`03f96000 fffff880`03fac000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    fffff880`0419a000 fffff880`041a9000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`059d6000 fffff880`059e4000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff800`00bd2000 fffff800`00bdc000   kdcom    kdcom.dll    Sat Feb 05 07:21:45 2011 (4D4D40D9)
    fffff880`041ba000 fffff880`041fd000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
    fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
    fffff880`01554000 fffff880`0157f000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
    fffff880`045ef000 fffff880`045f4200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
    fffff880`04488000 fffff880`0449d000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`04444000 fffff880`04467000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
    fffff880`00cab000 fffff880`00cef000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
    fffff880`04436000 fffff880`04444000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
    fffff880`041a9000 fffff880`041b8000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`059e4000 fffff880`059f1000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff880`00c5c000 fffff880`00c76000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`0816b000 fffff880`08183000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
    fffff880`08183000 fffff880`081b0000   mrxsmb   mrxsmb.sys   Wed Feb 23 00:15:23 2011 (4D6497EB)
    fffff880`081b0000 fffff880`081fe000   mrxsmb10 mrxsmb10.sys Wed Feb 23 00:15:14 2011 (4D6497E2)
    fffff880`0449d000 fffff880`044c0000   mrxsmb20 mrxsmb20.sys Wed Feb 23 00:15:13 2011 (4D6497E1)
    fffff880`00da9000 fffff880`00db4000   msahci   msahci.sys   Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`019d9000 fffff880`019e4000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00e09000 fffff880`00e13000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`0108c000 fffff880`010ea000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
    fffff880`03ed0000 fffff880`03edb000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
    fffff880`015d1000 fffff880`015e3000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`01402000 fffff880`014f4000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`04109000 fffff880`04115000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
    fffff880`08140000 fffff880`08153000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
    fffff880`04115000 fffff880`04144000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`04552000 fffff880`04567000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
    fffff880`02dac000 fffff880`02dbb000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`02c98000 fffff880`02cdd000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
    fffff880`014f4000 fffff880`01554000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
    fffff880`05862000 fffff880`0597c000   netr28ux netr28ux.sys Wed May 26 06:22:27 2010 (4BFCF663)
    fffff880`019e4000 fffff880`019f5000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`03ec4000 fffff880`03ed0000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
    fffff800`0300e000 fffff800`035eb000   nt       ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
    fffff880`01257000 fffff880`013fa000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
    fffff880`0196b000 fffff880`01974000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`0453a000 fffff880`04552000   nusb3hub nusb3hub.sys Mon Jul 26 20:45:44 2010 (4C4E2C38)
    fffff880`03fac000 fffff880`03fdc000   nusb3xhc nusb3xhc.sys Mon Jul 26 20:45:44 2010 (4C4E2C38)
    fffff880`10ac5000 fffff880`10ac6180   nvBridge nvBridge.kmd Fri Mar 18 17:25:53 2011 (4D83CDE1)
    fffff880`04567000 fffff880`04590000   nvhda64v nvhda64v.sys Thu Nov 11 18:10:36 2010 (4CDC77EC)
    fffff880`0fe68000 fffff880`10ac4a00   nvlddmkm nvlddmkm.sys Fri Mar 18 17:27:34 2011 (4D83CE46)
    fffff880`080ed000 fffff880`08140000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
    fffff880`02d70000 fffff880`02d96000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
    fffff880`00e20000 fffff880`00e35000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00d61000 fffff880`00d94000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00db4000 fffff880`00dc4000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`08404000 fffff880`084aa000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
    fffff880`04590000 fffff880`045cd000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00cef000 fffff880`00d03000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`040e5000 fffff880`04109000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`04144000 fffff880`0415f000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
    fffff880`0415f000 fffff880`04180000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
    fffff880`04180000 fffff880`0419a000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
    fffff880`03e73000 fffff880`03ec4000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
    fffff880`019be000 fffff880`019c7000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`019c7000 fffff880`019d0000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`019d0000 fffff880`019d9000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`011a9000 fffff880`011e3000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
    fffff880`08153000 fffff880`0816b000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`0404f000 fffff880`040a6000   Rt64win7 Rt64win7.sys Fri Sep 03 01:58:32 2010 (4C808E88)
    fffff880`05606000 fffff880`05861d80   RTKVHD64 RTKVHD64.sys Fri Sep 03 04:02:27 2010 (4C80AB93)
    fffff880`02c14000 fffff880`02c2e000   SCDEmu   SCDEmu.SYS   Sun Nov 08 22:27:29 2009 (4AF78C21)
    fffff880`084aa000 fffff880`084b5000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`040a6000 fffff880`040b2000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`02dbb000 fffff880`02dd8000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`015c9000 fffff880`015d1000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`08e6f000 fffff880`08f04000   srv      srv.sys      Wed Feb 23 00:16:24 2011 (4D649828)
    fffff880`0853a000 fffff880`085a1000   srv2     srv2.sys     Wed Feb 23 00:15:59 2011 (4D64980F)
    fffff880`084b5000 fffff880`084e2000   srvnet   srvnet.sys   Wed Feb 23 00:15:49 2011 (4D649805)
    fffff880`041b8000 fffff880`041b9480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
    fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
    fffff880`084e2000 fffff880`084f4000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
    fffff880`0181e000 fffff880`0182b000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
    fffff880`01800000 fffff880`0181e000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
    fffff880`02c00000 fffff880`02c14000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
    fffff960`00440000 fffff960`0044a000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff880`03f70000 fffff880`03f96000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
    fffff880`04000000 fffff880`04012000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
    fffff880`05989000 fffff880`059a6000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
    fffff880`0fe57000 fffff880`0fe58f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
    fffff880`0fe46000 fffff880`0fe57000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
    fffff880`044e0000 fffff880`0453a000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
    fffff880`03e00000 fffff880`03e56000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
    fffff880`00e13000 fffff880`00e20000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`0197b000 fffff880`01989000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`01989000 fffff880`019ae000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`00d94000 fffff880`00da9000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
    fffff880`0115d000 fffff880`011a9000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
    fffff880`0597c000 fffff880`05989000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
    fffff880`02d96000 fffff880`02dac000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
    fffff880`02dd8000 fffff880`02df3000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
    fffff880`019ae000 fffff880`019be000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`00ef5000 fffff880`00f99000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00f99000 fffff880`00fa8000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`02d67000 fffff880`02d70000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`084f4000 fffff880`0850e200   WibuKey64 WibuKey64.sys Wed Nov 22 07:09:49 2006 (45643E0D)
    fffff960`000b0000 fffff960`003c2000   win32k   win32k.sys   unavailable (00000000)
    fffff880`00e00000 fffff880`00e09000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`04467000 fffff880`04488000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
    
    Unloaded modules:
    fffff880`08f04000 fffff880`08f75000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00071000
    fffff880`018fa000 fffff880`01908000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`01908000 fffff880`01914000   dump_pciidex
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`01914000 fffff880`0191f000   dump_msahci.
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000B000
    fffff880`0191f000 fffff880`01932000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    
    
     
  19. akeremis

    akeremis New Member

    Joined:
    Apr 20, 2011
    Messages:
    28
    Likes Received:
    0
    i have only this and the other two dmps i uploaded earlier because the guys from the service erased them:(. yesterday i had no crashes.


    i unistalled avg yesterday and replaced it.
    i will uninstall and the WibuKey64.sys.
    i will try another hdd to see if the problem remains and finally i will try another set of rams.
    i will post again when the hd diagnostic finishes.

    i've seen it crashing with or without a running programm t. i don't believe that the ram is broken or something like that but it maybe not working 100% or just not good as the recomended ones from gigabyte.

    thank you all for your support. i'll try your advices and i will report again
     
    #19 akeremis, Apr 23, 2011
    Last edited: Apr 23, 2011
  20. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Good idea, try another HDD and RAM, keep us updated.
     

Share This Page

Loading...