Many bsods on a new system lately...

This one occurred BEFORE the asacpi.sys change I made. This bsod had both sticks of ram in and it resulted some time after I woke up the computer from its sleep when it was left on over night.

So far though, no bsods after that asacpi change. We'll see....

PS: Is there a way to force the bsods to occur in my case? They all seem to occur at random times but maybe there is something I'm just not seeing, maybe something related to the functions of the drivers and the applications that access them?...

Dweezy said:

This one occurred BEFORE the asacpi.sys change I made. This bsod had both sticks of ram in and it resulted some time after I woke up the computer from its sleep when it was left on over night.

So far though, no bsods after that asacpi change. We'll see....

PS: Is there a way to force the bsods to occur in my case? They all seem to occur at random times but maybe there is something I'm just not seeing, maybe something related to the functions of the drivers and the applications that access them?...

yes driver verifier but lets go one step at a time , too many changes too quick clouds the issue :)

crash was UNEXPECTED_KERNEL_MODE_TRAP

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002eca301}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002eca301

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: speedfan.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002eca469 to fffff80002ecaf00

STACK_TEXT:
fffff800`00ba4d28 fffff800`02eca469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02ec8932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`02eca301 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x1a6


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02ec8932 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

these drivers where still present and need updating but you've sorted "ASACPI.sys" now ??

ASACPI.sys fffff880`04829000 fffff880`04831000 0x00008000 0x42476c4c 28/03/2005 02:30:36
speedfan.sys fffff880`017a7000 fffff880`017ae000 0x00007000 0x45168798 24/09/2006 13:26:48
PxHlpa64.sys fffff880`00db1000 fffff880`00dbcd00 0x0000bd00 0x47d88a39 13/03/2008 01:58:17
adfs.SYS fffff880`01200000 fffff880`01218000 0x00018000 0x48640195 26/06/2008 20:52:37

I have sorted ASACPI.sys. I did install a new version of speedfan (4.40 ~November 2009?). Still no bsods, I'll update when anything changes.

As for the other two drivers, I have several adobe applications installed but to my recollection they are recent releases (perhaps something apart from the main software that is bundled along with them are still old.) But let's just wait for a bsod before I go reinstalling software I guess. I don't know whether to hope for a bsod or not, haha. I really hope it was that ASACPI.sys that was making a fuss. Thanks again :)

Hmmm...I ran into a new problem. While watching a youtube video, my computer froze without a bsod, just froze. The sound was stuck also. This happened on two occasions (the last coincidentally happened when I accidently hit my knee against the table that my computer is sitting on...not sure if they're related...). I had to do a hard reset on my computer both times.

However no bsods yet...but this new problem...

Just got another bsod while playing Team Fortress 2 connected to Steam online. It was really fast though and I didn't see the actual blue screen. The computer restarted itself.

Dweezy said:

Just got another bsod while playing Team Fortress 2 connected to Steam online. It was really fast though and I didn't see the actual blue screen. The computer restarted itself.

the freeze when you accidentally knocked your PC is normally a loose connection, that could mean anything such as badly seated ram or pci cards graphics card and sata eide connections , maybe open your box and reseat everything ?

the bluescreen was

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004d3b038, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004d3b038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031a86f0 fffff800`030c5a89 : fffffa80`04d3b010 fffffa80`03a05b60 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`02fa7547 : fffffa80`04d3b010 fffff800`030205f8 fffffa80`03a05b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`02f0fb95 : fffff800`03082360 fffffa80`04a84828 fffffa80`04a84820 fffffa80`03a05b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`02e8a161 : fffff880`00c30e00 fffff800`02f0fb70 fffffa80`03a05b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`03120166 : 00000000`00000000 fffffa80`03a05b60 00000000`00000080 fffffa80`039ef040 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`02e5b486 : fffff880`02f63180 fffffa80`03a05b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`031a7d90 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

this could well be a bad processor, let's hope you didn't kill it by overclocking

need some more minidumps then maybe run driver verifier but for now temporarily unninstall speedfan ..................

Dweezy said:

Hopefully I did not kill the processor, I made sure temps weren't high and there's plenty of cooling. No more overclocking since these bsods occurred anyways. :/

I'm running memtest on one stick at the moment for a long period of time. I was wondering, in memtest for the "settings," shouldn't they reflect my ram's timings? memtest is saying "533mhz, (ddr1066) / CAS : 2.5-1-05 DDR-1 (128 bits)". Is that how it's suppose to be? (I currently have my ram set in the bios @ 1600, 9-9-9-24, 1.55V). I tried to enter memtest's configuration and press "9" for advanced options and "2" to change memory timing but I get kicked back to the main menu. *shrugs*

Update: I ran into a problem. I'm curious about why memtest will fail to run if I have two sticks of ram in. I set it for 1333, 1600 at various timings and memtest will continue to fail when both are in...

I think memtest86 reports timings correctly and 533 on DDR will give an effective 1066, not sure what they are referring to here "CAS : 2.5-1-05 DDR-1 (128 bits)" , but the most significant thing is two sticks crash it, this might be resolvable by timings and combinations so try slots 1 & 3 or 1 & 2 as a pair and drop timings to the lowest common denominator in ram ? anything too aggressive will test the tolerances and take ram closer to being unstable, try slower timings and see if you can get sticks to work together .........

also once you have your ram stable we could try prime95 to stress the cpu and ram ?