Kernel Error, might be harddrive problem

Page 2 of 2 FirstFirst 12

  1. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #11

    DeanP said:
    nTune doesn't have compatibility with Windows 7 - only Vista and XP. Try this - NVIDIA DRIVERS 6.05

    If you don't like it - let me know.

    These dumps are old - upload the latest 5 from :\Windows\Minidump

    thanks, I'll give that a go.

    Also I mention already, why isn't it logging the dumps. The last 3 BSOD crash I had, none of it been logged into mini dumps. latest is 03/01/2011

    Here screenshot.




    Also i did the driver verifier thing, and had about 2 BSOD and none of them have been logged either.
      My Computer


  2. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #12

    DeanP said:
    nTune doesn't have compatibility with Windows 7 - only Vista and XP. Try this - NVIDIA DRIVERS 6.05

    If you don't like it - let me know.
    [/B]
    This is similar like ntune, also I tried to change the settings and save a profile settings too. After restart, it goes back to it defualt settings.
    Also, the settings are not right when I set it. Set manual control to 40%, it show on the gpu gadget as 59% ?
      My Computer


  3. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #13

    No BSOD since last post. But will get back here if one occurs.

    I got this update, important update on Windows Update.

    That I need to install ATK0110 ACPI Utility



    I have not uninstalled any other drivers beside the NVIDIA DRIVERS 6.0.

    Last time I checked, I installed that a while ago. Reinstall it again from official ASUS P5QL-E Site
      My Computer


  4. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #14

    I found out why my mini dumps weren't logging, apparently my pagefile.sys was full. no more mini dumps were created.
    I thought it would keep creating mini dumps as long there's free space on the hdd.

    so I did some googling, and found a link to a dump configurator.
    original thread

    tweak it.restarted it, cleared old mini and memory dumps. did the driver verifier. only two BSOD come up which they the same thing.

    It the Trusteer Rapport creating the BSOD. but I do not know if this is the main cause from my previous BSOD.
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\John\Desktop\Windows_NT6_BSOD_jcgriff2\022811-29733-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Debugging Tools\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304ae90
    Debug session time: Mon Feb 28 14:14:11.008 2011 (UTC + 0:00)
    System Uptime: 0 days 0:01:27.928
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {226, fffff88001934aa0, fffff9801ce1eee0, 0}
    
    Unable to load image \SystemRoot\System32\Drivers\RapportKE64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for RapportKE64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RapportKE64.sys
    Probably caused by : RapportKE64.sys ( RapportKE64+6aa0 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
    	or someone forgot to return STATUS_PENDING.
    Arg2: fffff88001934aa0, The address in the driver's code where the error was detected.
    Arg3: fffff9801ce1eee0, IRP address.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_226
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226
    
    FAULTING_IP: 
    RapportKE64+6aa0
    fffff880`01934aa0 4889542410      mov     qword ptr [rsp+10h],rdx
    
    FOLLOWUP_IP: 
    RapportKE64+6aa0
    fffff880`01934aa0 4889542410      mov     qword ptr [rsp+10h],rdx
    
    IRP_ADDRESS:  fffff9801ce1eee0
    
    DEVICE_OBJECT: fffffa80087b5e40
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  RapportService
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000330c3dc to fffff80002e85640
    
    STACK_TEXT:  
    fffff880`0867f4e8 fffff800`0330c3dc : 00000000`000000c9 00000000`00000226 fffff880`01934aa0 fffff980`1ce1eee0 : nt!KeBugCheckEx
    fffff880`0867f4f0 fffff800`0331647a : fffff800`0330a9f0 fffff880`01934aa0 fffff980`1ce1eee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0867f530 fffff800`03317483 : 00000000`00000226 fffffa80`0a3aed18 fffff980`1ce1eee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`0867f580 fffff800`0332279c : 00000000`00000000 fffffa80`0a3aec60 fffffa80`0a3aed18 fffffa80`0a4159d0 : nt!VfErrorReport1+0x63
    fffff880`0867f620 fffff800`03322b63 : fffffa80`0a3aec60 00000000`00000002 fffffa80`087b5e40 fffff800`033152a7 : nt!IovpCallDriver2+0x1bc
    fffff880`0867f680 fffff800`03328c2e : fffffa80`087b5e40 fffff980`1ce1eee0 00000000`00000002 fffffa80`087b5e40 : nt!VfAfterCallDriver+0x353
    fffff880`0867f6d0 fffff800`03183495 : 00000000`00000025 fffffa80`0a980778 fffffa80`0a71c9b0 fffffa80`0a3aec60 : nt!IovCallDriver+0x57e
    fffff880`0867f730 fffff800`0317fd38 : fffffa80`087b5e40 00000000`00000000 fffffa80`0a9805c0 fffff6fc`00000001 : nt!IopParseDevice+0x5a5
    fffff880`0867f8c0 fffff800`03180f56 : 00000000`00000000 fffffa80`0a9805c0 fffff680`003b7968 fffffa80`0765e750 : nt!ObpLookupObjectName+0x588
    fffff880`0867f9b0 fffff800`0318285c : fffffa80`0a3c0ec8 00000000`00000000 fffffa80`0a3bc301 ffffffff`ffffffff : nt!ObOpenObjectByName+0x306
    fffff880`0867fa80 fffff800`0318d478 : 00000000`0008e2e8 fffff8a0`c0100080 00000000`0008ebb0 00000000`0008e300 : nt!IopCreateFile+0x2bc
    fffff880`0867fb20 fffff800`02e848d3 : fffffa80`0a3c0b30 0000007f`ffffffff fffffa80`0a3bc330 00000980`00000000 : nt!NtCreateFile+0x78
    fffff880`0867fbb0 00000000`76f3186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008e278 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f3186a
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  RapportKE64+6aa0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: RapportKE64
    
    IMAGE_NAME:  RapportKE64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d5d775f
    
    FAILURE_BUCKET_ID:  X64_0xc9_226_VRF_RapportKE64+6aa0
    
    BUCKET_ID:  X64_0xc9_226_VRF_RapportKE64+6aa0
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #15

    JoHn87 said:
    I found out why my mini dumps weren't logging, apparently my pagefile.sys was full. no more mini dumps were created.
    I thought it would keep creating mini dumps as long there's free space on the hdd.

    so I did some googling, and found a link to a dump configurator.
    original thread

    tweak it.restarted it, cleared old mini and memory dumps. did the driver verifier. only two BSOD come up which they the same thing.

    It the Trusteer Rapport creating the BSOD. but I do not know if this is the main cause from my previous BSOD.
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\John\Desktop\Windows_NT6_BSOD_jcgriff2\022811-29733-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Debugging Tools\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304ae90
    Debug session time: Mon Feb 28 14:14:11.008 2011 (UTC + 0:00)
    System Uptime: 0 days 0:01:27.928
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {226, fffff88001934aa0, fffff9801ce1eee0, 0}
    
    Unable to load image \SystemRoot\System32\Drivers\RapportKE64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for RapportKE64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RapportKE64.sys
    Probably caused by : RapportKE64.sys ( RapportKE64+6aa0 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
        or someone forgot to return STATUS_PENDING.
    Arg2: fffff88001934aa0, The address in the driver's code where the error was detected.
    Arg3: fffff9801ce1eee0, IRP address.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_226
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226
    
    FAULTING_IP: 
    RapportKE64+6aa0
    fffff880`01934aa0 4889542410      mov     qword ptr [rsp+10h],rdx
    
    FOLLOWUP_IP: 
    RapportKE64+6aa0
    fffff880`01934aa0 4889542410      mov     qword ptr [rsp+10h],rdx
    
    IRP_ADDRESS:  fffff9801ce1eee0
    
    DEVICE_OBJECT: fffffa80087b5e40
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  RapportService
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000330c3dc to fffff80002e85640
    
    STACK_TEXT:  
    fffff880`0867f4e8 fffff800`0330c3dc : 00000000`000000c9 00000000`00000226 fffff880`01934aa0 fffff980`1ce1eee0 : nt!KeBugCheckEx
    fffff880`0867f4f0 fffff800`0331647a : fffff800`0330a9f0 fffff880`01934aa0 fffff980`1ce1eee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0867f530 fffff800`03317483 : 00000000`00000226 fffffa80`0a3aed18 fffff980`1ce1eee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`0867f580 fffff800`0332279c : 00000000`00000000 fffffa80`0a3aec60 fffffa80`0a3aed18 fffffa80`0a4159d0 : nt!VfErrorReport1+0x63
    fffff880`0867f620 fffff800`03322b63 : fffffa80`0a3aec60 00000000`00000002 fffffa80`087b5e40 fffff800`033152a7 : nt!IovpCallDriver2+0x1bc
    fffff880`0867f680 fffff800`03328c2e : fffffa80`087b5e40 fffff980`1ce1eee0 00000000`00000002 fffffa80`087b5e40 : nt!VfAfterCallDriver+0x353
    fffff880`0867f6d0 fffff800`03183495 : 00000000`00000025 fffffa80`0a980778 fffffa80`0a71c9b0 fffffa80`0a3aec60 : nt!IovCallDriver+0x57e
    fffff880`0867f730 fffff800`0317fd38 : fffffa80`087b5e40 00000000`00000000 fffffa80`0a9805c0 fffff6fc`00000001 : nt!IopParseDevice+0x5a5
    fffff880`0867f8c0 fffff800`03180f56 : 00000000`00000000 fffffa80`0a9805c0 fffff680`003b7968 fffffa80`0765e750 : nt!ObpLookupObjectName+0x588
    fffff880`0867f9b0 fffff800`0318285c : fffffa80`0a3c0ec8 00000000`00000000 fffffa80`0a3bc301 ffffffff`ffffffff : nt!ObOpenObjectByName+0x306
    fffff880`0867fa80 fffff800`0318d478 : 00000000`0008e2e8 fffff8a0`c0100080 00000000`0008ebb0 00000000`0008e300 : nt!IopCreateFile+0x2bc
    fffff880`0867fb20 fffff800`02e848d3 : fffffa80`0a3c0b30 0000007f`ffffffff fffffa80`0a3bc330 00000980`00000000 : nt!NtCreateFile+0x78
    fffff880`0867fbb0 00000000`76f3186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008e278 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f3186a
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  RapportKE64+6aa0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: RapportKE64
    
    IMAGE_NAME:  RapportKE64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d5d775f
    
    FAILURE_BUCKET_ID:  X64_0xc9_226_VRF_RapportKE64+6aa0
    
    BUCKET_ID:  X64_0xc9_226_VRF_RapportKE64+6aa0
    
    Followup: MachineOwner
    ---------
    Latest BSODs caused by RapportKE64.sys which is part of Trusteer Rapport
    Trusteer Rapport is a security program that is known to cause BSOD's on some Windows 7 systems. You should completely uninstall it.
      My Computer


  6. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #16

    yowanvista said:
    Latest BSODs caused by RapportKE64.sys which is part of Trusteer Rapport
    Trusteer Rapport is a security program that is known to cause BSOD's on some Windows 7 systems. You should completely uninstall it.
    OK, I will do.

    Can I re-installed EVGA Precision back on? as I cant find a better alternative software to control my gpu fan.
      My Computer


  7. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #17

    JoHn87 said:
    yowanvista said:
    Latest BSODs caused by RapportKE64.sys which is part of Trusteer Rapport
    Trusteer Rapport is a security program that is known to cause BSOD's on some Windows 7 systems. You should completely uninstall it.
    OK, I will do.

    Can I re-installed EVGA Precision back on? as I cant find a better alternative software to control my gpu fan.
    Install it if you don't get anymore BSODs after the removal of Trusteer Rapport
      My Computer


  8. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #18

    yowanvista said:
    Install it if you don't get anymore BSODs after the removal of Trusteer Rapport
    OK, will report back if I get BSOD.

    + rep ya all who help me here. (yowanvista, DeanP, zigzag3143)
      My Computer


  9. Posts : 68
    Windows 7 Pro x64
    Thread Starter
       #19

    Update:
    Things are back to normal.
    Installed EVGA Precision back on.
    Clean my computer case, spray switch cleaner on the connectors for HDD, power/sata cables. which solved my HDD problem, which was a different problem.

    No BSOD since last post
      My Computer


  10. Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       #20

    Sounds good. However, if BSOD occurs again, then remove EVGA Precision.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 20:49.
Find Us