locked
BSOD after several reinstalls RRS feed

  • Question

  • My system freezes up in an BSOD after while, at regular intervals. And i can't find the reason for this problem. Is there anyone who can help me read the minidump and maybe find out what's causing this ? I have windows 7 running on a desktop self designed system, mostly consisting of Asus hardware. (sorry for my bad english)

    Friday, August 26, 2011 2:51 PM

Answers

  • It could be a corrupted installation dvd or download file if you are not using a Microsoft retail disk.

    Try reburning the installation dvd from the .iso at a slower speed and verify when complete.

    Another common source for this is the display adapter drivers.

    Formatting the drive is a half-clean. Delete all partitions first, repartition, set one active, install or format and install.

     


    • Marked as answer by Leo Huang Monday, September 5, 2011 1:06 AM
    Saturday, August 27, 2011 12:01 PM
  • I checked one of your dump file:

     

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    SYSTEM_SERVICE_EXCEPTION (3b)

    An exception happened while executing a system service routine.

    Arguments:

    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    Arg2: fffff80002bc0121, Address of the instruction which caused the bugcheck

    Arg3: fffff8800bd5b050, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.

     

    Debugging Details:

    ------------------

     

     

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

     

    FAULTING_IP:

    nt!ObReferenceObjectByHandleWithTag+191

    fffff800`02bc0121 488901          mov     qword ptr [rcx],rax

     

    CONTEXT:  fffff8800bd5b050 -- (.cxr 0xfffff8800bd5b050)

    rax=fffffa8007e40290 rbx=fffff8a008ebc4c0 rcx=5803f8800bd5b350

    rdx=0000000000000000 rsi=fffff8a0079ffd10 rdi=fffffa800979ab60

    rip=fffff80002bc0121 rsp=fffff8800bd5ba30 rbp=fffffa8007e40260

     r8=fffff8a008ebc000  r9=0000000000000130 r10=fffffa800704cd50

    r11=00000000001f0001 r12=0000000000000000 r13=0000000000000130

    r14=0000000000000001 r15=fffffa8007fafb30

    iopl=0         nv up ei pl nz na pe nc

    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

    nt!ObReferenceObjectByHandleWithTag+0x191:

    fffff800`02bc0121 488901          mov     qword ptr [rcx],rax ds:002b:5803f880`0bd5b350=????????????????

    Resetting default scope

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0x3B

     

    PROCESS_NAME:  wuauclt.exe

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from fffff80002bd7231 to fffff80002bc0121

     

    STACK_TEXT: 

    fffff880`0bd5ba30 fffff800`02bd7231 : 00000000`00000000 00000000`00000001 fffffa80`0704cd50 ffffd7dd`6c0fc801 : nt!ObReferenceObjectByHandleWithTag+0x191

    fffff880`0bd5bb00 fffff800`028c8ed3 : fffffa80`0979ab60 fffff880`0bd5bca0 00000000`00000003 000007fe`f79406dc : nt!NtAlpcSendWaitReceivePort+0x71

    fffff880`0bd5bbb0 00000000`77a21b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

    00000000`017ee128 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a21b6a

     

     

    FOLLOWUP_IP:

    nt!ObReferenceObjectByHandleWithTag+191

    fffff800`02bc0121 488901          mov     qword ptr [rcx],rax

     

    SYMBOL_STACK_INDEX:  0

     

    SYMBOL_NAME:  nt!ObReferenceObjectByHandleWithTag+191

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: nt

     

    IMAGE_NAME:  ntkrnlmp.exe

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

     

    STACK_COMMAND:  .cxr 0xfffff8800bd5b050 ; kb

     

    FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+191

     

    BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+191

     

    Followup: MachineOwner

    ---------

     

    About bugcheck 0x3b, you can refer this article:

    http://msdn.microsoft.com/en-us/library/ff558949(v=VS.85).aspx

     

    The issue caused by the process wuauclt.exe, this is Windows Update AutoUpdate Client. This is a background process which checks with the Microsoft website for updates to the operating system.

    Sometimes it maybe a virus or spyware.

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Leo Huang Monday, September 5, 2011 1:06 AM
    Monday, August 29, 2011 3:36 AM

All replies

  • Yep, upload it to skydrive and paste a link here
    Friday, August 26, 2011 5:15 PM
  • This is windows update crashing on a read error in the kernel.  Have you run antivirus?  This could be anything from a rootkit to a bad stick of RAM.
    Friday, August 26, 2011 6:11 PM
  • I formatted the c drive and reinstalled Windows. So it shouldnt be a virus. I was also thinking about the ram. But how do i check if its malfunctioning ?
    Friday, August 26, 2011 11:12 PM
  • I formatted the c drive and reinstalled Windows. So it shouldnt be a virus. I was also thinking about the ram. But how do i check if its malfunctioning ?


    And i had this problem before, this is the third reinstallation i did and problem keeps coming back. I posted the lastest Minidump on skydrive

     

    https://skydrive.live.com/redir.aspx?cid=f8fa9742c38d036f&resid=F8FA9742C38D036F!131&authkey=KS3fzjGitf8%24

     

    Thanks again

    Friday, August 26, 2011 11:18 PM
  • You can check by running memtest.  http://www.memtest.org/

     

    Any errors are too many.  Let it run overnight or something, and if there are any errors, replace the RAM. 

    Friday, August 26, 2011 11:22 PM
  • Ok i'm gonna run the memory test, thnx again for the quick response and support
    Saturday, August 27, 2011 11:07 AM
  • It could be a corrupted installation dvd or download file if you are not using a Microsoft retail disk.

    Try reburning the installation dvd from the .iso at a slower speed and verify when complete.

    Another common source for this is the display adapter drivers.

    Formatting the drive is a half-clean. Delete all partitions first, repartition, set one active, install or format and install.

     


    • Marked as answer by Leo Huang Monday, September 5, 2011 1:06 AM
    Saturday, August 27, 2011 12:01 PM
  • I checked one of your dump file:

     

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    SYSTEM_SERVICE_EXCEPTION (3b)

    An exception happened while executing a system service routine.

    Arguments:

    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    Arg2: fffff80002bc0121, Address of the instruction which caused the bugcheck

    Arg3: fffff8800bd5b050, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.

     

    Debugging Details:

    ------------------

     

     

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

     

    FAULTING_IP:

    nt!ObReferenceObjectByHandleWithTag+191

    fffff800`02bc0121 488901          mov     qword ptr [rcx],rax

     

    CONTEXT:  fffff8800bd5b050 -- (.cxr 0xfffff8800bd5b050)

    rax=fffffa8007e40290 rbx=fffff8a008ebc4c0 rcx=5803f8800bd5b350

    rdx=0000000000000000 rsi=fffff8a0079ffd10 rdi=fffffa800979ab60

    rip=fffff80002bc0121 rsp=fffff8800bd5ba30 rbp=fffffa8007e40260

     r8=fffff8a008ebc000  r9=0000000000000130 r10=fffffa800704cd50

    r11=00000000001f0001 r12=0000000000000000 r13=0000000000000130

    r14=0000000000000001 r15=fffffa8007fafb30

    iopl=0         nv up ei pl nz na pe nc

    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

    nt!ObReferenceObjectByHandleWithTag+0x191:

    fffff800`02bc0121 488901          mov     qword ptr [rcx],rax ds:002b:5803f880`0bd5b350=????????????????

    Resetting default scope

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0x3B

     

    PROCESS_NAME:  wuauclt.exe

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from fffff80002bd7231 to fffff80002bc0121

     

    STACK_TEXT: 

    fffff880`0bd5ba30 fffff800`02bd7231 : 00000000`00000000 00000000`00000001 fffffa80`0704cd50 ffffd7dd`6c0fc801 : nt!ObReferenceObjectByHandleWithTag+0x191

    fffff880`0bd5bb00 fffff800`028c8ed3 : fffffa80`0979ab60 fffff880`0bd5bca0 00000000`00000003 000007fe`f79406dc : nt!NtAlpcSendWaitReceivePort+0x71

    fffff880`0bd5bbb0 00000000`77a21b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

    00000000`017ee128 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a21b6a

     

     

    FOLLOWUP_IP:

    nt!ObReferenceObjectByHandleWithTag+191

    fffff800`02bc0121 488901          mov     qword ptr [rcx],rax

     

    SYMBOL_STACK_INDEX:  0

     

    SYMBOL_NAME:  nt!ObReferenceObjectByHandleWithTag+191

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: nt

     

    IMAGE_NAME:  ntkrnlmp.exe

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

     

    STACK_COMMAND:  .cxr 0xfffff8800bd5b050 ; kb

     

    FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+191

     

    BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+191

     

    Followup: MachineOwner

    ---------

     

    About bugcheck 0x3b, you can refer this article:

    http://msdn.microsoft.com/en-us/library/ff558949(v=VS.85).aspx

     

    The issue caused by the process wuauclt.exe, this is Windows Update AutoUpdate Client. This is a background process which checks with the Microsoft website for updates to the operating system.

    Sometimes it maybe a virus or spyware.

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Leo Huang Monday, September 5, 2011 1:06 AM
    Monday, August 29, 2011 3:36 AM