Crashing after new set up

Welcome to the forum, happycamper1. I will look at your dmp and be right back.

Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

You have a stop error code of 1E'

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

The dmp file does not pinpoint the cause, so we are going to have to dig a little

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\062810-22230-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol  information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList =  0xfffff800`02c89e50
Debug session time: Mon Jun 28 19:24:55.489 2010 (GMT-4)
System Uptime: 0 days 21:15:21.770
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                              *
*                        Bugcheck Analysis                                     *
*                                                                              *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e  )

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

Let's start with drivers. You have two older drivers that need to be updated. I cant say these driver caused the BSOD, but old drivers do not work well with Win7 in general.

amdxata.sys Tue May 19 13:56:59 2009 - Amdxata.sys with description Storage Filter Driver is a driver file from company Advanced Micro Devices belonging to product Storage Filter Driver. Try the Ausus website for this driver and then try the AMD website.

cmudax3.sys Wed Dec 03 01:32:46 2009 - This is a Windows Media audio driver. See if there is a newer driver available. Try the Asus website for this driver.

Update these drivers and we will see where we are.

Thanks for filling out your system specs!

Too many times, BSOD analysis is trial and error. When a dmp file does not give us a definitive answer we have to look at possible causes. My method is to start with the most simple and see if that solves the problem. If it doesn't we go further.

I cannot really say in your case. Windows 7 does not like older drivers. It is a totally new OS and older drivers many times do not work properly. Sometimes one has to uninstall older software or even replace older hardware.

Try updating these drivers and run you system. We will see if that fixed the problem or we will look at the next BSOD dmp. Sometimes there is a magic answer and sometimes there isn't. Unfortunately, this is one of the "isn't's".

Very good; I'm glad you updated the sound driver. Did you reboot after you updated it? If not, please do so.

I'm not sure I understand your question.

We do not recommend using Windows Update nor Device Manager to update drivers in most instances. We recommend going to the manufacturers' sites, download the new driver, and install it. In this case, try the Asus website for this driver and if you can't find it there, try the AMD website.

Let us know. I am going to bed shortly. However, if you need further help or have questions, please post. One of the other BSOD team members will pick it up.

I hope to see you tomorrow with a smooth running system. :)