Need Help Fixing this BugCheck Event
Hello Klosh, The below info is for your reference. Analyze the dump files and try to find the file, which is cause of this server shutdown. Based on the files you can go for new HW drivers update and new hot fixes. Below links are for your reference while analyzing dump file: for dump file analysis download windebuger SW and analyze the *.dmp file to know the cause of server shutdown.Links for the software: https://skydrive.live.com/#cid=63D5AB5243DB43E7&id=63D5AB5243DB43E7%21120 or http://www.windbg.org/ Link for the steps to analyse a dmp file: http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx#3476888\ Another useful link for bugcheck codes :http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx Regards, Ravikumar P
June 30th, 2012 8:21am

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-06-26T23:21:41.000000000Z" /> <EventRecordID>4710</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>CalebLosh-PC</Computer> <Security /> </System> - <EventData> <Data Name="param1">0x0000001e (0xffffffffc0000005, 0xfffff8000315a790, 0x0000000000000000, 0xffffffffffffffff)</Data> <Data Name="param2">C:\windows\MEMORY.DMP</Data> <Data Name="param3">062612-21075-01</Data> </EventData> </Event> What can I do to fix this?
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2012 10:12pm

Hello Klosh, The below info is for your reference. Analyze the dump files and try to find the file, which is cause of this server shutdown. Based on the files you can go for new HW drivers update and new hot fixes. Below links are for your reference while analyzing dump file: for dump file analysis download windebuger SW and analyze the *.dmp file to know the cause of server shutdown.Links for the software: https://skydrive.live.com/#cid=63D5AB5243DB43E7&id=63D5AB5243DB43E7%21120 or http://www.windbg.org/ Link for the steps to analyse a dmp file: http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx#3476888\ Another useful link for bugcheck codes :http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx Regards, Ravikumar P
July 2nd, 2012 10:21pm

Hi, Generally, you may update BIOS and other hardware drivers first. If it does not work, you may analyze them with Debugging Tools by yourself. You can install it and its Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the Search bar and press Enter. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click OK. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click Start, type %SystemRoot%\Minidump" (without quotation marks) in Search bar and press Enter. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Arthur Li TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2012 2:25am

Hi, Generally, you may update BIOS and other hardware drivers first. If it does not work, you may analyze them with Debugging Tools by yourself. You can install it and its Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the Search bar and press Enter. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click OK. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click Start, type %SystemRoot%\Minidump" (without quotation marks) in Search bar and press Enter. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Arthur Li TechNet Community Support
July 3rd, 2012 2:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics