As we know, Microsoft create the Blue Screen Of Death ( BSOD ) is to immediately stop your Windows operation to prevent more damage to your software and hardware. When the BSOD appear, it will show your the technical error code and create minidump file to your windows folder in directory : C:\WINDOWS\Minidump. But, do you know how to read or trace the error by open the dump file or trace the code by doing some searching on the internet? Actually, It is not and easy task. Here, we will show you how to trace and fix the BSOD error in Windows XP, Windows Vista & Windows 7 and find the culprit file or driver that cause this error.

First step, you must make sure you enable the "Write Debugging Information" in creating the minidump file during the error. To enable this, go to your Control Panel, click on the "System" icon and the system properties window will appear. Next, go to the "Advanced" tab and click the "Startup and Recovery" setting button. After that another window will appear. In the "Write debugging Information" section, set the dropdown box to "Small memory Dump 64Kb" and uncheck the "Automatically Restart" box. Click OK and Apply to save the setting.

After enabling the "Write Debugging Information" option, go to Resplendence website to download the WhoCrashed software. This powerful software can trace the BSOD error by analyzing the minidump file like :

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
Stop 0x00000024 or NTFS_FILE_SYSTEM
Stop 0x0000002E or DATA_BUS_ERROR
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
Stop 0x00000079 or MISMATCHED_HAL
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
Stop 0xC2 or BAD_POOL_CALLER
Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

To install this software, you need to download and install Windows Debugging Package from Microsoft because WhoCrashed relies with this software. After you install both software, you can start analyzing the error by clicking the "Analyze" button. After a few seconds, you may see the analysis result by scroll down the page. Below is the analyze report with description:

On Thu 4/22/2010 1:31:59 AM your computer crashed ( Time description )
This was likely caused by the following module: ( file that cause the error ) ewusbmdm.sys
Bugcheck code ( Technical Error Code ): 0x1000007E (0xC0000005, 0x805454F3, 0xAD705B2C, 0xAD705828)
Error ( BSOD error name) : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file ( minidump file that was analyzed by this software) :  C:\WINDOWS\Minidump\Mini042210-01.dmp
file path ( Location of the error file ): C:\WINDOWS\system32\drivers\ewusbmdm.sys
product (Hardware Name if problem cause by hardware ): Huawei Technologies Co., Ltd. USB Modem/Serial Device Driver
company (hardware manufacturer): Huawei Technologies Co., Ltd.
description (Type of hardware) : USB Modem/Serial Device Driver

If your BSOD cause you cannot login to your Windows, you can try to repair it using recovery console using Windows CD or enter your using Windows Safe Mode function then use the WhoCrashed to trace the error. With this error report tracer, you may narrowed up your problem questionnaire and directly target to the root that cause the error. This also can save up your precious time.