Random BSODs, Minidump diagnosis

[Devious]

Hi all.

In the last few months, my comp has been doing completly random BSOD's on a daily basis. I've tested basicly all my hardware to see if any was malfunctioning without results. The only time i (almost) every time can guarentee i'll get a BSOD (besides when least convenient ) is when i transfer files between my 2 comps (via LAN).

I've attached the minidumps from the past 2 days in hope someone have the time to help me make sence of them.

In advance, thank you very much for your time

 

[kimsland]

Inside the 5 MiniDumps:

BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : i8042prt.sys

BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : NDIS.SYS

BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : NDIS.SYS

BugCheck 100000D1, {0, 2, 0, b82c26de}
Probably caused by : rdbss.sys

BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : portcls.sys

i8042prt.sys is a driver for the ps/2 ports
NDIS.SYS is a driver for your network card
RDBSS.SYS Redirected Drive Buffering SubSystem Driver
portcls.sys Multimedia Audio Controller

Please update all drivers from your Manufactures support page
(Umm once you work out what your Motherboard Model Number is exactly!)

 

[Devious]

It's been a while since my first post, and i've consulted god knows how many people about my random BSOD's. In the process i learned to analyze the minidumps myself as well. Anyway, updating all my drivers narrowed the crash errors down a bit. The one i keep getting and seems like i can't get rid off is:

BugCheck 1000000A, {820, 1e, 1, 804d9e0e}
Probably caused by : NDIS.SYS

See the old mini dumps for additional info. They're identical

And today this one popped up as well:

BugCheck 1000000A, {4, 2, 0, 805223bb}



Probably caused by : ntkrnlmp.exe ( nt!KiTimerListExpire+117 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805223bb, address which referenced memory

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




READ_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerListExpire+117
805223bb f6400480 test byte ptr [eax+4],80h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 804e207d to 805223bb

STACK_TEXT:
805563fc 804e207d 80560f00 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x117
80556428 804dcd22 80561300 00000000 00267741 nt!KiTimerExpiration+0xb1
80556440 80560ca0 ffdffc50 00000000 80560ca0 nt!KiRetireDpcList+0x61
80556450 804dcc07 00000000 0000000e 00000000 nt!KiIdleThread0
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerListExpire+117
805223bb f6400480 test byte ptr [eax+4],80h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTimerListExpire+117

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e54690

FAILURE_BUCKET_ID: 0xA_nt!KiTimerListExpire+117

BUCKET_ID: 0xA_nt!KiTimerListExpire+117

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

Any ideas? Except from dumping this sh*tty machine in the nearest harbour?

EDIT: Typo's

 

[kimsland]

Yes, do a Windows Update and install Service Pack 3