Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Howto: Troubleshoot STOP codes
New Posts  All Forums:Forum Nav:

Howto: Troubleshoot STOP codes

post #1 of 2
Thread Starter 
Hello all,

In trying to find a way to contribute to the forum community, I thought I would post some info that I use on a weekly basis for my job.

How to find drivers that are causing BSOD.
When a BSOD stop message indicates a driver problem. You may need to use pstat.exe to identify the faulting driver. For example, the computer stopped with the blue screen message "STOP: IRQL_NOT_LESS_OR_EQUAL 0x000000d1 (0xc0c1400c, 0x00000001, 0x00000000, 0x8011c627). If you do not know the stop message the Windows System Event log will log the error under the source "Save Dump" and show the error code (0x000000d1).
You can look up the error code on the MSDN bug check code list here. One of the parameters of the stop code (the 4 parameters are the hex numbers listed in parentheses) often is the memory address of the driver that caused the error. Pstat can help you find the driver. Google pstat.exe if you do not have it. You can get it from the Microsoft site too in their Support Tools.

Copy pstat to the c:\\%windows directory%\\system32\\

Open a command prompt.

Type "pstat > c:\\pstat.txt"

Open pstat.txt.

The last table in the pstat.txt looks like this:

ModuleName Load Addr Code Data Paged LinkDate
------------------------------------------------------------------------------
ntoskrnl.exe 804D7000 477184 93440 1243392 Tue Mar 01 18:59:37 2005
hal.dll 806EC000 29312 6400 25088 Wed Aug 04 00:59:04 2004
KDCOM.DLL F8A37000 2560 256 1280 Fri Aug 17 15:49:10 2001
BOOTVID.dll F8947000 5632 3584 0 Fri Aug 17 15:49:09 2001
ACPI.sys F84E8000 110336 11008 41984 Wed Aug 04 01:07:35 2004
WMILIB.SYS F8A39000 512 0 1280 Fri Aug 17 16:07:23 2001
pci.sys F84D7000 16000 1664 34176 Wed Aug 04 01:07:45 2004
isapnp.sys F8537000 8704 768 18688 Fri Aug 17 15:58:01 2001



Copy this table into a spreadsheet program (Excel) and sort the list by Load Address. The module name is the name of the driver file. The load address is the address in memory that the module loaded. Memory loads from the op down. So the first driver would load at FFFFFFFF.

The stop messages referenced memory address will be less than the address that the faulting module loaded. For example, if the one of the stop message parameters lists the memory address that caused the fault was F84D6FE0 we would see from the table that the cause of the error was pci.sys, which loaded at F84D7000. Once you find the driver, you can search for updates or reinstall.


Hope this helps someone out.
Frankenbox
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core 2 Dou E8500 EVGA EVGA 9800GTX+ 512MB 4GB 
Hard DriveOSMonitorCase
Two 80GB SATA Raid 0 Vista 64bit ASUS 22" Widescreen LCD Futureware Rackmount case 
  hide details  
Reply
Frankenbox
(13 items)
 
  
CPUMotherboardGraphicsRAM
Core 2 Dou E8500 EVGA EVGA 9800GTX+ 512MB 4GB 
Hard DriveOSMonitorCase
Two 80GB SATA Raid 0 Vista 64bit ASUS 22" Widescreen LCD Futureware Rackmount case 
  hide details  
Reply
post #2 of 2
good stuff thanks for contributing
    
CPUMotherboardGraphicsRAM
Intel I7 2600k Asus p8p67-Deluxe Zotac GTX780 6GB OC G-skill Ripjaws 1866 
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 EVO 250 Samsung EVO 120 Western Digital 1TB Black Lite On 20x DVD RW 
CoolingOSOSOS
XSPC RayStorm + 360Extreme Rad Arch Linux Windows 8.1 x64 WindowsRE 
MonitorKeyboardPowerCase
Asus PB278Q ThermalTake Meka G1 Evga SuperNova 1000 P2 Xigmatek Elysium 
MouseMouse PadAudio
Logitec G500 Gaming Mouse Ultra Pad Fiio E-17 + ATH-M50 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel I7 2600k Asus p8p67-Deluxe Zotac GTX780 6GB OC G-skill Ripjaws 1866 
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 EVO 250 Samsung EVO 120 Western Digital 1TB Black Lite On 20x DVD RW 
CoolingOSOSOS
XSPC RayStorm + 360Extreme Rad Arch Linux Windows 8.1 x64 WindowsRE 
MonitorKeyboardPowerCase
Asus PB278Q ThermalTake Meka G1 Evga SuperNova 1000 P2 Xigmatek Elysium 
MouseMouse PadAudio
Logitec G500 Gaming Mouse Ultra Pad Fiio E-17 + ATH-M50 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Howto: Troubleshoot STOP codes