Random BSODs


  1. Posts : 2
    Windows 7 Home Premium 32bit
       #1

    Random BSODs


    All right, so I'm pretty much at the end of my rope here and I'm hoping that y'all can give me ANY idea what course of action to take.

    I built a computer back in May and have already fully formatted it 5 times due to problems with crashing and restarting. It has survived a prime95 torture test with no problems at all, and actually seems to work better under higher load. Here is the build:

    AZZA Solano Full Tower ATX case (air-cooled)
    GIGABYTE GA-P55-USB3 LGA 1156 Intel P55 USB 3.0 ATX Intel Motherboard
    Intel Core i3-530 Clarkdale 2.93GHz LGA 1156 73W Dual-Core Desktop Processor, stock cooling
    XFX HD-577A-ZNFC Radeon HD 5770 (Juniper XT) 1GB 128-bit GDDR5 Video Card
    Antec EarthWatts EA750 750W Continuous Power ATX12V version 2.3 Power Supply
    G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) 9-9-9-24 timings Dual Channel Kit Desktop Memory Model F3-12800CL9D-4GBNQ
    Western Digital Caviar Blue WD5000AAKS 500GB 7200 RPM SATA Internal Hard Drive
    Windows 7 Home Premium 32-bit OS

    I have already tried increasing voltages slightly to increase stability in addition to trying several stable voltage/frequency settings from this and other sites, turning off power-saving features, using memtest86+ for 12 passes (no problems), and running from integrated sound and video. It’s been a long time trying to get this thing working, so my apologies if I forgot something specific. I can post data from any testing program, but I honestly don’t really know where to start given the problems I am experiencing.

    The primary point is that this doesn’t seem to be related to hardware installation, since the build works perfectly with Windows 7 before installation of drivers and programs, and during the latest restore even was working after installation of all drivers and several programs (MS Office, MediaMonkey, Firefox, Security Essentials, etc.) It also seems to have completely random errors with programs when it starts up, but particularly Windows Explorer. The one error message I have written down (most of the rest flash right before BSOD) in relation to several explorer.exe processes is “The instruction at 0x76919A70 referenced memory at 0x00000250. The memory could not be read. Click OK to close the program.”

    Also, the computer seems to be worst from cold boot. I noticed recently that it goes in a pattern, normally taking 3-4 boots to remain stable in Windows in any combination of these crashes/errors:

    -Gets past “Loading Windows” screen and then BSOD
    -Gets to login screen, then BSOD when I click on my profile.
    -Click on profile, then goes to a black screen with a cursor, must be manually shut down
    -Get into Windows Explorer, let load for about a minute, then try and do anything and it BSOD’s (click on link, open program, etc.)
    -Click on profile and it takes longer than usual at the “Preparing desktop” screen. Then it “sets up a temporary account” and I have to log off in order to get back to my actual account. It seems like it normally runs stable after that.
    -When Windows Update is installing things, it will BSOD and then freeze there without restarting. This seems to happen every other time.

    -I ran WD Data Lifeguard Diagnostics on the first HD but it came up with no problems. My brother (who built a computer of his own) said that most of the problems sounded like HD problems, and that I shouldn't trust that diagnostic software would catch everything.

    -While my brother was there, I used the video card from his computer which I know works (I believe it is a nVidia 9000 series or something) in place of the one currently in mine. It immediately had the exact same problems, so it seems as though at least none of the major issues are caused by the video card. I have heard that the ATI drivers can cause stability issues, so I've tried both the Catalyst suite and the basic drivers with no difference. I also installed .NET Framework 4.0 beforehand because I had read that if it is not present there may be problems.

    -I bought a new HD because that was the most likely candidate for the problems I've had. The new one is a "Western Digital Caviar Black WD6402AAEX 640GB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive." It worked better for installation of Windows 7 and hasn't had the constant crashing problems that the other one did, but it just gave me a BSOD twice, booted Windows with a black screen and a cursor, crashed Firefox/Chrome and Catalyst Control Center several times, and has prompted me several times to run both disk check and startup repair. The problems went away for a bit, but then came back just the same. I do have my original Caviar Blue HD installed as a second non-RAID hard drive.

    -I have disabled all power saving BIOS options and changed the "minimum CPU load" setting to 100%, and while this seemed to help for a week or so it's back to doing the same thing it normally does.

    -I looked at https://www.sevenforums.com/crashes-d...nel-power.html and tried most of the ideas on there, but I don't want to buy a new motherboard or PSU without at least having someone look at the dump files I'm uploading here.

    There are two things I'd like to know in addition to ANYTHING that you guys happen to think would help. First, is there a software that effectively runs diagnostics on the motherboard/PSU? I'm starting to think that the motherboard might be the problem. Second, I've been looking for RAM specs. I've tried to figure out where to locate these, but have so far had no luck. Is there a site that would have the full voltage and frequency specifications for my RAM when used in this GIGABYTE motherboard (or something close enough that it would at least be accurate)? I've looked on the G.Skill website with no luck on full stats, and most other sites only have partial stats that I'm not sure are accurate for my specific RAM.

    It does seem like a lot of these errors are related to explorer.exe and result in a BSOD, but I lack the experience to know how to troubleshoot problems of this sort. I apologize if this post isn't exactly what you need, but please let me know if there's anything else that would help diagnose what the hell is going on and I'll try and get it (since stability is the problem, it might be difficult...). Thank you so much for any help, I really appreciate it.
      My Computer


  2. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #2

    I looked at your three most recent dumps. None of them give us a direct cause and they all indicate memory corruption.

    I recommend that while you are troubleshooting, you uninstall Avast. Avast generally runs well with Win 7; but one of your dumps shows it was involved in the crash, though not necessarily the cause. Download and install Microsoft Security Essentials. Once you get your system stable, you can try Avast again.

    Next run Memtest again from a cold boot after your computer has been off for a couple of hours. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Let it run for at least seven passes. I know you ran more passes before. Post back with your results.

    If you find no errors with Memtest, Enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any and all dumps triggered by Driver Verifier.

    Do you have another known good power supply that you can try? A faulty power supply can trigger the BSOD's you are having.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82c55000 PsLoadedModuleList = 0x82d9d810
    Debug session time: Wed Dec 22 12:59:54.051 2010 (GMT-5)
    System Uptime: 0 days 0:00:17.988
    Loading Kernel Symbols
    ...............................................................
    ...............................................................
    Loading User Symbols
    Loading unloaded module list
    ....
    2: kd> !Analyze
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffffff, 0, 9a11d71c, 0}
    
    
    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!wcsncpycch+14 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: ffffffff, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 9a11d71c, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
    Unable to read MiSystemVaType memory at 82d9d160
     ffffffff 
    
    FAULTING_IP: 
    win32k!wcsncpycch+14
    9a11d71c 0fb70a          movzx   ecx,word ptr [edx]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  8e56b7a4 -- (.trap 0xffffffff8e56b7a4)
    ErrCode = 00000000
    eax=00b8c748 ebx=ffb8c748 ecx=879d7a60 edx=ffffffff esi=00b8c748 edi=ffb898a0
    eip=9a11d71c esp=8e56b818 ebp=8e56b81c iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    win32k!wcsncpycch+0x14:
    9a11d71c 0fb70a          movzx   ecx,word ptr [edx]       ds:0023:ffffffff=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82c9b638 to 82cda903
    
    STACK_TEXT:  
    8e56b78c 82c9b638 00000000 ffffffff 00000000 nt!MmAccessFault+0x106
    8e56b78c 9a11d71c 00000000 ffffffff 00000000 nt!KiTrap0E+0xdc
    8e56b81c 9a0f23fb 00b8c748 ffffffff ffffffff win32k!wcsncpycch+0x14
    8e56b844 9a0fc5e5 147bcf92 00000000 ffb92390 win32k!PDEVOBJ::bMakeSurface+0xe2
    8e56b8bc 9a0fb312 ffb92390 ffb8b110 ffbadf20 win32k!hCreateHDEV+0x7b8
    8e56ba78 9a0f9eee 00000000 00000000 00000000 win32k!DrvCreateMDEV+0x5fd
    8e56bb84 9a0f917e 00000000 00000000 00000000 win32k!DrvInternalChangeDisplaySettings+0x50b
    8e56bca0 9a0d62ce 00000000 00000000 00000000 win32k!DrvChangeDisplaySettings+0x3ae
    8e56bcf8 9a0d4be3 00000000 00000040 00000000 win32k!InitVideo+0x60
    8e56bd18 9a0d59b0 0021f538 8e56bd34 82c9844a win32k!UserInitialize+0x115
    8e56bd24 82c9844a 00000040 00000044 0021f554 win32k!NtUserInitialize+0x9f
    8e56bd24 770464f4 00000040 00000044 0021f554 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0021f554 00000000 00000000 00000000 00000000 0x770464f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!wcsncpycch+14
    9a11d71c 0fb70a          movzx   ecx,word ptr [edx]
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  win32k!wcsncpycch+14
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c7dbbb5
    
    FAILURE_BUCKET_ID:  0x50_win32k!wcsncpycch+14
    
    BUCKET_ID:  0x50_win32k!wcsncpycch+14
    
    Followup: MachineOwner
    ---------
    
    Debug session time: Fri Dec 10 23:06:12.072 2010 (GMT-5)
    System Uptime: 0 days 0:04:34.384
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    .....
    3: kd> !Analyze
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {5003, c0802000, 5fd, 5ffbba}
    
    Probably caused by : memory_corruption ( nt!MiAllocateWsle+6f )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00005003, The subtype of the bugcheck.
    Arg2: c0802000
    Arg3: 000005fd
    Arg4: 005ffbba
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_5003
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  DAOriginsLaunc
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 82ce7a30 to 82d2ad10
    
    STACK_TEXT:  
    9eff2b3c 82ce7a30 0000001a 00005003 c0802000 nt!KeBugCheckEx+0x1e
    9eff2b74 82cef944 c03b3c90 84bb8d14 00000000 nt!MiAllocateWsle+0x6f
    9eff2bc4 82cf5c32 00000000 878cc900 76792e74 nt!MiCompleteProtoPteFault+0x34f
    9eff2c08 82cde916 00000000 76792e74 c03b3c90 nt!MiResolveProtoPteFault+0x1e1
    9eff2c90 82cd5dd5 76792e74 00000000 878cc900 nt!MiDispatchFault+0x5d6
    9eff2d1c 82c94638 00000008 76792e74 00000001 nt!MmAccessFault+0x25cc
    9eff2d1c 76792e74 00000008 76792e74 00000001 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f3d8 00000000 00000000 00000000 00000000 0x76792e74
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiAllocateWsle+6f
    82ce7a30 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiAllocateWsle+6f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+6f
    
    BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+6f
    
    Followup: MachineOwner
    ---------
    
    Debug session time: Thu Dec  9 18:56:52.993 2010 (GMT-5)
    System Uptime: 0 days 0:03:02.366
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    ......
    0: kd> !Analyze
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {7, 1097, 6e0069, a43c2998}
    
    GetPointerFromAddress: unable to read from 82d77718
    Unable to read MiSystemVaType memory at 82d57160
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
    *** WARNING: Unable to verify timestamp for ksecpkg.sys
    *** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
    *** WARNING: Unable to verify timestamp for fvevol.sys
    *** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    *** WARNING: Unable to verify timestamp for Rt86win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
    *** WARNING: Unable to verify timestamp for ks.sys
    *** ERROR: Module load completed but symbols could not be loaded for ks.sys
    *** WARNING: Unable to verify timestamp for aswTdi.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
    *** WARNING: Unable to verify timestamp for aswRdr.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswRdr.SYS
    *** WARNING: Unable to verify timestamp for aswSP.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for aswMonFlt.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
    *** WARNING: Unable to verify timestamp for aswFsBlk.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.SYS
    *** WARNING: Unable to verify timestamp for RTKVHDA.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys
    *** WARNING: Unable to verify timestamp for ivusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for ivusb.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *** WARNING: Unable to verify timestamp for TSDDD.dll
    *** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
    *** WARNING: Unable to verify timestamp for cdd.dll
    *** ERROR: Module load completed but symbols could not be loaded for cdd.dll
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys
    *** WARNING: Unable to verify timestamp for secdrv.SYS
    *** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
    *** WARNING: Unable to verify timestamp for spsys.sys
    *** ERROR: Module load completed but symbols could not be loaded for spsys.sys
    GetPointerFromAddress: unable to read from 82d77718
    Unable to read MiSystemVaType memory at 82d57160
    Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+1b1 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000007, Attempt to free pool which was already freed
    Arg2: 00001097, (reserved)
    Arg3: 006e0069, Memory contents of the pool block
    Arg4: a43c2998, Address of the block of pool being deallocated
    
    Debugging Details:
    ------------------
    
    GetPointerFromAddress: unable to read from 82d77718
    Unable to read MiSystemVaType memory at 82d57160
    GetPointerFromAddress: unable to read from 82d77718
    Unable to read MiSystemVaType memory at 82d57160
    
    POOL_ADDRESS: GetPointerFromAddress: unable to read from 82d77718
    Unable to read MiSystemVaType memory at 82d57160
     a43c2998 
    
    BUGCHECK_STR:  0xc2_7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 82e2790d to 82d2e1b6
    
    STACK_TEXT:  
    8e593c6c 82e2790d a43c2998 00000000 820e9468 nt!ExFreePoolWithTag+0x1b1
    8e593c80 82e27a85 00000000 820e9468 00000000 nt!CmpCleanUpKcbValueCache+0x3e
    8e593c94 82e4546d 00000000 820e9468 820e9488 nt!CmpCleanUpKcbCacheWithLock+0x25
    8e593cb4 82e56c5d 820e9468 00000000 82d76080 nt!CmpDereferenceKeyControlBlockWithLock+0x8d
    8e593ce4 82e27493 82d495bc 82d76070 8577ad48 nt!CmpDereferenceKeyControlBlock+0x11b
    8e593d00 82c7cf3b 00000000 00000000 8577ad48 nt!CmpDelayDerefKCBWorker+0xea
    8e593d50 82e1d6d3 00000001 a5277496 00000000 nt!ExpWorkerThread+0x10d
    8e593d90 82ccf0f9 82c7ce2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExFreePoolWithTag+1b1
    82d2e1b6 cc              int     3
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExFreePoolWithTag+1b1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac
    
    FAILURE_BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag+1b1
    
    BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag+1b1
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 32bit
    Thread Starter
       #3

    So yeah...the idea to cold boot into memtest probably just made my Christmas, as it's already discovered 1900 errors (!) in less than 20 minutes. Hopefully I can get G.Skill to send me some new RAM soon. I'll update if the new RAM has the same problems, but thank you so much for the insight I needed to clear this headache!

    Total of 13056 errors on 2 passes. Trying the single stick after I get home from Christmas Eve stuff :)
    Last edited by JaxomofRuatha; 24 Dec 2010 at 15:13.
      My Computer


 

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