Crashing & BSOD & Rebooting

[BLoodY]

Hi,

first of all, thanks for this care and service..

I have bad problem, sometimes "driver_irql_not_less_or_equal" and sometimes "STOP:0x0000008E)" error
My comp resets itself 10-15 times per day. (I turned off automatically start over option now I get BSODs)

I did not install any new hardware and my virus prg and firewall prg runs on my computer for long time.. (no change)
I changed RAMs.. no effect..
there are no spyware, trojans etc on computer

I attached my minidumps and event viewer file..

I exhausted for this problem

 

[cpc2004]

Hi BLoodY,

Upgrade AVG may resolve the blue screen problem.

 

[BLoodY]

cpc2004 thanks, i will try this on computer tomorrow..

additionally I want to give some info more..

- comp. crashed just one time with "bad_pool_caller" BSOD
- it resets itself sometimes at just the end of Scandisk progress
- rarely resets on windows load screen

i attached two new minidump

 

[BLoodY]

upgrading AVG didn't solve the problem
(0x0000008e problem)

could you review my minidump ?

 

[cpc2004]

Hi Bloody,

Your firewall is 6 years behind. De-install or upgrade it to latest level.

FWFILT FWFILT.SYS Wed Oct 13 06:55:26 1999 (3803BC5E)
HTTPFILT HTTPFILT.SYS Wed Oct 13 06:54:55 1999 (3803BC3F)

nVidia Dispaly Card display card driver is one year behind. Upgrade it to latest level.
nv4_disp nv4_disp.dll Sat Oct 30 09:15:58 2004 (4182EB4E)

 

[BLoodY]

hi cpc, (thanks a lot for your time)

i installed newest nvidia driver but no change.
my firewall (atguard) runs on my machine for several years and I didin't get any problem.. I will be looking for new version of firewall..

now comp. sometimes restarts without bluescreen .. just restarting.. sometimes I get minidumps..

here are newest two file

 

[cpc2004]

Hi Bloody,

Reboot without blue screen is the symptom of hardware such as faulty ram, cpu, m/b and psu. After you upgrade AVG, your windows crashes with bugcheck 0A and more information is logged at the stack trace. The last minidump is crashed with illegal instruction. Probably it is faulty ram or m/b.

FAULTING_IP:
nt!NtWaitForSingleObject+bb
805f45a1 8b45ec mov eax,[ebp-0x14]

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA

EXCEPTION_RECORD: f56a7ba4 -- (.exr fffffffff56a7ba4)
ExceptionAddress: 804dab60 (nt!KiComputeTimerTableIndex+0x00000060)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

LAST_CONTROL_TRANSFER: from 804dbeff to 804dab60

STACK_TEXT:
f56a7ca0 804dbeff ffffd8f0 ffffffff 5a66dee0 nt!KiComputeTimerTableIndex+0x60
f56a7cbc 804d8afa ffffd8f0 ffffffff 00000000 nt!KiInsertTreeTimer+0x7d
f56a7cec 8056539e 00000001 00000006 819b6401 nt!KeWaitForSingleObject+0x161
f56a7d50 804de7ec 00000960 00000000 f56a7d1c nt!NtWaitForSingleObject+0x9a
f56a7d50 7c8feb94 00000960 00000000 f56a7d1c nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0445ff6c 00000000 00000000 00000000 00000000 0x7c8feb94

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty

Take out one memory stick. If windows does not crash, the removed memory stick is faulty.