Vista BSOD

Sybrsean · 05-19-2008, 10:44 AM

I recieved a refurbished Dell 720H2C with raid 0. I switched it to Raid 1 and used the OEM OS install disk from Dell to reload. I've done this over 9 times in different ways based on various forums related to each type of BSOD. No matter how I load the machine or what drivers I seem to use the machine BSOD under load. (Hasn't happended at idle yet). It's even crashed during the windows load.

I've trouble shot this with Dell, reloaded using there exact directions and still get BSOD (most were noted as SATA driver issues in the Problem Reports and Solutions (PRoS) in Vista. The solutions are listed as "install SP1). No matter which order I load drivers, WU etc. I still get BSOD and even with SP1 I get the PRoS saying Sata is an issue.

I've ran hardware diagnostics for over 24 hours with no errors. Attached are the last two dumps from the most recent reload. At this point the computer is loaded with the most up to date drivers direct from the manufatures for the MB, Video and Sound.

Thanks for your help.

The dump files were renamed .txt just so they could be uploaded. You'll need to rename them .dmp to see in the degugger.

**jcgriff2** · 05-19-2008, 12:50 PM

Hi Sybrsean. ..

Welcome to the Tech Support Forum - Vista Support!

Thanks for starting your own thread. Everything herein will pertain to you and your system trouble - and to no one else.

Besides the dumps that you attached, I would like to get the following:

• Belarc Advisor report saved as a web page (html, mht (IE7/8) or as a 2007 (only) Word document docx. You can download Belarc HERE

• DXDiag report - START | type dxdiag into the Start Search box | right-click on dxdiag.exe | select Run as Administrator | respond to User Access Control prompt | Save as a text file.

• MS32info NFO file - START | type msinfo32 into the Start Search box | right-click on msinfo32.exe | select Run as Administrator | respond to User Access Control prompt | System Information will then come up | save the report in System Information File (NFO) format by selecting File, then Save As.

• Event Logs - Get them all - dozens -They are located in: c:\windows\system32\winevt\logs.

Zip them all up and send to me - see my PM for instructions.

Regards. . .

jcgriff2

Sybrsean · 05-20-2008, 11:10 AM

Dell wanted me to test the ram one stick at a time however, with the deadline looming that I can return the computer I just went out and purchased 4GB of new ram and started over. Deleted the raid, recreated it, installed windows. (Crashed during install). Completed install, downloaded 8800GTX drivers from Dell and here we are again.

I've included the dmp from the windows install in the zip as well as all the other itmes you requested.

Sybrsean · 05-20-2008, 11:28 AM

P.S. I just realized that in the last time I tried the most upto date drivers for the MB and SATA from Nvidia, I was using the series 6 Nforce drivers! Not the 5 series that the Berlarc Advisor says I have. I thought 680i meant 6 series drivers! Not that this is a total resolution since it crashed during this last reinstall (before there were anything but the OEM OS reinstall disks driver were in).

Now I know that Dell reps think that I can just pop in the disk and I should be good to go. But I've read otherwise. One person from nforcers.com says that any OEM Vista SATA driver that get loaded mess things up and that becuase the new drivers are so different when you update over the top of them you'll still have BSOD issues and that you should load the updated drivers during install. Do you know if this is true?

Just thought I'd update.

Sybrsean · 05-20-2008, 04:43 PM

No luck. BSOD again loading LOTRO. But I can say this has been consistently the Program that had been crashing it. After loading the game with no issues the launcher goes to patch the and update the games files. Somewhere around 6000 files into the 14000 it needs to download then patch it always BSOD's with the same error.

I've attached this dmp file. along with a new zip of everything updated.

Sybrsean · 05-20-2008, 05:37 PM

Not sure if I posted this in the previous (wrong) forum, but I wanted to make it available regardless as it's knid of a record of 8 of the first BSOD that I started to record. As you can see all of them are 1A Stops with either 41284 as the first argument or 5003. Since these are all "Memory" Errors and I still crashed with all new memory sticks, Dell has agreed to replace the MB I should have this by Thurs or Fri I'm hoping.

Regardless if you find anthing in all the info I've sent that points to something other than hardware please let me know! :o)

Sybrsean · 05-23-2008, 10:45 AM

Dell replaced the motherboard yesterday. Thus far... no BSOD. Not during windows load, not with the most updated drivers, not during game loads....

Fingers crossed, but it looks like this was the issue atm.

**jcgriff2** · 05-23-2008, 02: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-19-2008, 12:50 PM	#2 (permalink)
jcgriff2 Moderator, Microsoft Support Join Date: Sep 2007 Location: New Jersey / Southern California Posts: 7,884 OS: Windows 7 RC, Vista Ultimate My System	Re: Vista BSOD Hi Sybrsean. .. Welcome to the Tech Support Forum - Vista Support! Thanks for starting your own thread. Everything herein will pertain to you and your system trouble - and to no one else. Besides the dumps that you attached, I would like to get the following: • Belarc Advisor report saved as a web page (html, mht (IE7/8) or as a 2007 (only) Word document docx. You can download Belarc HERE • DXDiag report - START \| type dxdiag into the Start Search box \| right-click on dxdiag.exe \| select Run as Administrator \| respond to User Access Control prompt \| Save as a text file. • MS32info NFO file - START \| type msinfo32 into the Start Search box \| right-click on msinfo32.exe \| select Run as Administrator \| respond to User Access Control prompt \| System Information will then come up \| save the report in *System Information File (NFO)* format by selecting File, then Save As. • Event Logs - Get them all - dozens -They are located in: c:\windows\system32\winevt\logs. Zip them all up and send to me - see my PM for instructions. Regards. . . jcgriff2 __________________ Expecting a reply from me and it has been > 48 hours ? Send a PM containing a link to your thread Due to a family matter, my availability will be limited through ~ July 31, 2009

05-20-2008, 11:28 AM	#4 (permalink)
Sybrsean Registered User Join Date: May 2008 Posts: 7 OS: Vista Ultimate 32	Re: Vista BSOD P.S. I just realized that in the last time I tried the most upto date drivers for the MB and SATA from Nvidia, I was using the series 6 Nforce drivers! Not the 5 series that the Berlarc Advisor says I have. I thought 680i meant 6 series drivers! Not that this is a total resolution since it crashed during this last reinstall (before there were anything but the OEM OS reinstall disks driver were in). Now I know that Dell reps think that I can just pop in the disk and I should be good to go. But I've read otherwise. One person from nforcers.com says that any OEM Vista SATA driver that get loaded mess things up and that becuase the new drivers are so different when you update over the top of them you'll still have BSOD issues and that you should load the updated drivers during install. Do you know if this is true? Just thought I'd update. Last edited by Sybrsean; 05-20-2008 at 11:32 AM.

05-23-2008, 10:45 AM	#7 (permalink)
Sybrsean Registered User Join Date: May 2008 Posts: 7 OS: Vista Ultimate 32	Re: Vista BSOD Dell replaced the motherboard yesterday. Thus far... no BSOD. Not during windows load, not with the most updated drivers, not during game loads.... Fingers crossed, but it looks like this was the issue atm.

05-23-2008, 02:15 PM	#8 (permalink)
jcgriff2 Moderator, Microsoft Support Join Date: Sep 2007 Location: New Jersey / Southern California Posts: 7,884 OS: Windows 7 RC, 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) __________________ Expecting a reply from me and it has been > 48 hours ? Send a PM containing a link to your thread Due to a family matter, my availability will be limited through ~ July 31, 2009