Tech Support Forum - View Single Post

**jcgriff2** · 05-23-2008, 03:15 PM

Hi Sean. . .

I have been processing your memory dumps during the last 24 hours and I must say that I am rather puzzled at this time - for more than one reason. The first set of kernel mini dump debugger results that you posted in THIS THREAD are dramatically different than those kernel dumps that you attached to this thread itself.

The first two BSODs from May 15, 2008, undoubtedly show that symevent.sys, a Symantec Norton driver failed; however it did so under the executing processes TurbineLauncher, related to gaming - possibly Lord of the Rings, psqltray.exe, UPEK, Inc., Protector Suite QL, and repair.exe, a tweaking utility which most likely belongs to World of Warcraft.

The subsequent memory dumps indicate hardware failure - especially the system crash on May 18, 2008, 20:01 hours - something that I did not find in the first two dumps. Because the Symantec related dumps were the only ones available at the time, I find these new inclusive results to be rather far beyond the Symantec fix offered by our Microsoft MVP visitor found HERE. Furthermore, the fix provided therein does not specify a compatibility with Vista, which does not necessarily mean that it is not. Check the version of Norton that you have and assure its compatibility with Vista.

Now... the next area that I found initially confusing related to exactly which system(s) I/we are dealing with. Two of the reports - Belarc and dxdiag - show the system to be a Dell XPS720 in a pre-Vista SP1 state. The other reports show a system of unknown origin - but to have been updated with Vista SP1. I then came out here to the forum and saw your post regarding the re-install of Vista and things fell into place.

Here are the memory dump results:

Code:


05/18/2008 01 07:27 memory_corruption/installer.exe BugCheck 1A, {41284, 85eb001, 6fdd, c0802000}

05/18/2008 02 20:01 hardware/Crysis.exe BugCheck 124, {0, 847183f0, f2000040, 800}

05/19/2008 01 15:58 memory_corruption/explorer.exe  BugCheck 1A, {41284, 2575001, 1b6f, c0802000}

05/19/2008 02 19:00 memory_corruption/TurbineLauncher BugCheck 1A, {5003, c0802000, 673e, 6658e7d}

         
05/20/2008 01 09:05 memory_corruption/WinSAT.exeBugCheck 1A, {41284, 86c5001, 5b0d, c0801000}               


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 847183f0, Address of WHEA_ERROR_RECORD structure
Arg3: f2000040, High 32 bits of MCi_STATUS MSR for the MCA bank that had
	the error
Arg4: 00000800, Low  32 bits of MCi_STATUS MSR for the MCA bank that had
	the error


Error Record @ FFFFFFFF847183F0 has 3 sections
   Severity        : Fatal
   Validation Bits : 0x00000002 timestamp
   Total Length    : 0x6C2
   Timestamp       : 12/25/6174 13:39:33.476
   Creator         : Unknown Creator 52455043-0201-FFFF-FFff-030001000000
   Notify Type     : 00000002-06C2-0000-0B01-000013050814
   Record ID       : 0x01C8B8DA80F9154A
   Flags           : 0x00000000

The May 15, 2008, BSOD with the bugcheck error of 124 is the one that I especially took note of. It involves the Windows Hardware Error Architecture or WHEA. Please see THIS post that I made on WHEA just a few days ago.

I would definitely keep in touch with Dell regarding this system that is soon to be out of warranty. The hardware 124 error is puzzling to say the least. I have only begun to see them recently in kernel mini dumps and do not really know alot about them. There is an Event Viewer log specific to WHEA - The Microsoft Windows Kernel WHEA - and yours shows just four entries:

Code:


WHEA successfully initialized.
   4 error sources are active
   Error record format version is 10.

One last item that I noticed is the size of your page file - 10GB. I know that you have 4GB of installed RAM and are obviously using the 2.5x formula for the size of the page file. I would simply say that this may be too aggressive in your quest for system optimization. Did you set this or did Vista? I would advise you to regularly defrag your hard drive as there must be a great deal of thrashing (moving to/from RAM/Virtual Memory)occurring with the pagefile. Also, I would strongly suggest that you partition your 750GB primary hard drive as keeping it all as drive c: would negate system optimization. Finally, take a look inside of msinfo32 as it contains information that you may find useful.

This is all that I have for you right now. Please let me know if subsequent BSODs occur... and most certainly any outcome to this. It is greatly appreciated. Thank you.

Regards. . .

jcgriff2 (JC)

05-23-2008, 03:15 PM	#8 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, S.O. . . . . . . . SHAMEFUL ACTIVITIES INDEED ! ! ! Posts: 10,164 OS: Windows 7, Vista Ultimate My System	Re: Vista BSOD Hi Sean. . . I have been processing your memory dumps during the last 24 hours and I must say that I am rather puzzled at this time - for more than one reason. The first set of kernel mini dump debugger results that you posted in THIS THREAD are dramatically different than those kernel dumps that you attached to this thread itself. The first two BSODs from May 15, 2008, undoubtedly show that symevent.sys, a Symantec Norton driver failed; however it did so under the executing processes TurbineLauncher, related to gaming - possibly Lord of the Rings, psqltray.exe, UPEK, Inc., Protector Suite QL, and repair.exe, a tweaking utility which most likely belongs to World of Warcraft. The subsequent memory dumps indicate hardware failure - especially the system crash on May 18, 2008, 20:01 hours - something that I did not find in the first two dumps. Because the Symantec related dumps were the only ones available at the time, I find these new inclusive results to be rather far beyond the Symantec fix offered by our Microsoft MVP visitor found HERE. Furthermore, the fix provided therein does not specify a compatibility with Vista, which does not necessarily mean that it is not. Check the version of Norton that you have and assure its compatibility with Vista. Now... the next area that I found initially confusing related to exactly which system(s) I/we are dealing with. Two of the reports - Belarc and dxdiag - show the system to be a Dell XPS720 in a pre-Vista SP1 state. The other reports show a system of unknown origin - but to have been updated with Vista SP1. I then came out here to the forum and saw your post regarding the re-install of Vista and things fell into place. Here are the memory dump results: Code: 05/18/2008 01 07:27 memory_corruption/installer.exe BugCheck 1A, {41284, 85eb001, 6fdd, c0802000} 05/18/2008 02 20:01 hardware/Crysis.exe BugCheck 124, {0, 847183f0, f2000040, 800} 05/19/2008 01 15:58 memory_corruption/explorer.exe BugCheck 1A, {41284, 2575001, 1b6f, c0802000} 05/19/2008 02 19:00 memory_corruption/TurbineLauncher BugCheck 1A, {5003, c0802000, 673e, 6658e7d} 05/20/2008 01 09:05 memory_corruption/WinSAT.exeBugCheck 1A, {41284, 86c5001, 5b0d, c0801000} WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 00000000, MCA_ASSERT Arg2: 847183f0, Address of WHEA_ERROR_RECORD structure Arg3: f2000040, High 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arg4: 00000800, Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Error Record @ FFFFFFFF847183F0 has 3 sections Severity : Fatal Validation Bits : 0x00000002 timestamp Total Length : 0x6C2 Timestamp : 12/25/6174 13:39:33.476 Creator : Unknown Creator 52455043-0201-FFFF-FFff-030001000000 Notify Type : 00000002-06C2-0000-0B01-000013050814 Record ID : 0x01C8B8DA80F9154A Flags : 0x00000000 The May 15, 2008, BSOD with the bugcheck error of 124 is the one that I especially took note of. It involves the Windows Hardware Error Architecture or WHEA. Please see THIS post that I made on WHEA just a few days ago. I would definitely keep in touch with Dell regarding this system that is soon to be out of warranty. The hardware 124 error is puzzling to say the least. I have only begun to see them recently in kernel mini dumps and do not really know alot about them. There is an Event Viewer log specific to WHEA - The Microsoft Windows Kernel WHEA - and yours shows just four entries: Code: WHEA successfully initialized. 4 error sources are active Error record format version is 10. One last item that I noticed is the size of your page file - 10GB. I know that you have 4GB of installed RAM and are obviously using the 2.5x formula for the size of the page file. I would simply say that this may be too aggressive in your quest for system optimization. Did you set this or did Vista? I would advise you to regularly defrag your hard drive as there must be a great deal of thrashing (moving to/from RAM/Virtual Memory)occurring with the pagefile. Also, I would strongly suggest that you partition your 750GB primary hard drive as keeping it all as drive c: would negate system optimization. Finally, take a look inside of msinfo32 as it contains information that you may find useful. This is all that I have for you right now. Please let me know if subsequent BSODs occur... and most certainly any outcome to this. It is greatly appreciated. Thank you. Regards. . . jcgriff2 (JC) __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! !