Hi Everyone, We have Windows 2008 R2 64 Bit OS and the server rebooted 4 times and creating following error. I think it is the memory issue because there are 4 Event ID 46 has created. I mentioned error below for your information. Please check and reply .... Also I need one more clarification. I cant install in server windbg tool, its required many approval process but I can install Windbg tool in my machine but my machine is x86, whether I can install x86 windbg version and verify the server dump file which is x64 bit? The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800dfbd028, 0x00000000fe000000, 0x000000000001009f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062111-51917-01. Event ID : 46 A fatal hardware error has occurred. Component : Memory Error Source : Machine Check Exception Thank you, Yuvi.....

Bug Check Code 0x124: http://msdn.microsoft.com/en-us/library/ff557321(v=VS.85).aspx A fatal hardware error occured. Use Microsoft Skydrive to upload C:\Windows\MEMORY.DMP file after compressing it. Once done, post a link here. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

Bug Check Code 0x124: http://msdn.microsoft.com/en-us/library/ff557321(v=VS.85).aspx A fatal hardware error occured. Use Microsoft Skydrive to upload C:\Windows\MEMORY.DMP file after compressing it. Once done, post a link here. Or either use the BlueScreenView application found here http://www.nirsoft.net/utils/blue_screen_view.html to load the dump file and try finding out the driver/module which caused the crash

Hi, You need to check the dump file from 64 bit OS on a 64 bit machine. You can also capture memory dumps for 32-bit processes on an x64 machine. For more information, please refer to the following links: Capturing memory dumps for 32-bit processes on an x64 machine http://blogs.msdn.com/b/tess/archive/2010/09/29/capturing-memory-dumps-for-32-bit-processes-on-an-x64-machine.aspx How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 As this issue needs debugging while we do not provide debugging support in this forum, if you would like to perform debugging, please contact Microsoft Customer Support Service (CSS). To obtain the phone numbers for specific technology request, please refer to the website listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US, please refer to http://support.microsoft.com for regional support phone numbers. Thanks. NinaPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.