The key to a BSOD! This is what you have been looking for.
Thursday, June 29, 2006 at 10:02 pm
Windows XP Annoyances Discussion Forum
Posted by Josh
(2 messages posted)
---------------------------------------------------------------
If the following information is unavailable to you in the event viewer (described
below), you will need to confirm that logging is turned on for system failures.
You can confirm this by right-clicking "My Computer" and selecting Properties. Navigate
to the "Advanced" tab and click "Settings" in the Startup and Recovery box.
"Write an event to the system log" MUST be checked in order for a record of the crash
to show up in event viewer.
---------------------------------------------------------------
The filenames that the BSOD give you are the filenames that the problem is with.
If you fail to get the filename it shows, you can right-click on "My Computer" and
select Manage. From there you will expand the Event Viewer (on the left) and look
into the System section.
In the right pane, a list of events will be there. Most of them will be "Information."
Your going to look for an Information event that has "Save Dump" next to it.
You can narrow your search by looking at the date and time. It should appear around
the date and time the crash occured.
Double click on the Save Dump and read the Description. Once you learn the location
and name of the Dump file (.dmp) you will need something to open this special type
of file with.
You can use WinDBG, which is included in the Microsoft Debugging Tools kit (http://www.microsoft.com/whdc/devtools/debugging/default.mspx).
Once you install the tools, you will need to run WinDBG from the start menu (Start>
All Programs> Debugging Tools for Windows> WinDBG). Select File, Open Crash Dump.
Navigate to the location of the dump file you found earlier in Event Viewer and open
it (Usually C:\WINDOWS\Minidump\dumpname.dmp).
Now you have the information from the dump file.
You should copy the name of the file that produced the BSOD and google it to get
more information. You need to know what the file is used for... what it belongs to.
Once you have this new information, you can begin fixing your problem.
Usually the filename will end up belonging to a specific device or goes in cooperation
with a specific device.
This is the device you should be troubleshooting.
You may need to reinstall the drivers for this device, or reinstall the device completely.
If it is a driver problem, your driver may be incompatable with your operating system
or may be having problems with new updates to your operating system (such as a new
service pack update).
If you continue to have problems after troubleshooting the device, you may want to
try reversing a service pack update.
Be forewarned, when reversing service pack updates you may risk corrupting your operating
system even further. The installation or uninstallation of ANY service pack or update
to your OS should go completely uninterrupted and without fault.
I hope this has helped to solve all of your BSOD problems, these are some of the
steps a computer technician will use to solve this type of problem.
Godbless and Goodluck to all of you.
- Written in response to:
- re: BSOD, win32k.sys (koyak: Friday, June 23, 2006 at 9:50 am)
Responses to this message:
|
|
All messages in this thread [show all]
 |  | | | | |  | Confused (Adri1456: Fri, May 14, 2004, 3:29 pm) |
| | | | | |  | Crash (greine12: Tue, Apr 6, 2004, 4:57 pm) |
| | | | | | | | | re: Crash (MadMan: Sat, Apr 10, 2004, 1:19 pm) |
| | | | | | | The key to a BSOD! This is what you have been looking for. (Josh: Thu, Jun 29, 2006, 10:02 pm) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
