Regular BSOD

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7
       #1

    Regular BSOD


    Hi,

    I am suffering from unpredictable but regular BSODs, one or more a day and they seem to be getting more frequent. They occur when I am doing light browsing or emailing, one yesterday happened during a system restore.

    The BIOS is up to date and have tried several versions of the video drivers, currently (I think) the windows 7 native version. I have definitely removed the catalyst utility.

    I have attached the contents of my minidump folder.

    Any help would be very appreciated because I'm running out of ideas.

    Thanks in advance.

    Stu.

    Core 2 Duo E7600
    4GB Corsair DDR2 1066mhz
    Asus P5QL/EPU
    Windows 7 (64bit)
    250GB HD
    512mb Radeon 4670
      My Computer


  2. Posts : 1,020
    Windows 7 Ultimate 64 bit
       #2

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Tim\Desktop\minidumps\123109-16567-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: K:\SOFTWARE\mICROSOFT\Win Debug\Symbols;SRV*c:\websymbols*Symbol information
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
    Debug session time: Fri Jan  1 02:52:12.116 2010 (GMT+11)
    System Uptime: 0 days 5:24:32.755
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff69300014748, 0, fffff80002cab1ca, 5}
    
    
    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+27b )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff69300014748, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cab1ca, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb10e0
     fffff69300014748 
    
    FAULTING_IP: 
    nt!MiSwapWslEntries+6a
    fffff800`02cab1ca 498b00          mov     rax,qword ptr [r8]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88008012820 -- (.trap 0xfffff88008012820)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000053a0000
    rdx=00000000053a8000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f8ec76 rsp=fffff880080129b0 rbp=fffff88008012c60
     r8=0000000000000000  r9=00000000ffffffff r10=0400000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!ProbeForWrite+0x36:
    fffff800`02f8ec76 0fb601          movzx   eax,byte ptr [rcx] ds:2b10:00000000`053a0000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002cf8b91 to fffff80002c7af00
    
    STACK_TEXT:  
    fffff880`080121f8 fffff800`02cf8b91 : 00000000`00000050 fffff693`00014748 00000000`00000000 fffff880`08012360 : nt!KeBugCheckEx
    fffff880`08012200 fffff800`02c78fee : 00000000`00000000 fffffa80`00000028 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
    fffff880`08012360 fffff800`02cab1ca : fffffa80`00000028 fffffa80`03f0cb38 fffff700`01080488 00000001`00000001 : nt!KiPageFault+0x16e
    fffff880`080124f0 fffff800`02c969b2 : 00000000`053a5041 00000000`053a6041 fffff700`01080000 00000000`053a0000 : nt!MiSwapWslEntries+0x6a
    fffff880`08012550 fffff800`02c9728f : 80000000`9a9f8825 fffffa80`01cfde80 00000000`000026a9 fffffa80`03f0cb38 : nt!MiUpdateWsle+0xd2
    fffff880`080125b0 fffff800`02c94f23 : ffffffff`ffffff00 fffff880`08012660 00000000`00000000 000003a8`00000000 : nt!MiDispatchFault+0x6cf
    fffff880`080126c0 fffff800`02c78fee : 00000000`00000000 00000000`053a7fff 00000000`053a7f00 00000000`00000007 : nt!MmAccessFault+0x343
    fffff880`08012820 fffff800`02f8ec76 : fffffa80`04e13b10 00000000`00000004 00000000`00001000 00000000`053a0000 : nt!KiPageFault+0x16e
    fffff880`080129b0 fffff800`02f24403 : fffffa80`03f0c7a0 00000000`053a7fff 00000000`00000004 00000000`0112e4b8 : nt!ProbeForWrite+0x36
    fffff880`080129e0 fffff800`02f2d68a : 00000000`053a0000 fffffa80`03f0c7a0 00000000`00000000 fffff880`00000000 : nt!MiSecureVirtualMemory+0x113
    fffff880`08012a50 fffff960`001547f3 : fffff880`08012c60 fffffa80`03e56aa0 00000000`0112e4b8 fffff880`08012b90 : nt!MmSecureVirtualMemory+0x16
    fffff880`08012a90 fffff800`02c7a153 : ffffffff`a9010be1 00000000`00000214 ffffffff`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x27b
    fffff880`08012b70 00000000`7384056a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0112e498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7384056a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!NtGdiCreateDIBSection+27b
    fffff960`001547f3 4c8be8          mov     r13,rax
    
    SYMBOL_STACK_INDEX:  b
    
    SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+27b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0
    
    FAILURE_BUCKET_ID:  X64_0x50_win32k!NtGdiCreateDIBSection+27b
    
    BUCKET_ID:  X64_0x50_win32k!NtGdiCreateDIBSection+27b
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff69300014748, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cab1ca, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS:  fffff69300014748 
    
    FAULTING_IP: 
    nt!MiSwapWslEntries+6a
    fffff800`02cab1ca 498b00          mov     rax,qword ptr [r8]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88008012820 -- (.trap 0xfffff88008012820)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000053a0000
    rdx=00000000053a8000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f8ec76 rsp=fffff880080129b0 rbp=fffff88008012c60
     r8=0000000000000000  r9=00000000ffffffff r10=0400000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!ProbeForWrite+0x36:
    fffff800`02f8ec76 0fb601          movzx   eax,byte ptr [rcx] ds:2b10:00000000`053a0000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002cf8b91 to fffff80002c7af00
    
    STACK_TEXT:  
    fffff880`080121f8 fffff800`02cf8b91 : 00000000`00000050 fffff693`00014748 00000000`00000000 fffff880`08012360 : nt!KeBugCheckEx
    fffff880`08012200 fffff800`02c78fee : 00000000`00000000 fffffa80`00000028 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
    fffff880`08012360 fffff800`02cab1ca : fffffa80`00000028 fffffa80`03f0cb38 fffff700`01080488 00000001`00000001 : nt!KiPageFault+0x16e
    fffff880`080124f0 fffff800`02c969b2 : 00000000`053a5041 00000000`053a6041 fffff700`01080000 00000000`053a0000 : nt!MiSwapWslEntries+0x6a
    fffff880`08012550 fffff800`02c9728f : 80000000`9a9f8825 fffffa80`01cfde80 00000000`000026a9 fffffa80`03f0cb38 : nt!MiUpdateWsle+0xd2
    fffff880`080125b0 fffff800`02c94f23 : ffffffff`ffffff00 fffff880`08012660 00000000`00000000 000003a8`00000000 : nt!MiDispatchFault+0x6cf
    fffff880`080126c0 fffff800`02c78fee : 00000000`00000000 00000000`053a7fff 00000000`053a7f00 00000000`00000007 : nt!MmAccessFault+0x343
    fffff880`08012820 fffff800`02f8ec76 : fffffa80`04e13b10 00000000`00000004 00000000`00001000 00000000`053a0000 : nt!KiPageFault+0x16e
    fffff880`080129b0 fffff800`02f24403 : fffffa80`03f0c7a0 00000000`053a7fff 00000000`00000004 00000000`0112e4b8 : nt!ProbeForWrite+0x36
    fffff880`080129e0 fffff800`02f2d68a : 00000000`053a0000 fffffa80`03f0c7a0 00000000`00000000 fffff880`00000000 : nt!MiSecureVirtualMemory+0x113
    fffff880`08012a50 fffff960`001547f3 : fffff880`08012c60 fffffa80`03e56aa0 00000000`0112e4b8 fffff880`08012b90 : nt!MmSecureVirtualMemory+0x16
    fffff880`08012a90 fffff800`02c7a153 : ffffffff`a9010be1 00000000`00000214 ffffffff`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x27b
    fffff880`08012b70 00000000`7384056a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0112e498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7384056a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!NtGdiCreateDIBSection+27b
    fffff960`001547f3 4c8be8          mov     r13,rax
    
    SYMBOL_STACK_INDEX:  b
    
    SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+27b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0
    
    FAILURE_BUCKET_ID:  X64_0x50_win32k!NtGdiCreateDIBSection+27b
    
    BUCKET_ID:  X64_0x50_win32k!NtGdiCreateDIBSection+27b
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff69300014748, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cab1ca, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS:  fffff69300014748 
    
    FAULTING_IP: 
    nt!MiSwapWslEntries+6a
    fffff800`02cab1ca 498b00          mov     rax,qword ptr [r8]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88008012820 -- (.trap 0xfffff88008012820)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000053a0000
    rdx=00000000053a8000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f8ec76 rsp=fffff880080129b0 rbp=fffff88008012c60
     r8=0000000000000000  r9=00000000ffffffff r10=0400000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!ProbeForWrite+0x36:
    fffff800`02f8ec76 0fb601          movzx   eax,byte ptr [rcx] ds:2b10:00000000`053a0000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002cf8b91 to fffff80002c7af00
    
    STACK_TEXT:  
    fffff880`080121f8 fffff800`02cf8b91 : 00000000`00000050 fffff693`00014748 00000000`00000000 fffff880`08012360 : nt!KeBugCheckEx
    fffff880`08012200 fffff800`02c78fee : 00000000`00000000 fffffa80`00000028 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
    fffff880`08012360 fffff800`02cab1ca : fffffa80`00000028 fffffa80`03f0cb38 fffff700`01080488 00000001`00000001 : nt!KiPageFault+0x16e
    fffff880`080124f0 fffff800`02c969b2 : 00000000`053a5041 00000000`053a6041 fffff700`01080000 00000000`053a0000 : nt!MiSwapWslEntries+0x6a
    fffff880`08012550 fffff800`02c9728f : 80000000`9a9f8825 fffffa80`01cfde80 00000000`000026a9 fffffa80`03f0cb38 : nt!MiUpdateWsle+0xd2
    fffff880`080125b0 fffff800`02c94f23 : ffffffff`ffffff00 fffff880`08012660 00000000`00000000 000003a8`00000000 : nt!MiDispatchFault+0x6cf
    fffff880`080126c0 fffff800`02c78fee : 00000000`00000000 00000000`053a7fff 00000000`053a7f00 00000000`00000007 : nt!MmAccessFault+0x343
    fffff880`08012820 fffff800`02f8ec76 : fffffa80`04e13b10 00000000`00000004 00000000`00001000 00000000`053a0000 : nt!KiPageFault+0x16e
    fffff880`080129b0 fffff800`02f24403 : fffffa80`03f0c7a0 00000000`053a7fff 00000000`00000004 00000000`0112e4b8 : nt!ProbeForWrite+0x36
    fffff880`080129e0 fffff800`02f2d68a : 00000000`053a0000 fffffa80`03f0c7a0 00000000`00000000 fffff880`00000000 : nt!MiSecureVirtualMemory+0x113
    fffff880`08012a50 fffff960`001547f3 : fffff880`08012c60 fffffa80`03e56aa0 00000000`0112e4b8 fffff880`08012b90 : nt!MmSecureVirtualMemory+0x16
    fffff880`08012a90 fffff800`02c7a153 : ffffffff`a9010be1 00000000`00000214 ffffffff`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x27b
    fffff880`08012b70 00000000`7384056a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0112e498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7384056a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!NtGdiCreateDIBSection+27b
    fffff960`001547f3 4c8be8          mov     r13,rax
    
    SYMBOL_STACK_INDEX:  b
    
    SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+27b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0
    
    FAILURE_BUCKET_ID:  X64_0x50_win32k!NtGdiCreateDIBSection+27b
    
    BUCKET_ID:  X64_0x50_win32k!NtGdiCreateDIBSection+27b
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 1,020
    Windows 7 Ultimate 64 bit
       #3

    I'd look at updating all of my drivers with the latest ones available on the manufacturers website (not MS update) and only use drivers for windows 7 (i.e. not force installed XP or vista drivers).

    Also remove and reinstall Chrome. It seems that it is conflicting with an unidentified driver.

    If you are using unapproved drivers, I would consider disabling these devices until you find out which one is causing your problem.

    Chrome works perfectly for me (and I like it), you may find that another browser is an option as well.

    Good Luck.
      My Computer


  4. Posts : 10
    Windows 7
    Thread Starter
       #4

    Thanks for your help. Chrome occasionally asks for a disk to be placed in the D drive (which is a DVD writer), so maybe that is part of the problem.

    I'll keep digging.

    Stuart.
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    Try running Driver Verifier using these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  6. Posts : 10
    Windows 7
    Thread Starter
       #6

    Thanks,

    I am currently running my PC with this process running so I'll let you know what happens. In the meantime, I tried to run backup 3 times and it crashed each time, see the attached file.
      My Computer


  7. Posts : 10
    Windows 7
    Thread Starter
       #7

    Hi,

    Here is a minidump from a BSOD I had just now. This has happened when trying to make a backup to an external USB hard-drive that is not usually turned on, so isn't totally representative of my problems. I will keep running validator in normal operation and will add another dump if (when) I get another error.
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Were all backups to the external drive? Have you run a diagnostic on the external drive? It's usually available for free from the manufacturer of the external drive. If not, then try this free one: HD Tune website (about ½ way down the page)

    I'd suggest updating this driver: ASACPI.sys Mon Jan 21 04:45:00 2008
    It's the Asus ATK0110 ACPI Utility - get the latest Win7 version from the Asus Support website

    Then I'd suggest this procedure for your networking drivers:
    Driver Removal and Reinstallation:
    Please do the following:
    - download a fresh copy of the latest Win7 version of the networking driver(s) from the device manufacturer's website (NOT from Windows Update or from the Update driver function in Device Manager). If there are no Win7 drivers, post back for further instructions on installing Vista drivers using Compatibility mode.
    - uninstall the current version from your system
    - install the freshly downloaded version
    - check to see if you have any further BSOD's
    If this doesn't help, please post back with the next BSOD's and we'll have a look at trying some different tests.
      My Computer


  9. Posts : 10
    Windows 7
    Thread Starter
       #9

    Thanks for your continued help and patience. Since I last posted, I have updated the driver for the network adapter (listed on the device manager now as realtek PCIe GBE family controller). Is this the one you suggested I do?

    I have successfully managed to back up my data on the external hard drive that was causing problems. However, I used a different USB port (one on the front rather than the back), so I don't know whether it was the new network driver or the different port that solved it. I'll have a play with HD tune.

    I have also found a new version of ASACPI. Fingers crossed!
      My Computer


  10. Posts : 1,020
    Windows 7 Ultimate 64 bit
       #10

    redstu said:
    Thanks for your continued help and patience. Since I last posted, I have updated the driver for the network adapter (listed on the device manager now as realtek PCIe GBE family controller). Is this the one you suggested I do?

    I have successfully managed to back up my data on the external hard drive that was causing problems. However, I used a different USB port (one on the front rather than the back), so I don't know whether it was the new network driver or the different port that solved it. I'll have a play with HD tune.

    I have also found a new version of ASACPI. Fingers crossed!
    Fingers are crossed! Let us know how you go.
      My Computer


 
Page 1 of 2 12 LastLast

  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 06:00.
Find Us