Need software!

[yoco]

You might also have a look at this app: Resplendence Software - WhoCrashed, automatic crash dump analyzer.
It scans the crash dumps and say what was the problem.
I have used it for quite a while and it has helped me many times.

Thnx a lot! This is what I needed!

Here's what I get:

On Sun 8.8.2010 21:27:14 your computer crashed
This was likely caused by the following module: wanarp.sys
Bugcheck code: 0x1000000A (0x35303838, 0x2, 0x0, 0x804E53BC)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini080810-01.dmp
file path: C:\WINDOWS\system32\drivers\wanarp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS Remote Access and Routing ARP Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

[anon]

wanarp.sys is, as the quote says, a driver handling ARP stuff, so the issue is network-related. I'd to a test run without a firewall, if you're using one. Checking whether there are newer drivers for your network card wouldn't hurt, either.

Also, if you or an application have turned autoreboot on, these "random reboots" could be actually your system automatically starting over after a BSoD you don't get to see. Check this out:
http://forums.techguy.org/windows-xp...d1-caused.html

[Uninvited2611]

You may replace fresh wanarp.sys. google "wanarp.sys crash", there's a lot having the same problem like you

[yoco]

I updated drivers for my network card, so I'll see if this will fix the problem. If not, I'll try your advice too!

[yoco]

So I was hoping that with updating the network drivers it would solve the crashing, but it didn't. My PC just crashed again. This time it showed me this on startup



And after checking in Event Viewer I saw this

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000014, 0x00000002, 0x00000000, 0xb4863872). A dump was saved in: C:\WINDOWS\Minidump\Mini081110-01.dmp.

[desodorante]

I second anon's suggestion on using memtest86, but I suggest memtest86+ Memtest86+ - Advanced Memory Diagnostic Tool
It could be one of your RAMs going nuts.
Also, you might want to use HDD Regenerator to check for faulty sectors in the HD (the program DOES recover them if there are not physically damaged), but I hardly believe that can be the source of your problem.
A Long time ago I had a problem with my computer crashing and it was due to using XP's drive cache, prefetcher and indexer, but I had no BSOD or resets.
Hope it helps!

[yoco]

I just did a RAM test and it passed without any error at all!
What about my graphic card? Could it be the source of problems? Is there any test for that?

[anon]

What about my graphic card?

Maybe, if you're using faulty drivers or something.

[yoco]

I updated the drivers just two days ago!
What about graphic card performance test? Is it possible? Like I did with RAM just now?

[anon]

What about graphic card performance test? Is it possible?

You can do that with 3D Benchmark if you want.

By the way, memtest86 isn't a performance test, but rather an integrity check - it tests all your RAM chips to see if any of them are faulty.

[Evilmill]

i am damn sure some hardware the culprit.. if u can disassemble ur system... try using ur pc without graphics card... if it runs fine then it was due to a faulty graphics card.. if not go for RAM, harddrive, etc ....

no software can help to find the solution ...

[yoco]

I run 3D Benchmark and I "passed". I really don't know what could be the problem :o

---------- Post added 13.08.10 at 09:18 ---------- Previous post was 12.08.10 at 18:16 ----------

So if anyone would know what this means, it would help a lot!

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


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

Symbol search path is: C:\WINDOWS\symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Aug 12 22:46:42.609 2010 (UTC + 2:00)
System Uptime: 0 days 4:07:59.257
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** 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, {331d353d, 2, 0, 804e53bc}

Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
Unable to load image wanarp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wanarp.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** WARNING: Unable to verify timestamp for psched.sys
Unable to load image cfosspeed.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cfosspeed.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed.sys
Probably caused by : wanarp.sys ( wanarp!WanReceiveCommon+164 )

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

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: 331d353d, 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: 804e53bc, address which referenced memory

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


READ_ADDRESS:  331d353d 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertQueueApc+84
804e53bc 8b7704          mov     esi,dword ptr [edi+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  winamp.exe

LAST_CONTROL_TRANSFER:  from 804e5451 to 804e53bc

STACK_TEXT:  
f7c4e5f8 804e5451 856e9708 856e96c8 00000000 nt!KiInsertQueueApc+0x84
f7c4e618 804ecac4 856e9708 00000000 00000000 nt!KeInsertQueueApc+0x40
f7c4e64c f44b6942 f7c4e6bc 85d1d100 f7c4e6bc nt!IopfCompleteRequest+0x1d8
f7c4e664 f44b9be3 856e96c8 00000000 000005d6 tcpip!TCPDataRequestComplete+0xa6
f7c4e684 f44b645f f7c4e6bc 85c3f0b0 853dd08e tcpip!CompleteSends+0x2b
f7c4e700 f44b3ef5 85b22128 881e3d56 dda475d4 tcpip!TCPRcv+0x1be
f7c4e760 f44b3b19 00000020 85b22128 f44b60b6 tcpip!DeliverToUser+0x18e
f7c4e7dc f44b3836 f44f3870 85b22128 853dd08e tcpip!DeliverToUserEx+0x95e
f7c4e894 f7984232 85b22128 853dd0a2 00000014 tcpip!IPRcvPacket+0x6cb
f7c4e8d8 f79842cc 0cabb1e5 85c27c10 853dd080 wanarp!WanReceiveCommon+0x164
f7c4e910 f758eb9f 0cabb1e5 00000000 f67c9b40 wanarp!WanNdisReceivePacket+0x60
f7c4e964 f67c401d 00d2f178 85ba8e30 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2
f7c4e978 f67c41b4 85b943d0 85ba8e30 00000001 psched!PsFlushReceiveQueue+0x15
f7c4e99c f67c45f9 85b7f010 00000000 85b943d0 psched!PsEnqueueReceivePacket+0xda
f7c4e9b4 f758ec40 85b7f008 85afb948 f7c4ebb4 psched!ClReceiveComplete+0x13
f7c4ea04 f6852bc2 00d2f178 f7c4ea6c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
WARNING: Stack unwind information not available. Following frames may be wrong.
f7c4ea74 f68b4751 853dd010 85c563e0 f7c4ea94 cfosspeed+0x46bc2
f7c4eadc f680dbc5 853dd010 85787158 f7c4eafc cfosspeed+0xa8751
f7c4eaec f68b1355 853dd010 85b4f2f0 f7c4eb18 cfosspeed+0x1bc5
f7c4eafc f68b56eb 853dd010 85469408 853dd0b8 cfosspeed+0xa5355
f7c4eb18 f6860423 853dd010 85784a08 f7c4eb40 cfosspeed+0xa96eb
f7c4eb28 f6812997 853dd010 00000000 8546a220 cfosspeed+0x54423
f7c4eb40 f681293d 853dd010 8546a220 85afb9dc cfosspeed+0x6997
f7c4eb50 f68c9bf0 853dd010 85c55c28 00000001 cfosspeed+0x693d
f7c4eb54 853dd010 85c55c28 00000001 f68ca6a8 cfosspeed+0xbdbf0
f7c4eb58 85c55c28 00000001 f68ca6a8 f7c4ebb4 0x853dd010
f7c4eb5c 00000000 f68ca6a8 f7c4ebb4 85dee6c8 0x85c55c28


STACK_COMMAND:  kb

FOLLOWUP_IP: 
wanarp!WanReceiveCommon+164
f7984232 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  wanarp!WanReceiveCommon+164

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wanarp

IMAGE_NAME:  wanarp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025790

FAILURE_BUCKET_ID:  0xA_wanarp!WanReceiveCommon+164

BUCKET_ID:  0xA_wanarp!WanReceiveCommon+164

Followup: MachineOwner

[desodorante]

I will suggest you check the video card temperature, I had to glue a psu fan in mine.
If that doesn't work, try booting up some live SO from a usb stick and use the computer just like you do when it crashes (so you do not have to reinstall xp)
Then, if you still have problems, try removing whatever hardware is not onboard (except for memory), or you may first try a different psu.
If all of this fails, It's time for you to change your computer.

[anon]

PROCESS_NAME:  winamp.exe

Anyone noticed this in the crash log?

[yoco]

Yea I noticed that too. The strange thing is, I always listen my music when I browse the internet, and that's when I get most of these crashes!

One more thing. These dump files. Do they ever get deleted or they stay in folder, cuz I noticed that my first dump file is from 31.7.2010, and now I don't remember if I had these crashes before that day!