Solved BSOD - 0x0000001e - 0x000000d1

[cdwriter2]

Hello, my brother has been getting Bluescreens, here's the dump folder that might help.

 

[koolkat77]

Hi.

Most of the BSOD-s seem to be caused by Arctosa.sys - Razer Arctosa Keyboard Driver from 2009. Quite old!

lmvm Arctosa
start             end                 module name
fffff880`08724000 fffff880`08728d80   Arctosa  T (no symbols)           
    Loaded symbol image file: Arctosa.sys
    Image path: \SystemRoot\system32\drivers\Arctosa.sys
    Image name: Arctosa.sys
    Timestamp:        Wed Aug 19 13:57:20 2009 (4A8BB060)
    CheckSum:         00007232
    ImageSize:        00004D80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Here's the link and method for updating the driver:

Driver Reference Table - Arctosa.sys

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:

• How to Clean Left Over Driver Files with Driver Sweeper

If updating the driver for this hardware component does not help I'd recommend using another keyboard.

Update Atheros network adapter driver in the same method mentioned above:

lmvm athrx
start             end                 module name
fffff880`06e0a000 fffff880`06f87000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Mon Oct 05 22:33:57 2009 (4ACA1FF5)
    CheckSum:         0017C3B2
    ImageSize:        0017D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If its wireless, match your device from here:

• ATHEROS Wireless drivers for Windows

If its not a wireless, match your device from here:

• ATHEROS Network drivers for Windows
  
  ATHEROS Wireless drivers for Windows

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Daemon Tools:

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Let us know the results.

 

[koolkat77]

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Mon Feb 18 14:38:17.119 2013 (UTC + 6:00)
System Uptime: 0 days 2:42:03.617
Probably caused by : Arctosa.sys ( Arctosa+11b7 )
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED  
Usual causes:  Device driver, hardware, System service, compatibility, 
Remote control programs, memory, BIOS
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_Arctosa+11b7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Tue Feb 12 11:06:21.866 2013 (UTC + 6:00)
System Uptime: 0 days 0:27:18.036
Probably caused by : Arctosa.sys ( Arctosa+11b7 )
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED  
Usual causes:  Device driver, hardware, System service, compatibility, 
Remote control programs, memory, BIOS
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_Arctosa+11b7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Tue Feb  5 11:18:34.020 2013 (UTC + 6:00)
System Uptime: 0 days 10:33:15.581
Probably caused by : athrx.sys ( athrx+59836 )
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL 
Usual causes:  Device driver
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xD1_athrx+59836
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

 

[cdwriter2]

Hi there,

Thanks for the quick and detailed reply.

My brother has finished all of the steps and his computer hasn't had a crash or freeze since so it's looking good. Early days though, of course.

If anything happens I'll let you know.

Thanks again,
Caleb

 

[koolkat77]

Good to hear.

Keep us posted.