Vista Ultimate 64bit unexpected system failure

I have start to experience a few hiccups in my system, recently it just shut it self down to prevent system damage when I check the details from the unexpexted shut down this is what was listed.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000008884
BCP2: FFFFFA8000E1EA60
BCP3: FFFFFA8000E1EA90
BCP4: 0000000000000502
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\Mini053109-01.dmp
C:\Users\Robb\AppData\Local\Temp\WER-75984-0.sysdata.xml
C:\Users\Robb\AppData\Local\Temp\WER41C7.tmp.version.txt

My system specs are attached to my profile if needed, I have seen this 3X now, any ideas?

Since i had no replys I kicked it up a notch and learned how to use WinDbg and the snipping tool from the tutorials. Here's some more info.

overmyhead said:

Since i had no replys I kicked it up a notch and learned how to use WinDbg and the snipping tool from the tutorials. Here's some more info.

View attachment 13201

Click to expand...

Good job. Unfortunately, since this hardware is new, there's a possibility that the error is caused by malfunctioning hardware.

Does the MiRelinkStandbyPage function get mentioned in all 3 minidumps?

Can you paste (just the text) output of the 'kv' command from each of those?

H2SO4 said:

overmyhead said:

Since i had no replys I kicked it up a notch and learned how to use WinDbg and the snipping tool from the tutorials. Here's some more info.

View attachment 13201

Click to expand...

Good job. Unfortunately, since this hardware is new, there's a possibility that the error is caused by malfunctioning hardware.

Does the MiRelinkStandbyPage function get mentioned in all 3 minidumps?

Can you paste (just the text) output of the 'kv' command from each of those?

Click to expand...

Thanks for the reply H2SO4,

In looking at all 3 minidumps it appears there were 3 seperate issuses which cause the problems the last one was svchost.exe the other 2 which happened on the 29th were dfrgntfs.exe and syncservice.exe.

since it is my first go at windbg can you please explain what you mean by the kv command, when I look at the data the only thing I see is a command kb.

Or is this a function command I need to run, and is there some to copy and paste the data as I am unable to highlight and copy. Thanks

overmyhead said:

Thanks for the reply H2SO4,

In looking at all 3 minidumps it appears there were 3 seperate issuses which cause the problems the last one was svchost.exe the other 2 which happened on the 29th were dfrgntfs.exe and syncservice.exe.

since it is my first go at windbg can you please explain what you mean by the kv command, when I look at the data the only thing I see is a command kb.

Or is this a function command I need to run, and is there some to copy and paste the data as I am unable to highlight and copy. Thanks

Click to expand...

Don't worry about the actual process whose thread was involved in the crash (svchost, syncservice...). Counter-intuitively, that is almost completely irrelevant for reasons difficult to explain succinctly.

Once the automated analysis is complete, just type "kv" (without the quotes). It will produce some output. Simply use the mouse to highlight that new output, copy, and paste it here as text.

Or just zip up and upload the minidumps themselves.

H2SO4 said:

overmyhead said:

Thanks for the reply H2SO4,

In looking at all 3 minidumps it appears there were 3 seperate issuses which cause the problems the last one was svchost.exe the other 2 which happened on the 29th were dfrgntfs.exe and syncservice.exe.

since it is my first go at windbg can you please explain what you mean by the kv command, when I look at the data the only thing I see is a command kb.

Or is this a function command I need to run, and is there some to copy and paste the data as I am unable to highlight and copy. Thanks

Click to expand...

Don't worry about the actual process whose thread was involved in the crash (svchost, syncservice...). Counter-intuitively, that is almost completely irrelevant for reasons difficult to explain succinctly.

Once the automated analysis is complete, just type "kv" (without the quotes). It will produce some output. Simply use the mouse to highlight that new output, copy, and paste it here as text.

Or just zip up and upload the minidumps themselves.

Click to expand...

Latest crash;

BugCheck 1A, {8884, fffffa8000e1ea60, fffffa8000e1ea90, 502}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a2 )
Followup: MachineOwner
---------
7: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffffa60`08b8d8c8 fffff800`022dd0d2 : 00000000`0000001a 00000000`00008884 fffffa80`00e1ea60 fffffa80`00e1ea90 : nt!KeBugCheckEx
fffffa60`08b8d8d0 fffff800`02333b5d : fffffa80`0d208bb0 fffffa80`0c286e68 fffffa80`0d208bb0 fffffa80`0c286e68 : nt!MiRelinkStandbyPage+0xa2
fffffa60`08b8d910 fffff800`02602cd4 : 00000000`00000000 fffffa60`00000000 00000000`00000000 fffffa80`0c286000 : nt!MmSetPfnListPriorities+0x28d
fffffa60`08b8d980 fffff800`02643092 : fffff880`0d974600 00000000`00000000 fffffa80`0c163000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffffa60`08b8d9d0 fffff800`02655aa8 : 00000000`00000000 00000000`00000004 00000000`00000438 00000000`00000001 : nt!PfSetSuperfetchInformation+0x191
fffffa60`08b8dab0 fffff800`0226eef3 : fffffa80`0d208bb0 00000000`03456b20 00000000`000000b5 00000000`00000000 : nt!NtSetSystemInformation+0x8fb
fffffa60`08b8dc20 00000000`77c8838a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffffa60`08b8dc20)
00000000`0288ebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c8838a

Crash 2;


BugCheck 4E, {2, 1fa891, 26ffff, 1}
Unable to load image \SystemRoot\system32\DRIVERS\eamon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+9044 )
Followup: MachineOwner
---------
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffffa60`0c2b5348 fffff800`022140e4 : 00000000`0000004e 00000000`00000002 00000000`001fa891 00000000`0026ffff : nt!KeBugCheckEx
fffffa60`0c2b5350 fffff800`02274ee3 : fffffa60`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x9044
fffffa60`0c2b5390 fffff800`022681f9 : fffff880`1c2c5bf0 fffff880`1c2c5df0 fffffa80`0f448380 fffffa80`0f448380 : nt!MiFlushSectionInternal+0xaa5
fffffa60`0c2b5590 fffff800`0226be7f : 00000000`00000000 fffff980`1bfce500 00000000`00000000 fffffa60`00000000 : nt!MmFlushSection+0x129
fffffa60`0c2b5650 fffffa60`010ca4ff : fffffa80`0f3d6310 00000000`00000000 fffffa80`00000000 fffffa60`0c2b5778 : nt!CcFlushCache+0x840
fffffa60`0c2b5740 fffffa60`0109cec8 : fffff880`165a0b50 fffff880`1c2f3140 fffffa80`0f69fe50 fffff880`00000000 : Ntfs!NtfsFlushUserStream+0x18f
fffffa60`0c2b57d0 fffffa60`010cb722 : fffffa80`0f69fe50 fffffa80`0ad7d180 fffffa60`005f5d01 fffff800`02319d00 : Ntfs!NtfsFlushVolume+0x298
fffffa60`0c2b58f0 fffffa60`010cbd8b : fffffa80`0f69fe50 fffffa80`0fd95010 fffffa80`0fd95010 fffffa80`0ad7d180 : Ntfs!NtfsCommonFlushBuffers+0x681
fffffa60`0c2b59c0 fffffa60`00a55e17 : fffffa80`0fd953f8 fffffa80`0fd95010 fffffa80`0f69fe50 fffffa60`0c2b59e8 : Ntfs!NtfsFsdFlushBuffers+0x10b
fffffa60`0c2b5a30 fffffa60`00a550dd : fffffa80`090e7900 fffffa80`0e82bf20 fffffa80`0ad79d00 fffffa60`01766180 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`0c2b5aa0 fffffa60`07f7ae21 : 00000000`00000000 00000000`00000006 00000000`00000190 00000000`00000190 : fltmgr!FltpDispatch+0xcd
fffffa60`0c2b5b00 00000000`00000000 : 00000000`00000006 00000000`00000190 00000000`00000190 fffffa60`005ec180 : eamon+0x3e21

1st crash;

BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 )
Followup: MachineOwner
---------
5: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffffa60`0931d158 fffff800`022aba22 : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0931d160 fffff800`0229b1d9 : 00000000`00000000 fffffa60`0931d2d0 fffffa60`0931d500 00000000`00000000 : nt!MmAccessFault+0x1722
fffffa60`0931d250 fffff800`02341770 : 00000000`00000000 fffffa60`0931d508 fffffa60`0931d530 00000000`00000013 : nt!KiPageFault+0x119 (TrapFrame @ fffffa60`0931d250)
fffffa60`0931d3e0 fffff800`0235b38f : fffff880`12613600 fffffa60`0931d6c0 00000003`00000000 fffff800`00000000 : nt!MiFreeWsleList+0x240
fffffa60`0931d6a0 fffff800`02477714 : fffffa80`09e72bb0 fffffa60`00000001 ffffffff`ffffffff 00000000`00000074 : nt!MiEmptyWorkingSet+0x1ef
fffffa60`0931d750 fffff800`024dc8ac : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt! ?? ::OKHAJAOM::`string'+0x1455
fffffa60`0931d7d0 fffff800`02533125 : fffffa80`09e72bb0 00000000`7efa3001 00000000`00000000 fffffa80`09e72bb0 : nt!PspSetQuotaLimits+0x2c4
fffffa60`0931d920 fffff800`0229c0f3 : 00000000`00002e38 fffffa60`0931dca0 00000000`058ee760 00000000`00000058 : nt!NtSetInformationProcess+0x6cc
fffffa60`0931dc20 00000000`77445c3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffffa60`0931dc20)
00000000`058ee738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77445c3a

I hope this is what you had in mind.

overmyhead said:

...I hope this is what you had in mind.

Click to expand...

Yes, that's it.

All 3 of those crashes are in low-level memory management routines - the ones controlling the interface between virtual and physical memory. However, all 3 are substantially different, and that tends to suggest more of a hardware-ish slant to the problem.

The second crash may potentially be linked to the EAMON.SYS (NOD32) driver, but it's almost impossible to tell from a minidump and the fact that the other two crashes are different suggests it's probably not all eamon's fault.

There are ways to make the OS apply greater scrutiny to drivers in the hope of catching them doing something obviously "bad", instead of running into corrupted data long after the original culprit is long gone, as in this case, but I think that approach may just further muddy the waters at present.

Instead, I'd suggest using memory test utilities like the built-in one, Memtest, and/or Prime95. If they detect obvious breakdowns at a hardware level, then you can be confident there's a hardware component to the problem.

H2SO4 said:

overmyhead said:

...I hope this is what you had in mind.

Click to expand...

Yes, that's it.

All 3 of those crashes are in low-level memory management routines - the ones controlling the interface between virtual and physical memory. However, all 3 are substantially different, and that tends to suggest more of a hardware-ish slant to the problem.

The second crash may potentially be linked to the EAMON.SYS (NOD32) driver, but it's almost impossible to tell from a minidump and the fact that the other two crashes are different suggests it's probably not all eamon's fault.

There are ways to make the OS apply greater scrutiny to drivers in the hope of catching them doing something obviously "bad", instead of running into corrupted data long after the original culprit is long gone, as in this case, but I think that approach may just further muddy the waters at present.

Instead, I'd suggest using memory test utilities like the built-in one, Memtest, and/or Prime95. If they detect obvious breakdowns at a hardware level, then you can be confident there's a hardware component to the problem.

Click to expand...

I purchased MemTest pro and started to run it the errors it is finding are to many to list but here is a sample.

[15348] Mon Jun 01 11:23:53 2009 >> Memory error detected between 0x9a09b0f8, 0x8c5b0f8 difference = 2000
======== Starting new MemTest session ========
MemTest PRO 3.8 (c) 2008, HCI Design (MemTest: RAM reliability tester for Windows)
NOTE: greater than 100% coverage is possible. Each 100% indicates a thorough testing of all allocated RAM, however, intermittent errors may take multiple 100% cycles to be detected.
[15344] Mon Jun 01 11:24:37 2009 >> Test started. Allocated 393 MB of memory for testing.
======== Starting new MemTest session ========
MemTest PRO 3.8 (c) 2008, HCI Design (MemTest: RAM reliability tester for Windows)
NOTE: greater than 100% coverage is possible. Each 100% indicates a thorough testing of all allocated RAM, however, intermittent errors may take multiple 100% cycles to be detected.
[12068] Mon Jun 01 11:24:37 2009 >> Test started. Allocated 3464 MB of memory for testing.
======== Starting new MemTest session ========
MemTest PRO 3.8 (c) 2008, HCI Design (MemTest: RAM reliability tester for Windows)
NOTE: greater than 100% coverage is possible. Each 100% indicates a thorough testing of all allocated RAM, however, intermittent errors may take multiple 100% cycles to be detected.
[15348] Mon Jun 01 11:24:37 2009 >> Test started. Allocated 3464 MB of memory for testing.
[15344] Mon Jun 01 11:24:41 2009 >> Memory error found copying between 0xf55976f8, 0xe9107538, difference =2000
[15348] Mon Jun 01 11:24:42 2009 >> Memory error found copying between 0xce12556c, 0x3cce50f8, difference =2000
[12068] Mon Jun 01 11:24:43 2009 >> Memory error found copying between 0xeee94088, 0x5da536f8, difference =2000
[15344] Mon Jun 01 11:24:45 2009 >> Memory error found copying between 0xf40350f8, 0xe7ba4808, difference =2000
[12068] Mon Jun 01 11:24:51 2009 >> Memory error found copying between 0xa72370f8, 0x15df6ed8, difference =2000
[12068] Mon Jun 01 11:24:52 2009 >> Memory error found copying between 0xc17326f8, 0x302f24d8, difference =2000
[15348] Mon Jun 01 11:24:54 2009 >> Memory error found copying between 0xba645908, 0x292055f8, difference =2000
[12068] Mon Jun 01 11:24:55 2009 >> Memory error found copying between 0xb2daed3c, 0x2196e0f8, difference =2000
[12068] Mon Jun 01 11:24:56 2009 >> Memory error found copying between 0xbce460f8, 0x2ba054b4, difference =2000
[12068] Mon Jun 01 11:24:56 2009 >> Memory error found copying between 0xedd38ff8, 0x5c8f83b4, difference =2000
[15344] Mon Jun 01 11:24:57 2009 >> Memory error found copying between 0xf6434294, 0xe9fa40f8, difference =2000
[15348] Mon Jun 01 11:24:59 2009 >> Memory error found copying between 0xb4e1cc08, 0x239dcbf8, difference =2000
[15348] Mon Jun 01 11:25:03 2009 >> Memory error found copying between 0xb889d0f8, 0x2745c82c, difference =2000
[15348] Mon Jun 01 11:25:03 2009 >> Memory error found copying between 0xba4410f8, 0x2900082c, difference =2000
[12068] Mon Jun 01 11:25:07 2009 >> Memory error found copying between 0x9db0915c, 0xc6c86f8, difference =2000
[12068] Mon Jun 01 11:25:08 2009 >> Memory error found copying between 0xec580a5c, 0x5b13fff8, difference =2000
[12068] Mon Jun 01 11:25:08 2009 >> Memory error found copying between 0xeff1665c, 0x5ead5bf8, difference =2000
[15348] Mon Jun 01 11:25:11 2009 >> Memory error found copying between 0xd6886ff8, 0x45446f58, difference =2000
[15348] Mon Jun 01 11:25:11 2009 >> Memory error found copying between 0xeebed798, 0x5d7ad6f8, difference =2000
[15348] Mon Jun 01 11:25:12 2009 >> Memory error found copying between 0xf25e20f8, 0x611a2058, difference =2000
[12068] Mon Jun 01 11:25:12 2009 >> Memory error found copying between 0xd3a33290, 0x425f30f8, difference =2000
[12068] Mon Jun 01 11:25:12 2009 >> Memory error found copying between 0xef0d06f8, 0x5dc90560, difference =2000
[15344] Mon Jun 01 11:25:13 2009 >> Memory error found copying between 0xf49aaff8, 0xe851acf8, difference =2000
[15348] Mon Jun 01 11:25:14 2009 >> Memory error found copying between 0x9b8ad1d8, 0xa46d0f8, difference =2000
[15348] Mon Jun 01 11:25:14 2009 >> Memory error found copying between 0xa24d11d8, 0x110910f8, difference =2000
[15348] Mon Jun 01 11:25:16 2009 >> Memory error found copying between 0xed0e87d8, 0x5bca86f8, difference =2000
[12068] Mon Jun 01 11:25:16 2009 >> Memory error found copying between 0xd3a33558, 0x425f30f8, difference =2000
[12068] Mon Jun 01 11:25:16 2009 >> Memory error found copying between 0xd3d6e558, 0x4292e0f8, difference =2000
[12068] Mon Jun 01 11:25:16 2009 >> Memory error found copying between 0xdef486f8, 0x4db08298, difference =2000
[12068] Mon Jun 01 11:25:19 2009 >> Memory error found copying between 0xc361a6f8, 0x321da328, difference =2000
[15344] Mon Jun 01 11:25:21 2009 >> Memory error found copying between 0xfa5746f8, 0xee0e4548, difference =2000
[15344] Mon Jun 01 11:25:22 2009 >> Memory error found copying between 0xfe4bd8c4, 0xf202d6f8, difference =2000
[15344] Mon Jun 01 11:25:22 2009 >> Memory error found copying between 0xf4460058, 0xe7fcfff8, difference =2000
[15348] Mon Jun 01 11:25:23 2009 >> Memory error found copying between 0xa15f26f8, 0x101b268c, difference =2000
[15348] Mon Jun 01 11:25:23 2009 >> Memory error found copying between 0xa2e5b164, 0x11a1b0f8, difference =2000
[15348] Mon Jun 01 11:25:23 2009 >> Memory error found copying between 0xbc4c7fa4, 0x2b087f38, difference =2000
[15344] Mon Jun 01 11:25:23 2009 >> Memory error found copying between 0xf4d48ff8, 0xe88b8eb4, difference =2000
[15348] Mon Jun 01 11:25:24 2009 >> Memory error found copying between 0xe88ad164, 0x5746d0f8, difference =2000
[12068] Mon Jun 01 11:25:25 2009 >> Memory error found copying between 0xdef486f8, 0x4db08694, difference =2000
[15348] Mon Jun 01 11:25:27 2009 >> Memory error found copying between 0xa06f87d4, 0xf2b86f8, difference =2000
[15348] Mon Jun 01 11:25:27 2009 >> Memory error found copying between 0xaa1087d4, 0x18cc86f8, difference =2000
[15348] Mon Jun 01 11:25:27 2009 >> Memory error found copying between 0xd220f1d4, 0x40dcf0f8, difference =2000
[15348] Mon Jun 01 11:25:31 2009 >> Memory error found copying between 0xfc686be8, 0x6b2465f8, difference =2000
[12068] Mon Jun 01 11:25:39 2009 >> Memory error detected between 0xb21aeff8, 0x20d6eff8 difference = 2000
[12068] Mon Jun 01 11:25:43 2009 >> Memory error found copying between 0xb21dd088, 0x20d9cff8, difference =2000
[12068] Mon Jun 01 11:25:43 2009 >> Memory error found copying between 0xd1e47088, 0x40a06ff8, difference =2000
[12068] Mon Jun 01 11:25:44 2009 >> Memory error found copying between 0xedec6088, 0x5ca85ff8, difference =2000
[12068] Mon Jun 01 11:25:44 2009 >> Memory error found copying between 0xef2e6788, 0x5dea66f8, difference =2000
[15344] Mon Jun 01 11:25:44 2009 >> Memory error found copying between 0xfa5746f8, 0xee0e423c, difference =2000
[15344] Mon Jun 01 11:25:44 2009 >> Memory error found copying between 0xfae9f4f8, 0xeea0f03c, difference =2000
[12068] Mon Jun 01 11:25:46 2009 >> Memory error found copying between 0xb69890f8, 0x25548e04, difference =2000
[12068] Mon Jun 01 11:25:47 2009 >> Memory error found copying between 0xf91f13ec, 0x67db10f8, difference =2000
[15348] Mon Jun 01 11:25:48 2009 >> Memory error detected between 0x9f1dcff8, 0xdd9cff8 difference = 2000
[15348] Mon Jun 01 11:25:48 2009 >> Memory error detected between 0xb73480f8, 0x25f080f8 difference = 2000
[15348] Mon Jun 01 11:25:49 2009 >> Memory error detected between 0xc4754bf8, 0x33314bf8 difference = 2000
[15348] Mon Jun 01 11:25:49 2009 >> Memory error detected between 0xce7460f8, 0x3d3060f8 difference = 2000
[15348] Mon Jun 01 11:25:49 2009 >> Memory error detected between 0xd3cfa0f8, 0x428ba0f8 difference = 2000

my memory is comfigured 3X 2GB and 3X 1GB the memory I was told was compatable as the mfg and version DDR3-1333 (PC-10666) is the same and the computer is see 9GB.

As my handle states I am in overmyhead what do I need to do to fix the errors the test is finding so far I am looking at 2000 errors and counting.

Could this also be causing a BSOD freeze issue I sometimes see after reboot and try logging into my user account?

I googled my problem and learned that if I removed all of the ram and placed each stick in one at a time into the lead memory slot and rerun the MemTest I would be able to determine which stick was the culprit.

So now that I have located it I off to my friendly Microcenter to get it replaced. I will update you as to whether or not this resolves the issue. However due to your keen intellect I have no doubt we have resolved my issue.


Thank you so much for your help and support H2SO4.

overmyhead said:

As my handle states I am in overmyhead what do I need to do to fix the errors the test is finding so far I am looking at 2000 errors and counting.

Click to expand...

I know it probably doesn't feel like it, but in a way you've been fortunate. The fact that memtest readily finds errors means at least you can be sure the hardware is suspect and there's no immediate need to tear your hair out looking at the software side of things - you'll need all the spare tearable hair for the hardware

Without wishing to get pointlessly philosophical, this is the downside of building your own machine. Put it all together, press the button, it produces a satisfying beep and boots... and then it starts doing mysterious s##t on ya. You can't call Dell/HP/whomever to complain, so you're left to your own devices to troubleshoot.

It may turn out to be fixable by tweaking voltages and improving the airflow or re-seating all componentry - that sort of thing. Check out similar hardware troubleshooting (voltage, temperature, frequencies, multipliers...) posts here by "stew2" or "smarteyeball". They offer a lot of advice on how to gauge your current hardware health.

Otherwise, there's the unfortunate possibility that the hardware is literally broken in a way that's unfixable, and replacement is the only way forward. In that case, I'd suggest starting with the RAM as the most likely culprit, although there's no guarantee.

overmyhead said:

Could this also be causing a BSOD freeze issue I sometimes see after reboot and try logging into my user account?

Click to expand...

Yes, absolutely. Unreliable physical memory can produce almost any effect or symptom. I'd suggest not spending more time on any of that until memtest gives you a 100% clean bill of health. Only then can you start to hope that any remaining symptoms may actually be software problems.

Good luck with it.

Quote from H2SO4:
I know it probably doesn't feel like it, but in a way you've been fortunate. The fact that memtest readily finds errors means at least you can be sure the hardware is suspect and there's no immediate need to tear your hair out looking at the software side of things - you'll need all the spare tearable hair for the hardware


Test of the replacement RAM is complete and all looks good, now only time well tell if this resolves my issuses.

What I can say is what a excellent mentor you have been H2SO4, if I could add more to your reputation I would but it tells me I need to spread some more lovin around before I can refirm the respect I have for you and your help.

It is one thing to google and find suggestion as to how to resolve issues but to have a site like this and individuals such as yourself willing to helpout and hand hold, this is truly a God send.

Thanks again

overmyhead said:

Quote from H2SO4:
I know it probably doesn't feel like it, but in a way you've been fortunate. The fact that memtest readily finds errors means at least you can be sure the hardware is suspect and there's no immediate need to tear your hair out looking at the software side of things - you'll need all the spare tearable hair for the hardware


Test of the replacement RAM is complete and all looks good, now only time well tell if this resolves my issuses.

What I can say is what a excellent mentor you have been H2SO4, if I could add more to your reputation I would but it tells me I need to spread some more lovin around before I can refirm the respect I have for you and your help.

It is one thing to google and find suggestion as to how to resolve issues but to have a site like this and individuals such as yourself willing to helpout and hand hold, this is truly a God send.

Thanks again

Click to expand...

I'm glad whenever I can help out others just a little through whatever knowledge I've gained through my many mistakes. Thank you sincerely for the rep and for your kind words

If there's anything still wrong with your machine, please come back and describe the symptom, and everyone here will try to help.