Christopher at 03:45, 31 August 2016

2016-08-31T03:45:09Z

Christopher at 03:44, 31 August 2016

2016-08-31T03:44:45Z

Christopher: Redirected page to StableBit DrivePool System Freeze

2015-05-17T23:27:40Z

Redirected page to StableBit DrivePool System Freeze

New page

#REDIRECT [[StableBit DrivePool System Freeze]]

← Older revision		Revision as of 03:45, 31 August 2016
Line 36:		Line 36:


−	''Dumps are only used to fix bugs in StableBit ~~DrivePool~~ and for no other purpose.''	+	''Dumps are only used to fix bugs in StableBit CloudDrive and for no other purpose.''

	''The dump files are extremely large and may take a while to upload. You may want to ZIP the file up before sending it. Do not stop until you see a message indicating success.''		''The dump files are extremely large and may take a while to upload. You may want to ZIP the file up before sending it. Do not stop until you see a message indicating success.''

← Older revision		Revision as of 03:44, 31 August 2016
Line 1:		Line 1:
−	~~#REDIRECT~~ [[StableBit DrivePool ~~System Freeze]~~]	+	You should prepare your server to collect a manually initiated memory dump and send them to StableBit for examination.
		+
		+	== Enabling a Manual System Crash ==
		+	First, we will configure your server to generate a kernel memory dump when you press a special key combination on the keyboard. The memory dump records the entire system state at the time of the freeze and can be analyzed to determine the cause.
		+
		+	== What You Will Need ==
		+	* Physical access to the server.
		+	* A USB or PS/2 keyboard connected to the server.
		+	* The ability to reproduce the system freeze.
		+
		+	== Configuring the Server ==
		+	* Place these files on a server share:
		+	** [http://dl.covecube.com/Assets/Reg/bugcheck_on.reg bugcheck_on.reg]
		+	** [http://dl.covecube.com/Assets/Reg/bugcheck_off.reg bugcheck_off.reg]
		+	* Log in as Administrator with Remote Desktop to your server ([[StableBit_DrivePool_Q7200705\|Q7200705]]).
		+	* Double click on the '''bugcheck_on.reg''' file to enable manual system crashes on the server.
		+	* Connect a PS/2 or a USB keyboard to the server if it doesn't have one connected already.
		+	* Reboot the server.
		+
		+	== Initiating the Memory Dump ==
		+	* Reproduce the system freeze and '''hold down the rightmost CTRL key, and press the SCROLL LOCK key twice''' on the keyboard connected to the server when you're sure that the system has locked up.
		+	*: This will write out a '''C:\Windows\MEMORY.DMP''' file.
		+	* Reboot the server and upload the C:\Windows\MEMORY.DMP file using the form below with a description of the freeze.
		+
		+	For more information on manual system crashes see: [http://msdn.microsoft.com/en-us/library/windows/hardware/ff545499(v=vs.85).aspx MSDN]
		+
		+	After you're done, you can disable the manual system crash key combination by double clicking on '''bugcheck_off.reg'''.
		+
		+	== Submit a crash dump ==
		+	Locate the MEMORY.DMP file in your ''C:\Windows'' folder on the server and upload it using the widget below.
		+
		+
		+
		+	[https://www.dropbox.com/request/lrCAeFa2EH9VSJqP3QLM Click here to submit files using Dropbox (you don't need to an account with Dropbox)]
		+
		+
		+
		+	''Dumps are only used to fix bugs in StableBit DrivePool and for no other purpose.''
		+
		+	''The dump files are extremely large and may take a while to upload. You may want to ZIP the file up before sending it. Do not stop until you see a message indicating success.''
		+
		+	== Open a support contact thread (optional) ==
		+	We get notified of dump submissions automatically. If you'd like, you can open a contact thread at [http://stablebit.com/contact http://stablebit.com/contact].
		+	This is optional, because we don't need a ticket to check the dumps. However, to give you feedback, this is the best way to do so.

StableBit CloudDrive System Freeze - Revision history

Christopher at 03:45, 31 August 2016

Christopher at 03:44, 31 August 2016

Christopher: Redirected page to StableBit DrivePool System Freeze