Often experiencing BSODs

Hello people,

I have huge problem with my computer. It is fairly new and I am very often receiving BSODs (My computer is formated 4 times since I bought it, and still experiencing BSOD, it is also checked by the technical stuff for hardware and software problem, and there is no problem, at least my technical stuff say it).

Oftenly ACPI.sys and random executable files... Also it often happens when I install new software or some random applications. Today I installed the newest version of nod32 and it happend. It often gives me error IRQL_LESS_OR_EQUAL.

My configuration:

Intel Pentium D CPU 3.20GHz, 2,00 GB of RAM.

GeForce 8400 GS

160 GB SATA disk

ASUS DVD/RW

Here are the logs of the dumps and hijack this. Thank you.

 

sounds like data corruption to me and if the ACPI is crashing is COULD be that the system is on its last legs or over heating or a bad power supply check and make sure the fans are clean over heating pop open the case check the fans and cooler's there fairly free of dust and look and are spinning when powered on

 

I already told you that it is cleaned 2 times in 2 months, and it had passed the hardware and software test (at least the guys from the shop told me like that).

Here are pictures from my BIOS:

Picture 1.

Picture 2.

Picture 3.

Picture 4.

 

I check the cooler and the temperature.
The temperature is 48 and the cooler 3600 RPM.

 

ok try this uninstall any clean up, tools av firewall ect ect ect like :tuneup"
run a scandisk uninstall an unneeded devices sound card ect ect ect and use it at see if its still unstable

if your still havening a issue its good bet its hardware related those types of issues are very hard to track down even if it pass's "the so called stress test" it may not tell you if there is anything wrong or not
and 48c is a little warm for my tastes but its still well with in the safe zone but one of that bios pic said it was at 50c and that is a hot for idle even for a dual core

 

What should be the ideal temperature? Can this error be from drivers?

 

I think the temperature of the CPU is good. Here you can see the picture, when my PC is not idle...

 

ok thats fine sometimes to temp sensors give faulse rateing when did this start after a software install or update ect or out of the blue ?

 

After a software install usually connected with drivers...

 

mm you said its been formated before did it do this then ?

 

Yes, 2 times. Now I also am trying to update the drivers, but I am not so optimistic.

 

I think so. I bought the computer from my local store. Also I am not sure is it ATA or SATA. Here is screenshot.
http://pic.mkd.net/images/231790untitled.JPG

 

Are you sure that it is hardware problem. Here are all the BSOD minidump files:

 

I know how to interpret them. There are several executables or sys files in the dump.

 

Today, I again received BSOD message. This time about firefox.exe

Code:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini050508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:/websymbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon May  5 16:11:12.515 2008 (GMT+2)
System Uptime: 0 days 2:15:38.257
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...........................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c01f8094, 2, 0, 80500351}

Probably caused by : memory_corruption ( nt!MiLocateSubsection+67 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c01f8094, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80500351, address which referenced memory

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


READ_ADDRESS:  c01f8094 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiLocateSubsection+67
80500351 8b0b            mov     ecx,dword ptr [ebx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

LAST_CONTROL_TRANSFER:  from 80500627 to 80500351

STACK_TEXT:  
9bc95c4c 80500627 895ab020 895ab158 895ab020 nt!MiLocateSubsection+0x67
9bc95c50 895ab020 895ab158 895ab020 87b6e020 nt!MMTEMPORARY+0x7b
WARNING: Frame IP not in any known module. Following frames may be wrong.
9bc95c54 895ab158 895ab020 87b6e020 f7717538 0x895ab020
9bc95c58 895ab020 87b6e020 f7717538 804dc766 0x895ab158
9bc95c5c 87b6e020 f7717538 804dc766 87b6e020 0x895ab020
9bc95c60 f7717538 804dc766 87b6e020 804ec2a0 0x87b6e020
9bc95c64 804dc766 87b6e020 804ec2a0 895ab110 0xf7717538
9bc95c8c 87b6e268 895ab020 00200008 00000006 nt!KeWaitForSingleObject+0x16
9bc95ca4 00000000 8949b020 520713fc 01c8aeb9 0x87b6e268


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiLocateSubsection+67
80500351 8b0b            mov     ecx,dword ptr [ebx]

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  469f6017

SYMBOL_NAME:  nt!MiLocateSubsection+67

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiLocateSubsection+67

BUCKET_ID:  0xA_nt!MiLocateSubsection+67

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