BSOD on new PC

[Flik]

Hi guys,

Could you have a look at my dump files please.

New PC arrived on Saturday morning, installed W7 and drivers. I had a couple of BSOD yesterday so reinstalled last night. Loaded motherboard drivers first then graphics. Seemed ok for the remainder of last night and today but I've just had another.

64 bit W7
System came without operating system. Full retail copy installed.

Thanks in advance

 

[zigzag3143]

Hi guys,

Could you have a look at my dump files please.

New PC arrived on Saturday morning, installed W7 and drivers. I had a couple of BSOD yesterday so reinstalled last night. Loaded motherboard drivers first then graphics. Seemed ok for the remainder of last night and today but I've just had another.

64 bit W7
System came without operating system. Full retail copy installed.

Thanks in advance

This crash was fairly straight forward. Its cause, your video driver.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Let us know if you need further assistance with this

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


Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080110-13884-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Sun Aug  1 15:46:33.098 2010 (GMT-4)
System Uptime: 0 days 11:03:35.622
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

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+4a179 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


OVERLAPPED_MODULE: Address regions for 'WUDFRd' and 'spsys.sys' overlap

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5ba2952f03b3dd40
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  b

EXCEPTION_RECORD:  fffff88002d1acd8 -- (.exr 0xfffff88002d1acd8)
ExceptionAddress: fffff88003b0c179 (atikmdag+0x000000000004a179)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002d1ad80 -- (.trap 0xfffff88002d1ad80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003e12f10 rbx=0000000000000000 rcx=fffffa8005d12720
rdx=fffffa8004fd01c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003b0c179 rsp=fffff88002d1af10 rbp=fffff88002d1afb0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff88002d1afb0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
atikmdag+0x4a179:
fffff880`03b0c179 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eb832e to fffff80002ec05d0

STACK_TEXT:  
fffff880`02d19dc8 fffff800`02eb832e : 00000000`00000008 fffffa80`0563e680 fffff880`02d1a540 fffff800`02eed524 : nt!KeBugCheck
fffff880`02d19dd0 fffff800`02ee62ed : fffff800`030ceb88 fffff800`03007a40 fffff800`02e50000 fffff880`02d1acd8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02d19e00 fffff800`02eed950 : fffff800`0300fb24 fffff880`02d19e78 fffff880`02d1acd8 fffff800`02e50000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02d19e30 fffff800`02efa8df : fffff880`02d1acd8 fffff880`02d1a540 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x410
fffff880`02d1a510 fffff800`02ebfc42 : fffff880`02d1acd8 00000000`00000000 fffff880`02d1ad80 fffff880`02d1b388 : nt!KiDispatchException+0x16f
fffff880`02d1aba0 fffff800`02ebe54a : fffffa80`0509d000 fffff880`03b45241 fffffa80`0509d000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02d1ad80 fffff880`03b0c179 : fffffa80`05346730 0000000f`008e8000 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`02d1af10 fffffa80`05346730 : 0000000f`008e8000 00000000`00000000 00000000`00000001 00000000`00000000 : atikmdag+0x4a179
fffff880`02d1af18 0000000f`008e8000 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`04ff0740 : 0xfffffa80`05346730
fffff880`02d1af20 00000000`00000000 : 00000000`00000001 00000000`00000000 fffffa80`04ff0740 00000000`c0000001 : 0xf`008e8000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+4a179
fffff880`03b0c179 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  atikmdag+4a179

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33da58

FAILURE_BUCKET_ID:  X64_0x1E_atikmdag+4a179

BUCKET_ID:  X64_0x1E_atikmdag+4a179

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

Old drivers

speedfan.sys        fffff880`014dd000    fffff880`014e4000    0x00007000    0x45168798    9/24/2006 09:26:48                        
usbfilter.sys        fffff880`04262000    fffff880`0426e000    0x0000c000    0x49d5f587    4/3/2009 07:39:51                        
AtiPcie.sys        fffff880`015f2000    fffff880`015fa000    0x00008000    0x4a005486    5/5/2009 11:00:22                        
spldr.sys        fffff880`014d5000    fffff880`014dd000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`00c2a000    fffff880`00c35000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

 

[Flik]

Thank you for the quick reply.

The latest video driver is installed. As this was a new PC this was the first and only driver installed. I shall remove and then run drive sweeper and reinstall and report back.

Is it worth trying an earler driver version if I still get the same?

 

[Flik]

I removed video drivers last night ran drive sweeper and installed newest ones.

On boot up this morning everything froze so had to do a restart. On booting I had another blue screen.

Dumps attached.

 

[ttran]

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

Do that instead!

 

[Flik]

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

Do that instead!

Ok, here you go. Apologies if I didn't do it correctly the last time.

 

[ttran]

What antivirus software are you using?

System Uptime: 0 days [COLOR=Red][B]0:00:29.948[/B][/COLOR]

It occur when you start your computer, please try to do a clean boot to see if it helps:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Although I'm not so sure about this, but you might want to uninstall ATi catalyst control center. It is known for causing BSODs on some system.
-Download the driver ONLY (not the whole Catalyst Control Center program) from http://www.ati.com
-Uninstall all your ATI stuff from Control Panel...Programs...Uninstall a program
-Install the downloaded driver

BUGCHECK SUMMARY:

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.036\080210-14040-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`0309be50
Debug session time: Mon Aug  2 14:19:21.527 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:29.948
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002eaa723}

Probably caused by : hardware ( nt!AlpcpLookasidePacketCallbackRoutine+73 )

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

Regard,

Tuan

 

[Flik]

I'm using MSE.

I've only had 1 BSOD on startup all the rest have been after I've been using the PC for quite a few hours.

A couple of times I've had the screen freeze and the display go to what I can only discribe as various shades of blue lines covering the entire screen then the BSOD.

I know it's a new system but could the graphics card be damaged? Or would it just not work at all if it was that?

Thanks again for your help.

*Edit*
I've uninstalled the catalyst control centre, ran drive sweeper and reinstalled just the video driver.

 

[ttran]

Good! let us know if you need more help

 

[Flik]

Just had another, thats with just the video driver installed.

Files attached.

 

[ttran]

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Flik]

Nothing in device manager, sfc /scannow came back ok. I ran memtest over night...9 passes no errors and still the blue screens. 3 after my last post.

Anyway, I've just been on the phone to the company that I bought it from and it's been RMA'd and going back today for testing etc

If it had just started happening after having the PC for a while then I would have stuck with it but the fact that they have been happening from the moment I got the PC on Saturday then something is wrong somewhere and I think it's up to them to sort it out.

Thanks again for your help, much appreciated.

 

[Flik]

Ok, quick update.

Sent machine back last week...turned out to be faulty RAM. They replaced it and it's now working perfectly

Thanks again for the help.

 

[Jonathan_King]

Thanks for the report!

Glad it's working now.

 

[Flik]

Another update....I spoke too soon, blue screens started again so I'm sending it back and getting a refund.

What is it with "new" computers these days they just don't seem to be as reliable as they used to be.

I'm now back on a temporary 6 year old celeron that is so slow I keep thinking it's about to stop but it works...has not had one thing go wrong with it since the day it was bought. Hmmm that's tempting fate a bit

 

[ttran]

I agree! hard question to answer but yes, new computer these days are not as reliable as before. I have heard somewhere a joke that, in order not to have BSODs, you should not install any 3rd party software, far away from your computer :roflmao: