BleepingComputer.com: BSOD during normal startup only starts in safe mode

all these dumps are a few months old...


==================================================
Dump File : Mini032811-01.dmp
Crash Time : 3/28/2011 11:37:18 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf031465
Parameter 3 : 0xebe48b00
Parameter 4 : 0x00000000
Caused By Driver : ialmdnt5.dll
Caused By Address : ialmdnt5.dll+11465
File Description : Controller Hub for Intel Graphics Driver
Product Name : Intel Graphics Accelerator Drivers for Windows NT®
Company : Intel Corporation
File Version : 6.14.10.3762
Processor : 32-bit
Computer Name :
Full Path : D:\Windows\MiniDump\Mini032811-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 110,592
==================================================

==================================================
Dump File : Mini022211-01.dmp
Crash Time : 2/22/2011 6:09:07 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x8572bb18
Parameter 2 : 0x872d8308
Parameter 3 : 0x84a2fa30
Parameter 4 : 0x00000001
Caused By Driver : ati3duag.dll
Caused By Address : ati3duag.dll+58300
File Description : ati3duag.dll
Product Name : ATI Technologies Inc. Radeon DirectX Universal Driver
Company : ATI Technologies Inc.
File Version : 6.14.10.0806
Processor : 32-bit
Computer Name :
Full Path : D:\Windows\MiniDump\Mini022211-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 68,000
==================================================

==================================================
Dump File : Mini012911-01.dmp
Crash Time : 1/29/2011 1:05:26 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x00000000
Parameter 3 : 0xa2ddfad0
Parameter 4 : 0x00000000
Caused By Driver : ati2mtag.sys
Caused By Address : ati2mtag.sys+27262e
File Description : ATI Radeon WindowsNT Miniport Driver
Product Name : ATI Radeon WindowsNT Miniport Driver
Company : ATI Technologies Inc.
File Version : 6.14.10.7157
Processor : 32-bit
Computer Name :
Full Path : D:\Windows\MiniDump\Mini012911-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 114,688
==================================================

==================================================
Dump File : Mini012111-01.dmp
Crash Time : 1/21/2011 10:33:05 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xad5e2a6a
Parameter 2 : 0x00000002
Parameter 3 : 0x00000008
Parameter 4 : 0xad5e2a6a
Caused By Driver : viahduaa.sys
Caused By Address : viahduaa.sys+c0a6a
File Description : VIA High Definition Audio Function Driver
Product Name : VIA High Definition Audio Driver
Company : VIA Technologies, Inc.
File Version : 6,0,01,1570 built by: WinDDK
Processor : 32-bit
Computer Name :
Full Path : D:\Windows\MiniDump\Mini012111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini012011-01.dmp
Crash Time : 1/20/2011 8:10:25 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 0x00000000
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ati2mtag.sys
Caused By Address : ati2mtag.sys+2730d3
File Description : ATI Radeon WindowsNT Miniport Driver
Product Name : ATI Radeon WindowsNT Miniport Driver
Company : ATI Technologies Inc.
File Version : 6.14.10.7157
Processor : 32-bit
Computer Name :
Full Path : D:\Windows\MiniDump\Mini012011-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 94,208
==================================================
thats the bluescreen one as for the other ill have to restart here

Does that mean that you no longer get BSODs?

Louis

ok heres the last one

Vino's Event Viewer v01c run on Windows XP in English
Report run at 25/04/2011 5:39:57 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 26/03/2011 6:36:38 PM
Type: error Category: 0
Event: 10005 Source: MsiInstaller
Product: Microsoft Silverlight -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2711. The arguments are: Complete4.0.60129.0, ,

Log: 'Application' Date/Time: 26/03/2011 6:36:19 PM
Type: error Category: 0
Event: 10005 Source: MsiInstaller
Product: Microsoft Silverlight -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2711. The arguments are: Complete4.0.60129.0, ,

Log: 'Application' Date/Time: 23/03/2011 3:21:56 AM
Type: error Category: 0
Event: 1012 Source: Windows Product Activation
Due to hardware changes on this computer, you will need to reactivate your Windows product.

Log: 'Application' Date/Time: 02/03/2011 6:35:04 PM
Type: error Category: 0
Event: 11316 Source: MsiInstaller
Product: ISScript -- Error 1316.A network error occurred while attempting to read from the file D:\ISScript9.Msi

Log: 'Application' Date/Time: 01/03/2011 8:59:13 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:11 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:11 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:11 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:10 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:09 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:09 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:09 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:08 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:08 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:08 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:08 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:08 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:07 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:59:05 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

Log: 'Application' Date/Time: 01/03/2011 8:58:43 PM
Type: error Category: 0
Event: 1000 Source: PerfDisk
Unable to open the Disk performance object. Status code returned is data DWORD 0.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: Aavmker4 AFD AmdPPM aswRdr aswSP aswTdi Fips IPSec MRxSmb NetBIOS NetBT RasAcd Rdbss Tcpip vmm WS2IFSL

Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The QoS RSVP service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning.

Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error: A device attached to the system is not functioning.

Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The Bonjour Service service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: A device attached to the system is not functioning.

Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The TCP/IP NetBIOS Helper service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning.

Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: A device attached to the system is not functioning.

Log: 'System' Date/Time: 25/04/2011 5:38:36 PM
Type: error Category: 0
Event: 7001 Source: Service Control Manager
The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error: A device attached to the system is not functioning.

Log: 'System' Date/Time: 25/04/2011 5:38:11 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}

Log: 'System' Date/Time: 25/04/2011 5:38:08 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service StiSvc with arguments "" in order to run the server: {A1F4E726-8CF1-11D1-BF92-0060081ED811}

Log: 'System' Date/Time: 25/04/2011 4:09:45 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}

Log: 'System' Date/Time: 25/04/2011 3:56:48 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service StiSvc with arguments "" in order to run the server: {A1F4E726-8CF1-11D1-BF92-0060081ED811}

Log: 'System' Date/Time: 25/04/2011 3:56:39 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service StiSvc with arguments "" in order to run the server: {A1F4E726-8CF1-11D1-BF92-0060081ED811}

Log: 'System' Date/Time: 25/04/2011 3:56:30 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service StiSvc with arguments "" in order to run the server: {A1F4E726-8CF1-11D1-BF92-0060081ED811}

Log: 'System' Date/Time: 25/04/2011 3:53:44 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service StiSvc with arguments "" in order to run the server: {A1F4E726-8CF1-11D1-BF92-0060081ED811}

Log: 'System' Date/Time: 25/04/2011 3:53:14 PM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 25/04/2011 3:53:14 PM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 25/04/2011 3:53:14 PM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 25/04/2011 3:53:14 PM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 25/04/2011 3:53:13 PM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 25/04/2011 3:53:13 PM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

If you look at "'System' Log - error Type" part, you can see, that several drivers/services refuse to load.
Could be you problem.

Go Start>Run ("Start Search" in Vista/7), type in:
sfc /scannow
Click OK (hold CTRL, and SHIFT, hit Enter in Vista/7).
Have Windows CD/DVD handy (with Vista/7, most likely, you won't need it).
If System File Checker (sfc) will find any errors, it may ask you for the CD/DVD (rarely in Vista/7 case).