10 BSODs in a week

[Makivante]

Fresh install of Windows 7 64-bit on or about April 1st. Crashes have been happening ever since.

Event ID 41 (which says not much), but Kernal-Power is the source every time.

Potential causes (my guesses):
Incorrect Raid controllers - I had to find new ones compatible with win 7 when I installed fresh.

Radeon 5700 graphics card driver issues, although I loaded the 8.723.0.0 drivers released on 4/28/2010.

Sleep/Hibernation issue. More often than not, I see a "Windows has recovered from an unexpected error" pop-up after I leave it alone for several hours.

Thanks in advance for examining my problem.

 

[Makivante]

And just when browsing to see what problems other people are having...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C23D8FF8
BCP2: 0000000000000001
BCP3: FFFFF960001939C6
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050910-15553-01.dmp

 

[zigzag3143]

Fresh install of Windows 7 64-bit on or about April 1st. Crashes have been happening ever since.

Event ID 41 (which says not much), but Kernal-Power is the source every time.

Potential causes (my guesses):
Incorrect Raid controllers - I had to find new ones compatible with win 7 when I installed fresh.

Radeon 5700 graphics card driver issues, although I loaded the 8.723.0.0 drivers released on 4/28/2010.

Sleep/Hibernation issue. More often than not, I see a "Windows has recovered from an unexpected error" pop-up after I leave it alone for several hours.

Thanks in advance for examining my problem.

Ok, you have several causes. First more than half of these were caused by either the directx component, or the video driver. ALl of these can be eliminated by completely removing your current driver (mfr probably makes an un-install tool) and just re-installing the most up to date driver. Dont add the extra stuff.

Then readyboost has caused a few. If you have enough ram (4gig+) you could not use it.

There are a few more. with that many causes I have to start thinking hardware, and I would start with memory. There was no clear evidence of memory problems but I would still test it by downloading memtestx86 and running it for 5 passes.

Let us know if you need help

Ken

040510-17425-01.dmp    4/5/2010 11:43:36 AM        0x00000116    fffffa80`01ac1210    fffff880`03ea9ef0    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\BSODs\040510-17425-01.dmp    2    15    7600    
040510-16894-01.dmp    4/5/2010 11:56:58 PM        0x00000116    fffffa80`01a89010    fffff880`03ee9ef0    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\BSODs\040510-16894-01.dmp    2    15    7600    
050710-15412-01.dmp    5/7/2010 5:56:04 AM        0x00000116    fffffa80`053da010    fffff880`02c0602c    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\BSODs\050710-15412-01.dmp    2    15    7600    
042810-14742-01.dmp    4/28/2010 4:06:44 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff900`c1f75ff8    00000000`00000001    fffff960`001239cb    00000000`00000000    dxgmms1.sys    dxgmms1.sys+c095                    x64        C:\Users\K\Desktop\BSODs\042810-14742-01.dmp    2    15    7600    
041610-15194-01.dmp    4/16/2010 1:20:38 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff880`0749aff8    00000000`00000000    fffff800`028cf610    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\041610-15194-01.dmp    2    15    7600    
042910-13712-01.dmp    4/29/2010 1:53:16 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02c06814    fffff880`0524e810    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\042910-13712-01.dmp    2    15    7600    
050410-16192-01.dmp    5/4/2010 9:16:42 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02986c07    fffff880`073bdc20    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\050410-16192-01.dmp    2    15    7600    
050710-16910-01.dmp    5/7/2010 3:23:56 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    fffff800`02daf714    00000000`00000000    00000000`00000008    fffff800`02daf714    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\050710-16910-01.dmp    2    15    7600    
050810-16364-01.dmp    5/8/2010 1:32:56 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff8a0`08f57ff8    00000000`00000001    fffff800`02a74620    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\050810-16364-01.dmp    2    15    7600    
050910-18720-01.dmp    5/9/2010 1:25:48 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02b8dc07    fffff880`08a8bc20    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\050910-18720-01.dmp    2    15    7600    
050910-16146-01.dmp    5/9/2010 4:22:46 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02bdb254    fffff880`06500c70    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\BSODs\050910-16146-01.dmp    2    15    7600    
041810-13494-01.dmp    4/18/2010 12:48:38 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`028988eb    fffff880`028c3030    00000000`00000000    nvm62x64.sys    nvm62x64.sys+5308                    x64        C:\Users\K\Desktop\BSODs\041810-13494-01.dmp    2    15    7600    
050510-17908-01.dmp    5/5/2010 12:07:26 AM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    ffffffff`c0000005    fffff800`02ab0c69    00000000`00000000    ffffffff`ffffffff    rdyboost.sys    rdyboost.sys+17101                    x64        C:\Users\K\Desktop\BSODs\050510-17908-01.dmp    2    15    7600    
050510-14180-01.dmp    5/5/2010 1:11:04 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff900`c1e8cff8    00000000`00000001    fffff960`000c39db    00000000`00000000    win32k.sys    win32k.sys+0                    x64        C:\Users\K\Desktop\BSODs\050510-14180-01.dmp    2    15    7600

 

[Makivante]

Made a burned Disc of RAM test and ran it for 5 iterations (2+ hours), no errors found.

I only have 2 gigs of ram - not sure about readyboost. The stickied STOP error thread at the top of this forum talks about a case where drives that are called aren't responding fast enough. I'm wondering if it's reading my storage drive as a flash drive or something odd, and it's not responding because it needs time to wake up.

Uninstalled all ATI, then redownloaded driver. My computer is trying to direct me to the 32-bit download page (which is fals). Upon reinstall, I had no choice but to install the "ATI Install manager" first, then the actual ATI driver. This doesn't include all the catalyst control center extras, though.

I'll follow up in a little while. Thanks again for your guidance.

 

[Makivante]

After installing drivers only and unhooking my terabyte-sized external HD, no problems for a day until (see attached zip).

Thoughts?

 

[zigzag3143]

After installing drivers only and unhooking my terabyte-sized external HD, no problems for a day until (see attached zip).

Thoughts?

This one is pretty staright forward. Your video driver. Use the mfr un-install tool to remove all traces of this drives and install a fresh copy.

Let us know if you need help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\051110-17550-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a12000 PsLoadedModuleList = 0xfffff800`02c4fe50
Debug session time: Tue May 11 16:24:17.229 2010 (GMT-4)
System Uptime: 1 days 16:24:09.087
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003a1e87e, fffff8800366d6d8, fffff8800366cf40}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+dea )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003a1e87e, The address that the exception occurred at
Arg3: fffff8800366d6d8, Exception Record Address
Arg4: fffff8800366cf40, Context Record Address

Debugging Details:
------------------


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

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+dea
fffff880`03a1e87e 4c8b4500        mov     r8,qword ptr [rbp]

EXCEPTION_RECORD:  fffff8800366d6d8 -- (.exr 0xfffff8800366d6d8)
ExceptionAddress: fffff88003a1e87e (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x0000000000000dea)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

CONTEXT:  fffff8800366cf40 -- (.cxr 0xfffff8800366cf40)
rax=0000000000000183 rbx=0000000000000000 rcx=0000000000613000
rdx=fffff8800366db80 rsi=fffffa8002467898 rdi=fffffa800531d000
rip=fffff88003a1e87e rsp=fffff8800366d910 rbp=003ffa8002432830
 r8=fffffa8001e55500  r9=fffff8800366d901 r10=0000000000000000
r11=fffffa8003078410 r12=0000000000000106 r13=0000000000000000
r14=fffffa800219b330 r15=000000000000069d
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xdea:
fffff880`03a1e87e 4c8b4500        mov     r8,qword ptr [rbp] ss:0018:003ffa80`02432830=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

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_PARAMETER1:  ffffffffffffffff

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cba0e0
 0000000000000000 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+dea
fffff880`03a1e87e 4c8b4500        mov     r8,qword ptr [rbp]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88003a3865d to fffff88003a1e87e

STACK_TEXT:  
fffff880`0366d910 fffff880`03a3865d : 00000000`00000000 fffff8a0`0698b610 fffffa80`00000000 fffffa80`0219b330 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xdea
fffff880`0366dae0 fffff880`03a38398 : fffff880`009efec0 fffff880`03a37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0366dcd0 fffff880`03a37e96 : 00000000`00000000 fffffa80`01b8f870 00000000`00000080 fffffa80`03078410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0366dd00 fffff800`02d27a86 : 00000000`03ab4550 fffffa80`04fe7b60 fffffa80`018a8040 fffffa80`04fe7b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0366dd40 fffff800`02a60b06 : fffff880`009eb180 fffffa80`04fe7b60 fffff880`009f5f40 5a483633`6d6f6d62 : nt!PspSystemThreadStartup+0x5a
fffff880`0366dd80 00000000`00000000 : fffff880`0366e000 fffff880`03668000 fffff880`0366d690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+dea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff8800366cf40 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+dea

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+dea

Followup: MachineOwner
---------

 

[Makivante]

I did this the first time you instructed me to (but apparently not correctly).

Is it worth trying to install the 32-bit graphics driver? To be clear, when I go to system properties, it tells me "64-bit operating system" on my machine - but - when looking at "Solve PC issues" in the lower right corner, it says "address a problem with ATI graphics driver" When I have seen this in the past and been able to follow the link, it took me to the Radeon 32 bit page, is why I ask. (That doesn't help though, the link times out - why is it that I can never download the solution when I click on the problem?)

Thanks, sorry for WallOfText

 

[zigzag3143]

I did this the first time you instructed me to (but apparently not correctly).

Is it worth trying to install the 32-bit graphics driver? To be clear, when I go to system properties, it tells me "64-bit operating system" on my machine - but - when looking at "Solve PC issues" in the lower right corner, it says "address a problem with ATI graphics driver" When I have seen this in the past and been able to follow the link, it took me to the Radeon 32 bit page, is why I ask. (That doesn't help though, the link times out - why is it that I can never download the solution when I click on the problem?)

Thanks, sorry for WallOfText

No problem.

First If you are 64bit I dont think you can use the 32 bit.

Did you use the un-install tool?

Did you just install the driver from the mfr web site. Dont use the win 7 update feature.

Ken

 

[Makivante]

Going to re-uninstall and document the process step by step. I'll follow up later. Thanks again for the help so far. It's been invaluable.

 

[zigzag3143]

Going to re-uninstall and document the process step by step. I'll follow up later. Thanks again for the help so far. It's been invaluable.

No problem that what we are here for
\
Ken

 

[Makivante]

Despite best efforts, couldn't find a specific program from ATI that is just for uninstalling. So, downloaded 64-bit version again, used the uninstall feature in the catalyst control panel to uninstall everything (only the ATI Driver was listed as installed previously - I don't think the install manager was removed though). Rebooted. Desktop comes back up after reboot with about 800x600 resolution (smallest).

I run the install program as administrator, deselecting all the other junk except the bare minimum (Driver, ATI Catalyst Install manager and Microsoft Visual C++ 2008 SP1 Redistributable) and install.

Further, I thought this might be related to hibernation/sleep issues, so I manipulated power settings in the control panel to prevent sleep/hibernation. Hooray for 3 page thread on AMD forums that includes several similar issues regarding the 5770 and win 7 64 bit: AMD Game Forums - Hibernate / sleep problems on Windows 7 with Radeon HD 5770

Hey, guess what happened? (see attached)

 

[zigzag3143]

Despite best efforts, couldn't find a specific program from ATI that is just for uninstalling. So, downloaded 64-bit version again, used the uninstall feature in the catalyst control panel to uninstall everything (only the ATI Driver was listed as installed previously - I don't think the install manager was removed though). Rebooted. Desktop comes back up after reboot with about 800x600 resolution (smallest).

I run the install program as administrator, deselecting all the other junk except the bare minimum (Driver, ATI Catalyst Install manager and Microsoft Visual C++ 2008 SP1 Redistributable) and install.

Further, I thought this might be related to hibernation/sleep issues, so I manipulated power settings in the control panel to prevent sleep/hibernation. Hooray for 3 page thread on AMD forums that includes several similar issues regarding the 5770 and win 7 64 bit: AMD Game Forums - Hibernate / sleep problems on Windows 7 with Radeon HD 5770

Hey, guess what happened? (see attached)

Well at least this one doesnt point to you video driver. Have you run a system file check yet?
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results as you may have to run it more than once

Ken

 

[Makivante]

Verification 100% Complete. Windows Resource Protection did not find any integrity violations. Running it again for kicks. (same result)

As an aside, speedfan 4.40 is showing temps between 50-60 C for hardware that's monitored. (2 cpu fans, 3 internal fans)

 

[zigzag3143]

Verification 100% Complete. Windows Resource Protection did not find any integrity violations. Running it again for kicks. (same result)

As an aside, speedfan 4.40 is showing temps between 50-60 C for hardware that's monitored. (2 cpu fans, 3 internal fans)

Re SFC good

Do you have any more recent DMP's or is this on crash since the video driver?

 

[Jonathan_King]

All dmps point to GFX card or display driver. Read this article: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

[font=lucida console]
BugCheck 1000007E, {ffffffffc0000005, fffff88003a1e87e, fffff8800366d6d8, fffff8800366cf40}
BugCheck A, {fffff80002db7714, 2, 8, fffff80002db7714}
BugCheck 50, {fffff900c23d8ff8, 1, fffff960001939c6, 0}
BugCheck 3B, {c0000005, fffff800028988eb, fffff880028c3030, 0}
BugCheck 50, {fffff8800749aff8, 0, fffff800028cf610, 0}
BugCheck 116, {fffffa8001ac1210, fffff88003ea9ef0, 0, 2}
BugCheck 116, {fffffa8001a89010, fffff88003ee9ef0, 0, 2}
BugCheck 3B, {c0000005, fffff80002b8dc07, fffff88008a8bc20, 0}
BugCheck 3B, {c0000005, fffff80002bdb254, fffff88006500c70, 0}
BugCheck 50, {fffff8a008f57ff8, 1, fffff80002a74620, 0}
BugCheck A, {fffff80002daf714, 0, 8, fffff80002daf714}
BugCheck 116, {fffffa80053da010, fffff88002c0602c, 0, 2}
BugCheck 1E, {ffffffffc0000005, fffff80002ab0c69, 0, ffffffffffffffff}
BugCheck 50, {fffff900c1e8cff8, 1, fffff960000c39db, 0}
BugCheck 3B, {c0000005, fffff80002986c07, fffff880073bdc20, 0}
BugCheck 3B, {c0000005, fffff80002c06814, fffff8800524e810, 0}
BugCheck 50, {fffff900c1f75ff8, 1, fffff960001239cb, 0}
[/font]

 

[Makivante]

I've uploaded all I have - only one since the fresh install of the driver. It really only happens during gaming, and I'm a getting wary of doing damage to my system with all the crashes (although I need to figure out what's going on of course).

Any other diagnostic suggestions?

edit: Checking out J_King's article, ty.

 

[Makivante]

Well, using J_King's posted link, I have not had another BSOD in the last 2 days. However, I have had spontaneous reboots *without* a BSOD (about 3 in the last 48 hours).

Windows is telling me that their is a problem with my ATI driver, but still no download available from the solution center.

I find it a bit odd that my comp should be overheating considering it has working (spinning, visually verified) fans over the RAM block, above the CPU (external), seperate CPU fans for each core and a flow series (front of case intake and back output).

Not sure where to look since there are no new dmp files being created and the Event Viewer is oddly quiet (no error after a crash, whut?)

If anyone has ideas of where to look next, that'd be great - otherwise I am at least somewhat happy it works with the cover off for now. Thanks, as always.

 

[Makivante]

In June, it started to act uppity again, so I took it to a shop by my house that does free diagnostics and included the comments of those who helped me here (thanks!). Individually, everything passed the stress tests, so there conclusion was a failing motherboard. Replaced motherboard.

Apologies if necroing this thread is inappropriate - wanted to provide my end actions in case someone did a search. Thanks everyone for your help.

 

[Jonathan_King]

Apologize? On the contrary, thank you.

We appreciate reports like yours. Too few take a moment and update their thread.

Glad it's all sorted out!