Hello All,

Here are some initial specs on my PC:
-Asus A8N-E motherboard
-AMD Athlon 64 processer 3700+
-2.21GHz,
-2GB RAM ()
-Windows XP Home SP3.
-Nvidia GeForce 6600 GT video card (PCI)

So I’ve been having some crashing issues on my PC for about a month now, maybe more.

I have not been able to determine what causes the crashing. One day I turned the PC on and it would not work. I figured what the heck, I got time to reinstall the OS so let’s give it a go. I re-installed the OS and what I believe all the software/drivers etc.

The crashing issue has not gone away.

I noticed that generally the PC could crash if it was idle for some time and then I tried to log back into my windows account (from the windows logon screen). Of course there are times where it seems the PC reboots itself during the night or whenever which I do not realize until I log back into my windows account.

I have been trying to understand the minidump files that are left behind but I just don’t get them.

-I ran memtest+ for more than 7 passes and no errors were noted.
-I installed the western digital lifeguard software and checked my harddrive but it did not notice anything wrong.

There have been several errors thrown in the event viewer that might help us determine what is happening with my PC.

Just this morning when I turned on my PC it said something about recovering the registry and then proceeded to do a chkdsk repair or something.

Here are some of the errors in event viewer that I have seen:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 9/1/2009
Time: 9:27:11 AM
User: N/A
Computer: SS
Description:
Faulting application ccSvcHst.exe, version 108.1.1.10, faulting module ccSet.dll, version 108.1.1.10, fault address 0x0002797c.

For more information, see Help and Support Center at
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 63 53 ure ccS
0018: 76 63 48 73 74 2e 65 78 vcHst.ex
0020: 65 20 31 30 38 2e 31 2e e 108.1.
0028: 31 2e 31 30 20 69 6e 20 1.10 in
0030: 63 63 53 65 74 2e 64 6c ccSet.dl
0038: 6c 20 31 30 38 2e 31 2e l 108.1.
0040: 31 2e 31 30 20 61 74 20 1.10 at
0048: 6f 66 66 73 65 74 20 30 offset 0
0050: 30 30 32 37 39 37 63 002797c


Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 9/1/2009
Time: 9:13:53 AM
User: N/A
Computer: SS
Description:
Faulting application ccSvcHst.exe, version 108.1.1.10, faulting module unknown, version 0.0.0.0, fault address 0x00450053.

For more information, see Help and Support Center at
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 63 53 ure ccS
0018: 76 63 48 73 74 2e 65 78 vcHst.ex
0020: 65 20 31 30 38 2e 31 2e e 108.1.
0028: 31 2e 31 30 20 69 6e 20 1.10 in
0030: 75 6e 6b 6e 6f 77 6e 20 unknown
0038: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 34 35 30 30 t 004500
0050: 35 33 53


Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 8/31/2009
Time: 8:06:32 PM
User: N/A
Computer: SS
Description:
Faulting application ccsvchst.exe, version 108.1.1.10, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x0000ff56.

For more information, see Help and Support Center at
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 63 73 ure ccs
0018: 76 63 68 73 74 2e 65 78 vchst.ex
0020: 65 20 31 30 38 2e 31 2e e 108.1.
0028: 31 2e 31 30 20 69 6e 20 1.10 in
0030: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
0038: 6c 20 35 2e 31 2e 32 36 l 5.1.26
0040: 30 30 2e 35 37 35 35 20 00.5755
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 30 66 66 t 0000ff
0058: 35 36 0d 0a 56..


Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/1/2009
Time: 9:07:33 AM
User: N/A
Computer: SS
Description:
Application popup: Windows - Registry Recovery : One of the files containing the system's Registry data had to be recovered by use of a log or alternate copy. The recovery was successful.

For more information, see Help and Support Center at

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/1/2009
Time: 9:07:15 AM
User: N/A
Computer: SS
Description:
Application popup: Windows - Corrupt File : The file or directory C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT is corrupt and unreadable. Please run the Chkdsk utility.

For more information, see Help and Support Center at

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 9/1/2009
Time: 9:07:08 AM
User: N/A
Computer: SS
Description:
The following boot-start or system-start driver(s) failed to load:
IDSxpx86

For more information, see Help and Support Center at

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 9/1/2009
Time: 9:07:08 AM
User: N/A
Computer: SS
Description:
The TCP/IP NetBIOS Helper service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 8/31/2009
Time: 9:16:42 AM
User: N/A
Computer: SS
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.

For more information, see Help and Support Center at
Data:
0000: 15 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 40 00 00 00 00 00 00 00 @.......
0020: 00 00 00 00 00 00 00 00 ........


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/30/2009
Time: 4:23:40 PM
User: N/A
Computer: SS
Description:
Error code 0000004e, parameter1 00000099, parameter2 03876a42, parameter3 00000005, parameter4 00000000.

For more information, see Help and Support Center at
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 34 0000004
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 39 39 2c 20 000099,
0038: 30 33 38 37 36 61 34 32 03876a42
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 35 2c 20 30 30 30 30 05, 0000
0050: 30 30 30 30 0000


-I’ve cleaned out as much dust from the PC as possible

-I’ve reseated the two 1 GB slots of RAM.

-I had a tv tuner card (ATI) but took it out (last week maybe..) and uninstalled the drivers for it.

-Not sure if the onboard video card could be having an issue with my GeForce one?

-I recently uninstalled Kapersky and installed Norton (NIS 2009).

-When I check speedfan it tells me the following:
+3.3V: 3.28V
+5V: 5.03V
+12V: 12.10V

GPU: 55C
Temp1: 36C
Temp2: 34C
Temp3: 25C
HD1: 52C
HD0: 30C
Temp1: 40C
Core: 36C
Core:55C

I will attach the minidump files in a RAR format if anyone is willing to help me out I would appreciate it.

I will read through the forums for suggestions on things to try but thought perhaps the minidumps (and those more closer to todays date) might help someone point me in the right direction.

Thanks in Advanced for your help and suggestions.

It will not let me attach files.

It also will not let me post a url link because i do not have 5 posts.

I apologize for making up the posts just so i can post a link.

duplicate post.

Hey Everyone,

For some reason it will not let me attach a file when i click on "manage attachments". It also would not let me post a URL because i did not have 5 posts yet (i'm a newb). I again apologize for making up the posts so that i would be able to post a link for files.

Anywho, you can see the minidumps (and dxdiag zip file) at the following link from rapidshare) here:

http://rapidshare.com/files/27449874...xdiag.zip.html


Thanks Again!

PS! i have IE 8 installed

My PC just showed the BSOD twice in less then 10 minutes or so.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Wed Sep 2 12:34:12.171 2009 (GMT-4)
System Uptime: 0 days 0:13:05.750
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......................
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {2850d67c, 2, 0, 804e12f4}

Probably caused by : ntkrnlpa.exe ( nt!CcSetDirtyPinnedData+7e )

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: 2850d67c, 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: 804e12f4, address which referenced memory

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


READ_ADDRESS: 2850d67c

CURRENT_IRQL: 2

FAULTING_IP:
nt!CcSetDirtyPinnedData+7e
804e12f4 837f6000 cmp dword ptr [edi+60h],0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80622de4 to 804e12f4

STACK_TEXT:
b84fbc2c 80622de4 b84fbc28 000f5800 e5c50d9c nt!CcSetDirtyPinnedData+0x7e
b84fbc7c 806307d2 e5c50b60 e51f9118 00000000 nt!CmpUnPinCmView+0x90
b84fbca8 80631dd7 e5c50b60 b84fbce0 e5c50d84 nt!HvpFlushMappedData+0xfe
b84fbd28 806324a0 e5c50b60 00000000 e5c50b60 nt!HvpDoWriteHive+0x1db
b84fbd40 80628c78 e5c50b01 8055b17c 80550d20 nt!HvSyncHive+0x88
b84fbd5c 80621ac5 00000000 8a740640 00000000 nt!CmpDoFlushAll+0x6c
b84fbd74 80534c12 00000000 00000000 8a740640 nt!CmpLazyFlushWorker+0x51
b84fbdac 805c61ec 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
b84fbddc 80541de2 80534b12 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CcSetDirtyPinnedData+7e
804e12f4 837f6000 cmp dword ptr [edi+60h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CcSetDirtyPinnedData+7e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

FAILURE_BUCKET_ID: 0xA_nt!CcSetDirtyPinnedData+7e

BUCKET_ID: 0xA_nt!CcSetDirtyPinnedData+7e

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

========================


Here is the other dump file:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Wed Sep 2 12:18:50.625 2009 (GMT-4)
System Uptime: 0 days 3:55:34.239
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......................................
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffff00, 0, 0, 0}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiMakeSystemAddressValidPfn+20 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffff00, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 00000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: ffffff00

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: msnmsgr.exe

LAST_CONTROL_TRANSFER: from 8051cc5f to 804f8cc5

STACK_TEXT:
a1aa1c80 8051cc5f 00000050 ffffff00 00000000 nt!KeBugCheckEx+0x1b
a1aa1ce0 80513b9c 00000000 ffffff00 00000000 nt!MmAccessFault+0x8e7
a1aa1d00 8051cf0c 00825446 00000000 0936febc nt!MiMakeSystemAddressValidPfn+0x20
a1aa1d4c 8054052c 00000000 00825446 00000001 nt!MmAccessFault+0xb94
a1aa1d4c 763a477f 00000000 00825446 00000001 nt!KiTrap0E+0xcc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0936febc 00000000 00000000 00000000 00000000 0x763a477f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiMakeSystemAddressValidPfn+20
80513b9c 3bc7 cmp eax,edi

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiMakeSystemAddressValidPfn+20

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x50_nt!MiMakeSystemAddressValidPfn+20

BUCKET_ID: 0x50_nt!MiMakeSystemAddressValidPfn+20

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

Ok, so i got several stop codes in quick succession. It seemed like the system was crashing every 15 minutes

-00000050
-0000000A
-000000C2
-00000000


I decided to shut down my PC and take one of the 1GB RAM sticks out. I browsed around for say an hour or so without any issues. So i turned off the PC and took out the remaining 1GB stick and replaced it with the other one.

Booted up the PC and before it could get to the windows startup logon screen it dropped a 0000008E error. I rebooted and BSOD came up with stop code 0000007e...restarted again and saw BSOD stop code 00000050.

I turned off the PC, took that RAM stick and moved it to another slot. This time the PC turned on but within 1 minute it crashed with stop code 0000008E and then 0000004E.

Looks like a possible faulty RAM stick.

I have since taken out that stick and put in the "working" one. So far it's been running for an hour without issue.

At least i have somewhere to check now. I'll see how this RAM stick performs over the next few days. If it's good then i guess this is solved....

Yes, definitely test your RAM again. 0xA errors are caused by either hardware or drivers. 0x50 errors can be caused by corrupted memory (though with this error there are other reasons as well). 0x8E errors are almost always caused by hardware and are especially strong indicators of corrupted memory. And you also have an 0x4E error and these are one of the strongest indicators of corrupted memory.

Coupled with the fact that your errors are all over the place points to corrupted memory. Plus one of the minidumps you posted specifically cites corrupted memory as your issue.


* Keep us informed.

Well i've been using my computer all day on just the 1 GB of RAM i left in their and it has not crashed once which is a good sign.

I'm definitely leading to the fact that i have one faulting RAM stick and believe that is the cause of my issues.

Thanks for your help!

Yes, I fully agree. Glad to help and I am glad you found the answer.