BSOD: upon GPU addition

Hi ya'll,

Doing new system build. Basiclly everything is working fine, except when I added a MSI ATI Radeon 5450 based GPU card (specifically a R5450-MD512H) -- had ideas of playing with Crossfire. No go, BSOD until I remove the card. BSOD is consistant in that it occurs very shortly after the boot animation completes. The SSD boot the system very very fast so it is hard to catch the BSOD text!

The BSOD text appears on the monitor that is attached to the new GPU card. The mobo integrated HD4290 does not display anything, but I do get POST video on both monitors attached to the 5450 GPU.

System:

MSI 890GXM-G65 mobo, Phenom II 555BE with one extra core unlocked (does not like 4th core), 4gb ram, OCZ Agility 60GB SSD, Seagate 1.5tb data drive.

Mobo has built in ATI Radeon HD4290.

Tried various obvious things... stock speed (no OC), no unlocked cores, made no difference. I had a thought that it might be power supply as I reused a old eMachines ATX case that had a 300 watt junker PSU in it, so i replaced it with a OCZ 550 watt new PSU... no change.

OS is Win7 Ultimate, retail box, 32 bit.

The attached data files are prepared per the BSOD posting instructions. Note the system health report is *without* the 5450 GPU installed since the system won't complete boot with it installed.

I am a bit at a loss here --- basic hardware function (dead or alive) is somewhat confirmed by the fact the PCI-E16 card does produce an output, albeit text only. BTW< I did try both PCI Express x16 slots on this mobo, no difference.

Next step; I have gone into msconfig / boot tab and set up nogui boot.... see what i get.

Ideas? Go get a different GPU card? Open to that idea, this card might be an out of the box lemon I suppose!

Thanks;

Don

The most important file is missing. Be sure to run as administrator shown in number 2
https://www.sevenforums.com/crashes-d...tructions.html

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Code:

Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Dgates_BSOD_As_Admin.zip[1].zip\Windows7_BSOD_jcgriff2\081310-14960-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a40000 PsLoadedModuleList = 0x82b88810
Debug session time: Fri Aug 13 18:17:46.832 2010 (GMT-4)
System Uptime: 0 days 0:00:08.205
Loading Kernel Symbols
...............................................................
..........................
Loading User Symbols
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000007E, {c0000005, 82ad1dc6, 8cf5d070, 8cf5cc50}
 
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : atikmpag.sys ( atikmpag+7c0b )
 
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: c0000005, The exception code that was not handled
Arg2: 82ad1dc6, The address that the exception occurred at
Arg3: 8cf5d070, Exception Record Address
Arg4: 8cf5cc50, 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: 
nt!IoGetAttachedDevice+c
82ad1dc6 8b4810          mov     ecx,dword ptr [eax+10h]
 
EXCEPTION_RECORD:  8cf5d070 -- (.exr 0xffffffff8cf5d070)
ExceptionAddress: 82ad1dc6 (nt!IoGetAttachedDevice+0x0000000c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000010
Attempt to read from address 00000010
 
CONTEXT:  8cf5cc50 -- (.cxr 0xffffffff8cf5cc50)
eax=00000000 ebx=865cdd00 ecx=00000018 edx=8cf5d148 esi=00000000 edi=853cd8c0
eip=82ad1dc6 esp=8cf5d138 ebp=8cf5d138 iopl=0         nv up ei pl nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210207
nt!IoGetAttachedDevice+0xc:
82ad1dc6 8b4810          mov     ecx,dword ptr [eax+10h] ds:0023:00000010=????????
Resetting default scope
 
CUSTOMER_CRASH_COUNT:  1
 
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:  00000000
 
EXCEPTION_PARAMETER2:  00000010
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba8718
Unable to read MiSystemVaType memory at 82b88160
00000010 
 
FOLLOWUP_IP: 
atikmpag+7c0b
90074c0b ??              ???
 
BUGCHECK_STR:  0x7E
 
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
 
LOCK_ADDRESS:  82ba5f60 -- (!locks 82ba5f60)
 
Resource @ nt!PiEngineLock (0x82ba5f60)    Available
 
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
 
 
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
 
1 total locks
 
PNP_TRIAGE: 
Lock address  : 0x82ba5f60
Thread Count  : 0
Thread address: 0x00000000
Thread wait   : 0x0
 
LAST_CONTROL_TRANSFER:  from 90074c0b to 82ad1dc6
 
STACK_TEXT:  
8cf5d138 90074c0b 00000000 86632940 001a0018 nt!IoGetAttachedDevice+0xc
WARNING: Stack unwind information not available. Following frames may be wrong.
8cf5d1d8 9007e898 86632ebc 00000000 86632940 atikmpag+0x7c0b
8cf5d1ec 90080021 865cdd00 8cf5d880 9008b4b3 atikmpag+0x11898
8cf5d1f8 9008b4b3 86632940 86618780 86631a68 atikmpag+0x13021
8cf5d880 900feed0 85934b60 8cf5d8f4 86631a68 atikmpag+0x1e4b3
8cf5d89c 900feffb 86631a68 85934b60 8cf5d8f4 dxgkrnl+0x58ed0
8cf5d960 82a54767 866006f8 85934b60 85933678 dxgkrnl+0x58ffb
8cf5d97c 82bef7cb 85934b60 900fef35 00000004 nt!PpvUtilCallAddDevice+0x19
8cf5d9c4 82be8302 866006f8 900fef35 00000002 nt!PnpCallAddDevice+0xb9
8cf5da98 82be788e 85933678 8cf5dcc8 00000000 nt!PipCallDriverAddDevice+0x565
8cf5dc94 82bcba42 853c9ab8 865d9ae0 8cf5dcc8 nt!PipProcessDevNodeTree+0x15d
8cf5dcd4 82a53f9c 865d9ae0 82ba3e80 853c54c0 nt!PiProcessStartSystemDevices+0x6d
8cf5dd00 82aadf3b 00000000 00000000 853c54c0 nt!PnpDeviceActionWorker+0x241
8cf5dd50 82c4e6d3 00000001 b859f896 00000000 nt!ExpWorkerThread+0x10d
8cf5dd90 82b000f9 82aade2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  atikmpag+7c0b
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: atikmpag
 
IMAGE_NAME:  atikmpag.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d52b
 
STACK_COMMAND:  .cxr 0xffffffff8cf5cc50 ; kb
 
FAILURE_BUCKET_ID:  0x7E_atikmpag+7c0b
 
BUCKET_ID:  0x7E_atikmpag+7c0b
 
Followup: MachineOwner
---------
 
1: kd> lmtsmn
start    end        module name
83a36000 83a7e000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8fc12000 8fc6c000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
9005c000 9006d000   amdppm   amdppm.sys   Mon Jul 13 19:11:03 2009 (4A5BBF07)
83b87000 83b90000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8fc6c000 8fc70100   aswRdr   aswRdr.SYS   Mon Jun 28 16:33:12 2010 (4C290708)
83800000 83826c00   aswSP    aswSP.SYS    Mon Jun 28 16:37:28 2010 (4C290808)
83bf6000 83bffc00   aswTdi   aswTdi.SYS   Mon Jun 28 16:37:50 2010 (4C29081E)
83b5b000 83b64000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
83b64000 83b87000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
9040e000 909f9000   atikmdag atikmdag.sys Tue Jul 06 21:34:15 2010 (4C33D997)
9006d000 900a6000   atikmpag atikmpag.sys Tue Jul 06 21:15:23 2010 (4C33D52B)
8b1ec000 8b1f4000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:16 2009 (4A005480)
8ae26000 8ae2d000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8fdf1000 8fdff000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
83857000 8385f000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
8ae00000 8ae1f000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
838a1000 8394c000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8afaa000 8afcf000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8385f000 838a1000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8b003000 8b060000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8afcf000 8afdc000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8fd75000 8fdd9000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
8fdd9000 8fdf1000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8fd69000 8fd75000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8b1db000 8b1ec000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8afdc000 8afe5000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b1f4000 8b1ff000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8afe5000 8aff6000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
900a6000 9015d000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
9015d000 90196000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
83bc4000 83bd5000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
83b90000 83bc4000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8b06e000 8b077000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8b1a9000 8b1db000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8b383000 8b3b4000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8b236000 8b236680   giveio   giveio.sys   Wed Apr 03 22:33:25 1996 (316334F5)
82a09000 82a40000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8b1a1000 8b1a9000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80bd0000 80bd8000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8af97000 8afaa000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8b16c000 8b191000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8383b000 83846000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
83b45000 83b5b000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
83a1d000 83a28000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
83a87000 83a8f000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8af6c000 8af97000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8fd5f000 8fd69000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8b191000 8b1a1000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8b077000 8b12e000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8fcc9000 8fcd7000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8fc71000 8fca3000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8b12e000 8b16c000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
83a28000 83a36000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8fd55000 8fd5f000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82a40000 82e50000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
8ae3d000 8af6c000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8ae1f000 8ae26000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
8fcaa000 8fcc9000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
83ac4000 83ad5000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
83a8f000 83ab9000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
83b30000 83b37000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
83b37000 83b45000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b060000 8b06e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
83846000 83857000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8fd14000 8fd55000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8aff6000 8affe000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
83a0d000 83a15000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
83a15000 83a1d000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8b209000 8b236000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8fcd7000 8fcf1000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
8b208000 8b209000   speedfan speedfan.sys Wed Jun 15 10:55:53 2005 (42B04179)
8b200000 8b208000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8b23a000 8b383000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
839e2000 839ed000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
839cb000 839e2000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8fd04000 8fd14000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
9003b000 9005c000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
83ab9000 83ac4000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8ae2d000 8ae39000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
83bd5000 83bf6000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8b3b4000 8b3bc380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
83ad5000 83ae5000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
83ae5000 83b30000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8b3bd000 8b3fc000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8fcf1000 8fd04000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
83a00000 83a0d000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8394c000 839bd000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
839bd000 839cb000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8fca3000 8fcaa000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
83a7e000 83a87000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)

Outdated Drivers
giveio.sys Wed Apr 03 22:33:25 1996
speedfan.sys Wed Jun 15 10:55:53 2005
AtiPcie.sys Tue May 05 11:00:16 2009
amdxata.sys Tue May 19 13:57:35 2009

Solution
The report indicates
Atikmpag.sys as the most likely cause of your BSOD. It must be replaced with a more current version
Atikmpag.sys file description
Productname: AMD driver
Description: AMD multi-vendor Miniport Driver
Company: Advanced Micro Devices, Inc.

Insufficient Disc Space must be addressed. Make sure that you have sufficient space on your hard drives. I would defrag and check for errors.
Driver Atikmpag.sys must be updated. The other drivers can be put on hold until you are certain that other suggested action has not solved the problem.
Go to Device Manager and make sure that the Video Card does not have any yellow warnings markers, showing a problem
A memory test should be taken using memtest86. Run for 6 passes or overnight. Take a good known RAM stick to test all the MB slots. This test can be delayed until after we are certain that the driver from Advaced Microdevices does not solve the problem
http://memtest.org/
If any remote control devices are in use they should be uninstalled.
Take a SFC scan to check for corruption
http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html For Seven or Vista
Run your antivirus to make sure a virus is not in hiding and the cause of the problem.

It is my opinion that the named Driver from AMD is the most likely cause and should be given priority. Remember these reports are a map to the solution, but leave us just short of the goal. You may experience additional BSOD, which we will analyze, but your problem will be resolved.

I am glad that I could help. Come back any time and tell your friends about the help available at our Forum.