Random BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by beasteh, Sep 23, 2010.

  1. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
  2. beasteh

    beasteh New Member

    Joined:
    Sep 23, 2010
    Messages:
    24
    Likes Received:
    0
  3. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    You've never installed it properly yet because the driver is actually from 4/26/2010 (I'm looking at it now) and your faulty version in crashes is from 4/22/2010.

    Simple run the .exe then copy the 2 sys files from the 64 bit extracted folder. Paste them over the ones at C:\Windows\System32\drivers and reboot.
     
  4. beasteh

    beasteh New Member

    Joined:
    Sep 23, 2010
    Messages:
    24
    Likes Received:
    0
    Firstly I definitly have installed it correctly 3 times. Secondly I followed your advice to the letter just to make sure. After reboot the computer BSOD 3 times.

    Just to confirm I have uploaded screens of the driver version date. Imageshack - driver.jpg

    Many thanks.
     

    Attached Files:

  5. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Those 2 crashes were an NTFS filesystem one and another caused by a Microsoft Windows 7 driver (which is 100% not a faulty driver).

    Your RAM is definitely messed up and perhaps, also the hard drive.

    If you are looking to get a refund or replacement machine, that's what you should do. You could replace components but you really shouldn't have the headache of it.

    Refund/replacement is definitely the suggestion.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI00.796\100310-25084-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50
    Debug session time: Sun Oct  3 08:37:53.521 2010 (UTC - 4:00)
    System Uptime: 0 days 0:01:50.536
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff8800333f348, fffff8800333ebb0, fffff88001255494}
    
    Probably caused by : Ntfs.sys ( Ntfs!memmove+204 )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff8800333f348
    Arg3: fffff8800333ebb0
    Arg4: fffff88001255494
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff8800333f348 -- (.exr 0xfffff8800333f348)
    ExceptionAddress: fffff88001255494 (Ntfs!memmove+0x0000000000000204)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff8800333ebb0 -- (.cxr 0xfffff8800333ebb0)
    rax=fffff8a004e5be80 rbx=0000000000000000 rcx=fffffa80096e3080
    rdx=fefffdfff7baf440 rsi=000000000e4e6a45 rdi=000000000e4ec1f7
    rip=fffff88001255494 rsp=fffff8800333f588 rbp=fffff800030185a0
     r8=0000000000000008  r9=0000000000000001 r10=fffff80003002888
    r11=fffffa80096e3080 r12=fffffa8008cfe1e0 r13=fffffa8006b2b180
    r14=0000000000000001 r15=fffffa80096e307c
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
    Ntfs!memmove+0x204:
    fffff880`01255494 488b040a        mov     rax,qword ptr [rdx+rcx] ds:002b:fefff880`012924c0=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ab0e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    Ntfs!memmove+204
    fffff880`01255494 488b040a        mov     rax,qword ptr [rdx+rcx]
    
    FAULTING_IP: 
    Ntfs!memmove+204
    fffff880`01255494 488b040a        mov     rax,qword ptr [rdx+rcx]
    
    BUGCHECK_STR:  0x24
    
    LAST_CONTROL_TRANSFER:  from fffff880012e139d to fffff88001255494
    
    STACK_TEXT:  
    fffff880`0333f588 fffff880`012e139d : 00000000`00000000 00000000`00000000 00000000`0e4e6a45 00000000`000007ff : Ntfs!memmove+0x204
    fffff880`0333f590 fffff880`012e36fb : fffff880`0333fab0 fffffa80`06b2b180 00000000`00000000 fffff880`0333fc00 : Ntfs!NtfsCheckpointVolume+0x6ed
    fffff880`0333f990 fffff880`012e38c7 : fffff880`0333fab0 fffffa80`06b2b180 fffffa80`06b2b188 fffffa80`066f4188 : Ntfs!NtfsCheckpointAllVolumesWorker+0x4b
    fffff880`0333f9e0 fffff880`012e2948 : fffff880`0333fab0 00000000`00000000 fffff880`012e36b0 fffff880`0333fcb8 : Ntfs!NtfsForEachVcb+0x167
    fffff880`0333fa80 fffff800`02e80961 : fffff880`05172500 fffff880`05249601 fffff800`03018500 00000000`00000000 : Ntfs!NtfsCheckpointAllVolumes+0xb8
    fffff880`0333fcb0 fffff800`03117c06 : 00000000`00000000 fffffa80`0553db60 00000000`00000080 fffffa80`0550d040 : nt!ExpWorkerThread+0x111
    fffff880`0333fd40 fffff800`02e51c26 : fffff880`0316a180 fffffa80`0553db60 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0333fd80 00000000`00000000 : fffff880`03340000 fffff880`0333a000 fffff880`0333e7f0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  Ntfs!memmove+204
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Ntfs
    
    IMAGE_NAME:  Ntfs.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f
    
    STACK_COMMAND:  .cxr 0xfffff8800333ebb0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!memmove+204
    
    BUCKET_ID:  X64_0x24_Ntfs!memmove+204
    
    Followup: MachineOwner
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI02.547\100310-24102-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50
    Debug session time: Sun Oct  3 08:35:15.148 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:16.163
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    ..
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {b074, 2, 0, fffff88003d2746d}
    
    Probably caused by : pacer.sys ( pacer!PcpLineUpdate+ad )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 000000000000b074, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88003d2746d, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b40e0
     000000000000b074 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    pacer!PcpLineUpdate+ad
    fffff880`03d2746d 48398c24b0000000 cmp     qword ptr [rsp+0B0h],rcx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880065a0650 -- (.trap 0xfffff880065a0650)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8007b03960 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88003d2746d rsp=fffff880065a07e0 rbp=0000000000000050
     r8=fffffa8007380ab8  r9=0000000000000003 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    pacer!PcpLineUpdate+0xad:
    fffff880`03d2746d 48398c24b0000000 cmp     qword ptr [rsp+0B0h],rcx ss:0018:fffff880`065a0890=fffff880065a0920
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e7bca9 to fffff80002e7c740
    
    STACK_TEXT:  
    fffff880`065a0508 fffff800`02e7bca9 : 00000000`0000000a 00000000`0000b074 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`065a0510 fffff800`02e7a920 : fffffa80`069b2200 fffffa80`07b081b0 fffffa80`00000000 fffff880`70614c00 : nt!KiBugCheckDispatch+0x69
    fffff880`065a0650 fffff880`03d2746d : fffffa80`07b081b0 00000000`00000330 00000000`00000018 fffff880`014e763a : nt!KiPageFault+0x260
    fffff880`065a07e0 fffff880`03d28fdc : 00000000`00000000 00000000`00000000 fffff880`065a0920 00000000`00000000 : pacer!PcpLineUpdate+0xad
    fffff880`065a0880 fffff880`014fc26d : fffffa80`0699e1a0 00000000`00000000 fffffa80`07b08c01 fffffa80`07b08c01 : pacer!PcFilterAttach+0x4dc
    fffff880`065a0960 fffff880`014ea8c5 : fffffa80`06d1e1a0 fffffa80`06d1e1a0 fffffa80`06d1c1a0 fffffa80`06d1e1a0 : ndis! ?? ::FNODOBFM::`string'+0xbc55
    fffff880`065a0bb0 fffff880`0157dd0d : fffffa80`06d1e101 00000000`00000080 fffffa80`06d1ace0 fffffa80`06cbd020 : ndis!ndisCheckMiniportFilters+0x125
    fffff880`065a0bf0 fffff880`014efb5a : 00000000`00000080 fffff880`0153e110 fffffa80`0737fa40 fffff880`014efaa0 : ndis!ndisCheckProtocolBindings+0x12e
    fffff880`065a0d10 fffff800`03120c06 : fffffa80`07b03960 fffffa80`054ed040 fffff880`065a0db0 fffffa80`07b03960 : ndis!ndisWorkerThread+0xba
    fffff880`065a0d40 fffff800`02e5ac26 : fffff880`02fd5180 fffffa80`07b03960 fffff880`02fe00c0 fffff880`01249a90 : nt!PspSystemThreadStartup+0x5a
    fffff880`065a0d80 00000000`00000000 : fffff880`065a1000 fffff880`0659b000 fffff880`065a0d40 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    pacer!PcpLineUpdate+ad
    fffff880`03d2746d 48398c24b0000000 cmp     qword ptr [rsp+0B0h],rcx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  pacer!PcpLineUpdate+ad
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: pacer
    
    IMAGE_NAME:  pacer.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bccc5
    
    FAILURE_BUCKET_ID:  X64_0xD1_pacer!PcpLineUpdate+ad
    
    BUCKET_ID:  X64_0xD1_pacer!PcpLineUpdate+ad
    
    Followup: MachineOwner
    ---------
    
    
    All you need to do is show the retailer my post right here.
     
    cybercore and (deleted member) like this.
  6. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    All your drivers are in excellent shape now, good job updating them. I have the same version Logitech driver, by the way, I think it's good and latest:

    LGBusEnum.sys Tue Nov 24 03:36:48 2009
    Logitech GamePanel Software



    100310-24102-01.dmp
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Stack: nt!, ndis!, nt!
    FAILURE_BUCKET_ID: X64_0xD1_pacer!PcpLineUpdate+ad
    Probably caused by : pacer.sys ( pacer!PcpLineUpdate+ad )


    100310-25084-01.dmp
    NTFS_FILE_SYSTEM (24)
    PROCESS_NAME: System
    Stack: nt!, ntfs!
    FAILURE_BUCKET_ID: X64_0x24_Ntfs!memmove+204
    Probably caused by : Ntfs.sys ( Ntfs!memmove+204 )





    Run hdd scan: HDDScan

    Run memtest: Memtest86+ - Advanced Memory Diagnostic Tool
     

Share This Page

Loading...