BSOD after fresh Install why?

ok so i fresh installed my computer brand new now i have a stock CPU fan and i think my CPU is overheating or something to do with heat or my CPU now the BSOD said it was a Thread or somthing it sounds to me a CPU thread so can you help me out thanks

Sam00 said:

ok so i fresh installed my computer brand new now i have a stock CPU fan and i think my CPU is overheating or something to do with heat or my CPU now the BSOD said it was a Thread or somthing it sounds to me a CPU thread so can you help me out thanks

Ok

Where to start




1-SPTD.SYS. used in alcohol/daemon tools is hideous for BSOD's

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-Your VB compiler.

This is what caused this crash.

3-AV and firewall. We recommend Microsoft Security Essentials and win 7

4-Memory

Just to be sure I would run memtestDownload 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.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\111210-12027-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e55e50
Debug session time: Fri Nov 12 00:55:57.382 2010 (GMT-5)
System Uptime: 0 days 5:57:50.802
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8007fb9b30, fffffa8007fb9e10, fffff80002f935d0}

Probably caused by : vbc.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007fb9b30, Terminating object
Arg3: fffffa8007fb9e10, Process image file name
Arg4: fffff80002f935d0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8007fb9b30

IMAGE_NAME:  vbc.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: vbc

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  MsMpEng.exe

BUGCHECK_STR:  0xF4_MsMpEng.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003014652 to fffff80002c88740

STACK_TEXT:  
fffff880`0a739b08 fffff800`03014652 : 00000000`000000f4 00000000`00000003 fffffa80`07fb9b30 fffffa80`07fb9e10 : nt!KeBugCheckEx
fffff880`0a739b10 fffff800`02fbd3e3 : ffffffff`ffffffff fffffa80`07373550 fffffa80`07fb9b30 fffffa80`06f7bb30 : nt!PspCatchCriticalBreak+0x92
fffff880`0a739b50 fffff800`02f4580c : ffffffff`ffffffff 00000000`00000001 fffffa80`07fb9b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17946
fffff880`0a739ba0 fffff800`02c87993 : fffffa80`07fb9b30 00000000`00000000 00000000`00000000 fffffa80`07373550 : nt!NtTerminateProcess+0x20c
fffff880`0a739c20 00000000`76e3001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0574de98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e3001a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_MsMpEng.exe_IMAGE_vbc.exe

BUCKET_ID:  X64_0xF4_MsMpEng.exe_IMAGE_vbc.exe

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

thanks very much

ASACPI.sys date stamped May 2009

vbc.exe (Visual Basic Command Line Compiler)
Updated it to Microsoft .NET Framework 4

Running Microsoft Security Essentials (Up to Date)

Ran Memtest86 passed 1 time but will do 5 or 6 now

Thanks for the Help