BSOD Help

[jsparry]

Ok BSOD within about 1 min on being on. Then got bsod just after Logo screen before you see Login. this happened 3 times.

DMP files attached...

Ignore the Date. I reset the BIOS and tried changed the Batt.

 

[jsparry]

Any ideas,

I just dont know where to start or what parts to try and replace 1st.

 

[Jonathan_King]

This one points to your graphics drivers:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_123101-26800-01.zip\123101-26800-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c43e50
Debug session time: Mon Dec 31 20:03:40.803 2001 (GMT-4)
System Uptime: 0 days 0:00:16.660
Loading Kernel Symbols
...............................................................
................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002a96183}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+a617 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a96183, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cae0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02a96183 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff88002dea1b0 -- (.trap 0xfffff88002dea1b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff98001540fb0 rbx=0000000000000000 rcx=fffff980014ccc00
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004663617 rsp=fffff88002dea348 rbp=fffffa8003201a20
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000014 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atikmdag+0xa617:
fffff880`04663617 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a75b69 to fffff80002a76600

STACK_TEXT:  
fffff880`02de9bf8 fffff800`02a75b69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02de9c00 fffff800`02a747e0 : 00000000`80000000 fffff980`032ccee0 00000000`0004001f 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02de9d40 fffff800`02a96183 : 00100000`1d4a7963 00000000`00000000 00000000`00000000 fffffa80`01908788 : nt!KiPageFault+0x260
fffff880`02de9ed0 fffff800`02a52fcf : 00000000`00000001 fffff800`02c02b40 00000000`00000000 fffff880`00000000 : nt!IopCompleteRequest+0xae3
fffff880`02de9fa0 fffff800`02a29b95 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`02dea020 fffff800`02a91b24 : 00000000`00000058 00000000`00000040 05d00000`1d4a78c2 00000000`00000002 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`02dea050 fffff800`02a746ee : 00000000`00000000 fffffa80`03d6e000 fffffa80`02477d00 fffff880`00000011 : nt!MmAccessFault+0x1844
fffff880`02dea1b0 fffff880`04663617 : fffff880`046850cc fffffa80`03d61000 fffff880`048c0ba8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`02dea348 fffff880`046850cc : fffffa80`03d61000 fffff880`048c0ba8 00000000`00000000 fffffa80`03d6e000 : atikmdag+0xa617
fffff880`02dea350 fffffa80`03d61000 : fffff880`048c0ba8 00000000`00000000 fffffa80`03d6e000 fffff980`032caea0 : atikmdag+0x2c0cc
fffff880`02dea358 fffff880`048c0ba8 : 00000000`00000000 fffffa80`03d6e000 fffff980`032caea0 fffff880`0466dcd9 : 0xfffffa80`03d61000
fffff880`02dea360 00000000`00000000 : fffffa80`03d6e000 fffff980`032caea0 fffff880`0466dcd9 fffffa80`03d6e000 : atikmdag+0x267ba8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+a617
fffff880`04663617 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  atikmdag+a617

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49f199cd

FAILURE_BUCKET_ID:  X64_0xA_VRF_atikmdag+a617

BUCKET_ID:  X64_0xA_VRF_atikmdag+a617

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

2: kd> lmsmn
start             end                 module name
fffff880`02bb1000 fffff880`02bef000   1394ohci 1394ohci.sys
fffff880`00e9e000 fffff880`00ef5000   ACPI     ACPI.sys    
fffff880`03a00000 fffff880`03a8a000   afd      afd.sys     
fffff880`04316000 fffff880`0432b000   amdppm   amdppm.sys  
fffff880`00e33000 fffff880`00e3e000   amdxata  amdxata.sys 
fffff880`04338000 fffff880`04340000   ASACPI   ASACPI.sys  
fffff880`042ea000 fffff880`042f0000   AsIO     AsIO.sys    
fffff880`00e00000 fffff880`00e09000   atapi    atapi.sys   
fffff880`00e09000 fffff880`00e33000   ataport  ataport.SYS 
fffff880`04659000 fffff880`04b7b000   atikmdag atikmdag.sys
fffff880`03b23000 fffff880`03b2a000   Beep     Beep.SYS    
fffff880`042d9000 fffff880`042ea000   blbdrive blbdrive.sys
fffff880`03ac3000 fffff880`03aed000   cdrom    cdrom.sys   
fffff880`00c98000 fffff880`00d58000   CI       CI.dll      
fffff880`011d0000 fffff880`01200000   CLASSPNP CLASSPNP.SYS
fffff880`00c3a000 fffff880`00c98000   CLFS     CLFS.SYS    
fffff880`012c9000 fffff880`0133c000   cng      cng.sys     
fffff880`015ee000 fffff880`015fc000   crashdmp crashdmp.sys
fffff880`04238000 fffff880`042bb000   csc      csc.sys     
fffff880`042bb000 fffff880`042d9000   dfsc     dfsc.sys    
fffff880`02ba2000 fffff880`02bb1000   discache discache.sys
fffff880`0123a000 fffff880`01250000   disk     disk.sys    
fffff880`01000000 fffff880`01009000   dump_atapi dump_atapi.sys
fffff880`013ed000 fffff880`013f9000   dump_dumpata dump_dumpata.sys
fffff880`01009000 fffff880`0101c000   dump_dumpfve dump_dumpfve.sys
fffff880`03c59000 fffff880`03d4d000   dxgkrnl  dxgkrnl.sys 
fffff880`03d4d000 fffff880`03d93000   dxgmms1  dxgmms1.sys 
fffff880`0432b000 fffff880`04338000   fdc      fdc.sys     
fffff880`00e8a000 fffff880`00e9e000   fileinfo fileinfo.sys
fffff880`00e3e000 fffff880`00e8a000   fltmgr   fltmgr.sys  
fffff880`0134d000 fffff880`01357000   Fs_Rec   Fs_Rec.sys  
fffff880`01200000 fffff880`0123a000   fvevol   fvevol.sys  
fffff880`01357000 fffff880`013a1000   fwpkclnt fwpkclnt.sys
fffff880`043ed000 fffff880`043fa000   GEARAspiWDM GEARAspiWDM.sys
fffff800`02fe2000 fffff800`0302b000   hal      hal.dll     
fffff880`043c9000 fffff880`043ed000   HDAudBus HDAudBus.sys
fffff880`015e5000 fffff880`015ee000   hwpolicy hwpolicy.sys
fffff800`00bca000 fffff800`00bd4000   kdcom    kdcom.dll   
fffff880`012af000 fffff880`012c9000   ksecdd   ksecdd.sys  
fffff880`01590000 fffff880`015bb000   ksecpkg  ksecpkg.sys 
fffff880`00c19000 fffff880`00c26000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll
fffff880`00fe5000 fffff880`00fff000   mountmgr mountmgr.sys
fffff880`03aed000 fffff880`03b1a000   MpFilter MpFilter.sys
fffff880`03b88000 fffff880`03b93000   Msfs     Msfs.SYS    
fffff880`00efe000 fffff880`00f08000   msisadrv msisadrv.sys
fffff880`01251000 fffff880`012af000   msrpc    msrpc.sys   
fffff880`02b97000 fffff880`02ba2000   mssmbios mssmbios.sys
fffff880`015d3000 fffff880`015e5000   mup      mup.sys     
fffff880`0143e000 fffff880`01530000   ndis     ndis.sys    
fffff880`02adf000 fffff880`02aee000   netbios  netbios.sys 
fffff880`02a55000 fffff880`02a9a000   netbt    netbt.sys   
fffff880`01530000 fffff880`01590000   NETIO    NETIO.SYS   
fffff880`03b93000 fffff880`03ba4000   Npfs     Npfs.SYS    
fffff880`02b8b000 fffff880`02b97000   nsiproxy nsiproxy.sys
fffff800`02a06000 fffff800`02fe2000   nt       ntkrnlmp.exe
fffff880`0102d000 fffff880`011d0000   Ntfs     Ntfs.sys    
fffff880`03b1a000 fffff880`03b23000   Null     Null.SYS    
fffff880`02a00000 fffff880`02a51380   nvmf6264 nvmf6264.sys
fffff880`0434c000 fffff880`04357000   nvsmu    nvsmu.sys   
fffff880`02aa3000 fffff880`02ac9000   pacer    pacer.sys   
fffff880`00f48000 fffff880`00f5d000   partmgr  partmgr.sys 
fffff880`00f08000 fffff880`00f3b000   pci      pci.sys     
fffff880`00fce000 fffff880`00fd5000   pciide   pciide.sys  
fffff880`00fd5000 fffff880`00fe5000   PCIIDEX  PCIIDEX.SYS 
fffff880`0133c000 fffff880`0134d000   pcw      pcw.sys     
fffff880`00c26000 fffff880`00c3a000   PSHED    PSHED.dll   
fffff880`02b3a000 fffff880`02b8b000   rdbss    rdbss.sys   
fffff880`03b6d000 fffff880`03b76000   RDPCDD   RDPCDD.sys  
fffff880`03b76000 fffff880`03b7f000   rdpencdd rdpencdd.sys
fffff880`03b7f000 fffff880`03b88000   rdprefmp rdprefmp.sys
fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys
fffff880`04340000 fffff880`0434c000   serenum  serenum.sys 
fffff880`02aee000 fffff880`02b0b000   serial   serial.sys  
fffff880`015cb000 fffff880`015d3000   spldr    spldr.sys   
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys   
fffff880`03bc2000 fffff880`03bcf000   TDI      TDI.SYS     
fffff880`03ba4000 fffff880`03bc2000   tdx      tdx.sys     
fffff880`02b26000 fffff880`02b3a000   termdd   termdd.sys  
fffff880`042f0000 fffff880`04316000   tunnel   tunnel.sys  
fffff880`043b8000 fffff880`043c9000   usbehci  usbehci.sys 
fffff880`04357000 fffff880`04362000   usbohci  usbohci.sys 
fffff880`04362000 fffff880`043b8000   USBPORT  USBPORT.SYS 
fffff880`00f3b000 fffff880`00f48000   vdrvroot vdrvroot.sys
fffff880`03b2a000 fffff880`03b38000   vga      vga.sys     
fffff880`03b38000 fffff880`03b5d000   VIDEOPRT VIDEOPRT.SYS
fffff880`015bb000 fffff880`015cb000   vmstorfl vmstorfl.sys
fffff880`00f5d000 fffff880`00f72000   volmgr   volmgr.sys  
fffff880`00f72000 fffff880`00fce000   volmgrx  volmgrx.sys 
fffff880`013a1000 fffff880`013ed000   volsnap  volsnap.sys 
fffff880`02ac9000 fffff880`02adf000   vwififlt vwififlt.sys
fffff880`02b0b000 fffff880`02b26000   wanarp   wanarp.sys  
fffff880`03b5d000 fffff880`03b6d000   watchdog watchdog.sys
fffff880`00d58000 fffff880`00dfc000   Wdf01000 Wdf01000.sys
fffff880`00c00000 fffff880`00c0f000   WDFLDR   WDFLDR.SYS  
fffff880`02a9a000 fffff880`02aa3000   wfplwf   wfplwf.sys  
fffff880`00ef5000 fffff880`00efe000   WMILIB   WMILIB.SYS

 

[jsparry]

I still got the spare gfx crd in there atm.

Should i put the good one back in?

 

[jsparry]

Ok im think im going to try a format.

Maybe with a clean install we can identify what device is the cause.

Unless you have any other ideas?

 

[jsparry]

With verifier on should the system run perfectly? (once its fixed..)


or could it bsod even if everything is ok?

 

[jsparry]

Can you check these one please:

 

[Jonathan_King]

I notice two things. QButton was running in both cases. I recommend uninstalling your Quick Button software.

The other thing I notice is that both dmps point to ASACPI.sys. I recommend uninstalling the AIsuite and installing a fresh copy.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 09:49:55.855 2010 (GMT-4)
System Uptime: 0 days 0:01:02.541
BugCheck C4, {f6, 1a8, fffffa8008c8e270, fffff88003ed2257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  QButton.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 09:51:59.143 2010 (GMT-4)
System Uptime: 0 days 0:01:31.203
BugCheck C4, {f6, 1a8, fffffa8008af1560, fffff88003f1f257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  QButton.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[jsparry]

Thanks Jonathan,

The fresh install is just about to finish installing.

Should i turn verifier on before i try to manually add any extra drivers?

 

[jsparry]

Ok..... Think im getting some where.

The fresh install is done. Iv'e turned driver verifier on and its working...

No BSOD yet..

Only got 3 devices that aint installed.

Wifi card
and Unknown device. (think this is the thing thats installed via the probe thing. )
and a Coprocessor.


Should i installed the things one at a time of leave it for a bit longer?

 

[jsparry]

I let windows update install the Wifi driver and as it was installing it BSOD.

More

 

[jsparry]

Any ideas what i should do?

i dont have a clue anymore

 

[Jonathan_King]

I have to suspect hardware. You may try to run Memtest for the full 5 passes, but I actually suspect your motherboard is failing.

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 12 12:45:10.560 2010 (GMT-4)
System Uptime: 0 days 0:00:13.074
BugCheck A, {0, 2, 0, fffff800028eca83}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 12 12:48:21.244 2010 (GMT-4)
System Uptime: 0 days 0:01:14.758
BugCheck A, {fffff80002b98046, 2, 0, fffff800028a9f62}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 12 12:57:27.652 2010 (GMT-4)
System Uptime: 0 days 0:07:14.509
BugCheck 7F, {8, 80050031, 6f8, fffff8000288ce72}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  linpack_xeon64
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 12 12:28:01.223 2010 (GMT-4)
System Uptime: 0 days 0:09:22.127
BugCheck 1A, {411, fffff6fc40008100, 6910000003334860, bffff6fc40008101}
Probably caused by : fileinfo.sys ( fileinfo!FIPreReadWriteCallback+185 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
[/font]

 

[jsparry]

Ok i've started that. I'll let you know the outcome.

Many thanks For all your help Jonathan.

Would have been very lost without you .

 

[jsparry]

Hi all,


Just to let you know i've sorted the problem.

Replaced the mobo and its all working great now....


Many Thanks For all your help...

 

[Jonathan_King]

Hi all,


Just to let you know i've sorted the problem.

Replaced the mobo and its all working great now....


Many Thanks For all your help...

Great, thanks a lot for the report!

We need feedback such as yours not only for morale boost, but also so we know how to help people in the future.

I'm glad it's solved.