Blue Screen of Death - DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL (SynTP.sys) Satellite P55-A5200

I am running Windows 8.1 Pro.
Frequently over the last several days, when I wake my computer from sleep, I get the blue screen of death with error DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL (SynTP.sys) which forces a restart.
Because of the SynTP.sys error, I have updated the track pad driver several times, using the latest driver from Toshiba (Syanptics 17.0.10.1 2013-09-24) and have alternatively used the recommended drive from Windows 8.1 (Synaptics 17.0.8.21 dated 2013/08/23). Neither driver helped.
I have reinstalled Windows 8.1 Pro amongst other attempted soluntions.
I now have removed all Synaptics drivers and am running the Generic Windows PS/2 driver. Interestingly, since this installtion, I have not had the blue screen.
Any thoughts would be appreciated.
Solved!
Go to Solution.

This error appears to be caused by the Synaptics SMB Touchpad Driver 17.0.10.1 and/or 17.0.8.
I rolled back the driver to version 16.4.20 and have not had a problem since.

Similar Messages

E2500 Wireless Causing Blue Screen of Death (BSOD) with My Company's VPN (AT&T Net Client)

Since recently replacing my home router with a Linksys E2500, I have been getting Blue Screen of Death (BSOD) with my Company's VPN (AT&T). It only happens when I am running wireless with my E2500. If I am hooked up to my E2500 through a ethernet cable it doesn't happen. I have updated the BIOS on my Lenovo Thinkpad T410 and ensured all of my drivers are up to date. I am 99.9% sure the problem is caused by my Linksys E2500 because I have used my laptop on other wireless routes at work and school and never get this problem. I am also ensured that my E2500 has the current firmware installed and upgraded my Company's VPN to the most current level to no avail.
I am getting DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen of Death in agnfilt.sys. Any assistance would be greatly appreciated. Thanks in advance.
Solved!
Go to Solution.

The symptoms you describe could be symptomatic of a variety of things to include hardware/software issues, overheating caused by a failed processor fan, bad memory (RAM), failing or underpowered power supply, CPU overheating, motherboard, video card, faulty or unsigned device drivers, CMOS battery going bad, BIOS and firmware problems, dirty hardware components, programs hanging or unresponsive in the background, and even malware. If the computer is overheating, it usually begins to shutdown/restart on a more regular basis.
If the machine is only crashing at home after establishing a connection but not at work when establishing a connection, then its probably an issue with your network configuration or something (i.e. wireless adapter) causing a conflict and not a malware issue.
The DRIVER_IRQL_NOT_LESS_OR_EQUAL error is usually due to a bad driver or faulty/incompatible hardware or software. This error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high.

Toshiba Satellite L755-S5306 Blue Screen of Death BSOD

If you are having “The Blue Screen Of Death” (BSOD) with a Toshiba Satellite L755-S5306 you are not alone. Please leave a comment in hopes enough of us can find each other and come up with a more permanent solution than the work around I present here. As of the day this was posted there was nothing index into Google or Toshiba’s forums regarding a Toshiba Satellite L755-S5306 having a BSOD problem.
Unfortunately I don't have an answer or solution so much as a troubleshooting alternative and that is to install Ubuntu 11+. I would rather use windows7 but the fact that Ubuntu runs without crashes indicates that my problem is a Windows 7 software issue. Windows7 is conflicting with either the hardware within my computer or some pre-installed factory software.
This laptop is new (it has only been out of the box for 3 months), has an i3 processor, 4GB of RAM and is still under warranty; until Sept. 10, 2012. I have yet to contact Toshiba but will. Within the last month (Feb. 2012) I started to get multiple BSODs out of no where. These were the following error messages:
1. KMODE_EXCEPTION_NOT_HANDLED
Caused By Driver : luafv.sys
2. KMODE_EXCEPTION_NOT_HANDLED
Caused By Driver : Ntfs.sys
3. SYSTEM_SERVICE_EXCEPTION
Caused By Driver : ntoskrnl.exe
4. PAGE_FAULT_IN_NONPAGED_AREA
Caused By Driver : ntoskrnl.exe
5. KMODE_EXCEPTION_NOT_HANDLED
Caused By Driver : partmgr.sys
You can see my full BSOD error reports here: CLICK HERE
I have done all of the following hoping to solve this issue with no luck:
1. Re-formated computer with factory shipped disk. Five Minutes after I did this I got the BSOD. That definitely eliminated the idea that it was something I had installed or that it was a windows update conflict.
2. Got all window updates. That didn’t help.
3. Checked all drivers manually one by one through the device manager for updates; according to the Device Manager there was no updates.
*However, this is the only area of hope that I have. I downloaded the program Drive Max and it list several drivers as outdated. I can only download two a day and install them. After I have them all installed I will report back as to whether or not I have a BSOD.
4. Updated BIOS. Toshiba did have a BIOS update available but the update did not fix my BSOD problems. I have seen on this forum many people have had problems with the BIOS but I have not.
5. Ran window's memory diagnostic tool. It reported no errors.
60 I also ran Ubuntus memory test and passed.
7. Check Disk with no errors
After all those failed attempts I took to the Internet. That is when I ran across a post online where a person stated they had the same problem with a similar Toshiba laptop and switched to Ubuntu. After doing so they had no problems. I did the same and agree I have no issues after one week. So I hope this helps for now. If anyone has this problem or finds a windows based solution please leave a comment.

Thank you all for your help.
Since I reformatted every time I have booted up I have turned on the Windows memory diagnostic too. I did this in hopes that if a BSOD occurred it would catch something when it rebooted and today it did after an extended memory test.
I got the standard message, “Hardware problems were detected...Test results will be displayed again after you log on”, however no test results were ever displayed. Does anyone know if there is a way to manually find the results of the test? Also, I ran the test again to see if I could get the results and the second time it said there were no problems detected.
At this point I am suspecting it to be a faulty stick of RAM. Windows 7 utilizes about 1.25GB of ram when booted and Ubuntu 200MB. This very well could be why Ubuntu works without problems.
I have to write a business plan in the next few weeks and cannot send my laptop in until that is done. So I will continue to use Ubuntu until done with my plan and then contact Toshiba. I will post back with any information I get in regards to the problem and once again thank you all for your help.

Blue Screen of Death on Toshiba Satellite

Hi, I have a Toshiba Satellite and for the last few months I have experienced two Blue Screens Of Death, at first, I didn't think much of it, but it kept getting more and more frequent. The STOP Codes are 0x1E and 0xA. Now, I cannot even boot my laptop normally, I have to boot it in Safe Mode with Networking. I tried using Repair your Computer, but I get a error code, I do not have any System Restore points, and Action Center doesn't have anything that can help. If you need some more info on my laptop, ask, please.
~Shade
Solved!
Go to Solution.

I tried a clean boot and it crashed with STOP code 0x1E, in safe mode
Are you saying it crashes while in Safe Mode? (In Safe Mode, you can not run Google Chrome.)
Open Device Manager (devmgmt.msc) and look around for warning messages.
If you can't operate in Safe Mode and there are no warnings in Device Manager, it's best to restore the hard disk to its original out-of-the-box contents using Toshiba recovery media. If that doesn't fix the problem, you know it's not due to software.
Those .dmp files have nothing new. Storport.sys is a Microsoft file (Storage Port Driver).
==================================================
Dump File         : 052413-90480-01.dmp
Crash Time        : 5/24/2013 3:11:40 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`03cc77ef
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`7efa0000
Caused By Driver : storport.sys
Caused By Address : storport.sys+1f03
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052413-90480-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052413-76487-01.dmp
Crash Time        : 5/24/2013 3:02:18 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`007400dc
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`03d14405
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052413-76487-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052413-31262-01.dmp
Crash Time        : 5/24/2013 3:18:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`03ccc813
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`000002e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052413-31262-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052313-42697-01.dmp
Crash Time        : 5/23/2013 9:26:00 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`030ad7ef
Parameter 3       : 00000000`00000000
Parameter 4      : 00000000`7efa0000
Caused By Driver : storport.sys
Caused By Address : storport.sys+1f03
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052313-42697-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052313-34086-01.dmp
Crash Time        : 5/23/2013 8:07:28 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`030607ef
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`7efa0000
Caused By Driver : storport.sys
Caused By Address : storport.sys+1f03
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052313-34086-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052313-30435-01.dmp
Crash Time        : 5/23/2013 10:03:28 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`000000dd
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`03d00405
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052313-30435-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052313-30404-01.dmp
Crash Time        : 5/23/2013 10:17:12 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`030b67ef
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`7efa0000
Caused By Driver : storport.sys
Caused By Address : storport.sys+1f03
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052313-30404-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
==================================================
Dump File         : 052313-26239-01.dmp
Crash Time        : 5/23/2013 8:59:20 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`030ad7ef
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`7efa0000
Caused By Driver : storport.sys
Caused By Address : storport.sys+1f03
File Description :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Test\052313-26239-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7601
==================================================
-Jerry

Blue screen of Death on Satellite M100

Hi
I have Satellite M100, we were having problems with the Blue screen of death occasionally, and then it seemed to get fairly consistent and the only way to ensure that the system didn't crash was to boot it in safe mode.
The sound had also stopped working. Decided to restore the system to factory settings so used the disc supplied and all went well till the system booted into windows allows you to go through the setup then blue screen again. The sound seems to have returned although it is a bit crackly.
So not sure whether this is the problem or not. Crashes Fatal system error and also driver_irql_not_less_or_equal.
Now can't boot into safe mode as windows setup hasn't finished....
Any ideas anyone?
Cheers
Simon

Hi
Yeah that;s what I am frightened of, tried several times no joy tried a normal xp pro disk as well as thought that might not have the right drivers and it might work but same there so guess it's a trip to the Toshiba hospital..... problem is guess everything is on the motherboard so by the time you have paid for a service call and motherboard you still have a 3 year old computer the figures don't add up and a new one would be the better option.....
Cheers
Simon

Blue Screen of Death on boot: ctaud2k.sys

Blue screen of Death on boot: ctaud2k.sys
MEMORY.DMP analysis:
(minidump will follow shortly)
Microsoft (R) Windows Debugger Version 6..000.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is:
SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.0026-30
Machine Name:
Kernel base = 0xfffff800`0000000 PsLoadedModuleList = 0xfffff800`0d440
Debug session time: Wed Dec 29 03:8:25.609 200 (GMT+)
System Uptime: 0 days 0:0:24.536
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
details
Loading unloaded module list
*????? Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffffadf8ebb5398, fffffadf8c644c0, 0}
Page ac7d4 not present in the dump file. Type ".hh dbgerr004" for details
Page acb29 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for
ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for
ctprxy2k.sys
PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
details
PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
details
Probably caused by : ctaud2k.sys ( ctaud2k+e398 )
Followup: MachineOwner
: kd> !analyze -v
*????? Bugcheck Analysis
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffffadf8ebb5398, Address of the exception record for the exception
that caused the bugcheck
Arg3: fffffadf8c644c0, Address of the context record for the exception that
caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
Page ac7d4 not present in the dump file. Type ".hh dbgerr004" for details
Page acb29 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
details
PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
details
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ctaud2k+e398
fffffadf`8ebb5398 488b02?? mov? rax,qword ptr [rdx]
CONTEXT:? fffffadf8c644c0 -- (.cxr 0xfffffadf8c644c0)
rax=000000000000000 rbx=fffffadf9a6390 rcx=000000000000000
rdx=0000008ffffffff rsi=fffffadf9a63260 rdi=0000000000000000
rip=fffffadf8ebb5398 rsp=fffffadf8c64cd0 rbp=fffffadf99c04330
?r8=fffffadf99c04330? r9=fffffadf9c6ff570 r0=fffffadf99c04330
r=fffffadf8c64d98 r2=0000000000000000 r3=fffffadf8c64d98
r4=000000000000000 r5=fffffadf9a632a8
iopl=0?? nv up ei pl nz na po nc
cs=000? ss=008? ds=002b? es=002b? fs=0053. gs=002b
efl=0000206
ctaud2k+0xe398:
fffffadf`8ebb5398 488b02?? mov? rax,qword ptr [rdx]
ds:002b:0000008`ffffffff=???
Resetting default scope
DEFAULT_BUCKET_ID:? DRIVER_FAULT
BUGCHECK_STR:? 0x3B
PROCESS_NAME:? DLLML.exe
CURRENT_IRQL:? 0
LAST_CONTROL_TRANSFER:? from fffffadf90b88785 to fffffadf8ebb5398
STACK_TEXT:
fffffadf`8c64cd0 fffffadf`90b88785 : 00000000`20206f49 fffff800`005039a
fffffadf`99c04330 fffffadf`9a6390 : ctaud2k+0xe398
fffffadf`8c64d50 fffff800`027f3 : 00000000`0000000 fffffadf`00000000
fffffadf`8c6500 00000000`00000000 : ctprxy2k+0x5785
fffffadf`8c64d90 fffff800`027ec36 : 00000000`0000034 00000000`00000000
00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa79
fffffadf`8c64eb0 fffff800`002e33d : fffffadf`99ee2c20 fffffadf`9c8bbb70
fffffadf`8c64f00 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffffadf`8c64f20 00000000`78b83e48 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`006dd98 fffff800`0026640 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : 0x78b83e48
fffffadf`8c65320 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiCallUserMode
FOLLOWUP_IP:
ctaud2k+e398
fffffadf`8ebb5398 488b02?? mov? rax,qword ptr [rdx]
SYMBOL_STACK_INDEX:? 0
SYMBOL_NAME:? ctaud2k+e398
FOLLOWUP_NAME:? MachineOwner
MODULE_NAME: ctaud2k
IMAGE_NAME:? ctaud2k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:? 4a26ba
STACK_COMMAND:? .cxr 0xfffffadf8c644c0 ; kb
FAILURE_BUCKET_ID:? X64_0x3B_ctaud2k+e398
BUCKET_ID:? X64_0x3B_ctaud2k+e398
Followup: MachineOwner
Bye,
? Skybuck.

Minidump:
<a rel="nofollow" target="_blank" href="http://members.home.nl/hbthouppermans/MiniDump/Mini2290-0.dmp"]http://members.home.nl/hbthouppermans/MiniDump/Mini2290-0.dmp[/url]
Microsoft (R) Windows Debugger Version 6..000.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini2290-0.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*c:\Tools\WinDbg\WebSymbols*<a rel="nofollow" target="_blank" href="http://msdl.microsoft.com/download/symbols"]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.0026-30
Machine Name:
Kernel base = 0xfffff800`0000000 PsLoadedModuleList = 0xfffff800`0d440
Debug session time: Wed Dec 29 03:8:25.609 200 (GMT+)
System Uptime: 0 days 0:0:24.536
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*????? Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffffadf8ebb5398, fffffadf8c644c0, 0}
Unable to load image \SystemRoot\system32\drivers\ctaud2k.sys, Win32 error
0n2
*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for
ctaud2k.sys
Probably caused by : ctaud2k.sys ( ctaud2k+e398 )
Followup: MachineOwner
: kd> !analyze -v
*????? Bugcheck Analysis
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffffadf8ebb5398, Address of the exception record for the exception
that caused the bugcheck
Arg3: fffffadf8c644c0, Address of the context record for the exception that
caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ctaud2k+e398
fffffadf`8ebb5398 ??
CONTEXT:? fffffadf8c644c0 -- (.cxr 0xfffffadf8c644c0)
rax=000000000000000 rbx=fffffadf9a6390 rcx=000000000000000
rdx=0000008ffffffff rsi=fffffadf9a63260 rdi=0000000000000000
rip=fffffadf8ebb5398 rsp=fffffadf8c64cd0 rbp=fffffadf99c04330
?r8=fffffadf99c04330? r9=fffffadf9c6ff570 r0=fffffadf99c04330
r=fffffadf8c64d98 r2=0000000000000000 r3=fffffadf8c64d98
r4=000000000000000 r5=fffffadf9a632a8
iopl=0?? nv up ei pl nz na po nc
cs=000? ss=008? ds=002b? es=002b? fs=0053. gs=002b
efl=0000206
ctaud2k+0xe398:
fffffadf`8ebb5398 ??
Resetting default scope
CUSTOMER_CRASH_COUNT:?
DEFAULT_BUCKET_ID:? DRIVER_FAULT
BUGCHECK_STR:? 0x3B
PROCESS_NAME:? DLLML.exe
CURRENT_IRQL:? 0
LAST_CONTROL_TRANSFER:? from 0000000000000000 to fffffadf8ebb5398
STACK_TEXT:
fffffadf`8c64cd0 00000000`00000000 : fffff800`00000000 00000000`00000000
00000000`00000000 00000000`20206f49 : ctaud2k+0xe398
FOLLOWUP_IP:
ctaud2k+e398
fffffadf`8ebb5398 ??
SYMBOL_STACK_INDEX:? 0
SYMBOL_NAME:? ctaud2k+e398
FOLLOWUP_NAME:? MachineOwner
MODULE_NAME: ctaud2k
IMAGE_NAME:? ctaud2k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:? 4a26ba
STACK_COMMAND:? .cxr 0xfffffadf8c644c0 ; kb
FAILURE_BUCKET_ID:? X64_0x3B_ctaud2k+e398
BUCKET_ID:? X64_0x3B_ctaud2k+e398
Followup: MachineOwner
Bye,
? Skybuck.

Blue Screen of Death after GPIB Software Drivers 2.1 install, nipsbfw.sys, nipalk.sys

I get a blue screen of death after I upgraded the GPIS Software Drivers to 2.1. The screen complains about the following files: nipsbfw.sys and nipalk.sys.
I'll copy down the exact message and post it...

Hello fkwok �
First, make sure GPIB software driver 2.1 is the correct driver for your operating system and board by clicking here.
If you are using Windows 2000, this KnowledgeBase is extremely useful.
If these suggestions do not solve your problem, please post the exact message and I will look into the issue some more. Have a great day!
Becky B.
Applications Engineer
National Instruments
Becky Linton
National Instruments
Field Engineer
Office: 734-464-2463
Cell: 248-709-2822
Email: [email protected]

Blue screen of death on Toshiba Satellite A215-S742 System Unit

i got the blue screen of death on my laptop. whenever i turn on my laptop, it loads up until the login page. then the blue screen of death appears and my laptop restarts and repeats. i have to do a hard shutdown. i can go into safe mode but i can do a system recovery (there are no recovery dates). even when i go into recovery mode, the blue screen of death appears after about 30min to an hour. i've tried updating the bios but it didn't work. i also tried using bootable cds with rescue programs but the cds dont boot (maybe im booting them the wrong way). what other ways are there to try to fix my laptop. please help!!!!!

Satellite A215-S7422
We need to know the Stop code on the blue screen. If there is a file name mentioned, we want that too.
You can prevent the rapid disappearance of the blue screen during a normal boot by choosing this at the F8 Startup menu.
Disable automatic restart on system failure
-Jerry

Blue Screen of Death and no XP CDs - Satellite M70

Hi.
I've got a Toshiba Satellite M70 that displays the Blue Screen of Death directly upon startup. It reads an error of 0x000000ED stating an unmountable error as the specific problem.
Unfortunately, I've no Windows XP CD to restore my computer. I do have the Toshiba Product Recovery CD, but that seems like it will simply format my computer, and I have important data I absolutely do not want to delete from my hard drive.
I cannot start in safe mode; Blue Screen of Death appears straightaway upon startup. If I try to get int through F8, Advanced Options appear but after selecting system restore it goes back to BSOD. I've also tried burning an ISO file for recovery, and the computer went into Windows Setup but hangs on "Setup is starting Windows".
Any idea what the trouble could be? And how can I fix this problem without deleting any info on my computer?
Thx.

The best option would be to remove the HDD and connect it to another PC using a USB 2.5" HDD Adapter. The HDD will appear as another Drive letter (E: for example) and you will be able to copy your data. Then you put the HDD back in and run Recovery.
If its simply a File System corruption problem, you could try running CHKDSK /F to fix it. You will need a retail version of the XP CD to do a CHKDSK from the Repair Console. Or you can create a Live Bootable XP CD which loads XP directly off a CD (Google BartPE) and run CHKDSK.
Otherwise the HDD may have bad sectors. You can use the Advanced test in Hitachi DFT to check the surface. But you should back up your data first, the HDD could get worse if you stress it out.

Satellite L450D-13X - Black Screen of Death/Blue Screen of Death

Hello everyone.
I have a Toshiba Satellite L450D-13X computer for the kids, and for the price it's a good laptop. Have had no issues with it until two weeks ago when the screen froze for the boys whilst playing a game and downloading a program from the net. Had to do a force shutdown and since then we have a BSoD on every boot-up. This is what we have tried:
On 'Starting Windows' we are given an option of either 'Launch Startup Repair' which ends up as BSoD or 'Start Windows Normally' which reverts back to the 'Starting Windows' option list.
Any attempt to enter 'Safe Mode' results in BSoD.
Attempting to boot an ISO of the Windows Recovery Disk on a USB key (we did highlight it and promote it to the top) results in BSoD. Borrowing a proper Window 7 installation DVD and highlighting this as an option results in BSoD.
In fact, the only option we used that threw up something different was using advanced boot options. On one of these options we got the Blue Screen of Death with the following information:
Unmountable_Boot_Volume
Disable Bios Memory Options such as caching/shadowing
Tech info
Stop: 0x000000ED (0xFFFFFA80023C2CDO 0xFFFFFFFFC0000185 0x0000000000000000 0x0000000000000000)
I don't mind erasing the hard drive and starting again, there's nothing on it that's critical. I'd very, very much appreciate a steer on this. Checked the web for stuff and nothing seems to assist in any other options. I am not particularly tech literate but can follow instructions.
Thanks in advance.

In my opinion system has a problem to start, so there are two most possible ways waht failed. Firstly as "Akuma" and "Keany" says HDD so check it. Second thing is RAM module. Check it using Memtest 86+ or if you have a possibility replace it for a while by other module. HDD is more possible, but RAM module is easier and faster to check (that's my opinion)

Blue screen of death due to usbaapl.sys

I know there has been a lot of writing about this, but I just can't get it to work. I'm running windows vista and have installed itunes 8.02 on my computer. Itunes detects my phone (which is stuck in restore mode) and tries to restore, but after a short while it crashes to the blue screen of death saying the problem is because of usbaapl.sys.
I've already updated all drivers on my pc (acer aspire 5530g) and tried to dissable dvd-drive, card-reader etc. NOTHING WORKS. I'v also uninstalled and reinstalled all my apple apps several times.
Please help me.
An unhappy Iphone 3g owner...

I know there has been a lot of writing about this, but I just can't get it to work. I'm running windows vista and have installed itunes 8.02 on my computer. Itunes detects my phone (which is stuck in restore mode) and tries to restore, but after a short while it crashes to the blue screen of death saying the problem is because of usbaapl.sys.
I've already updated all drivers on my pc (acer aspire 5530g) and tried to dissable dvd-drive, card-reader etc. NOTHING WORKS. I'v also uninstalled and reinstalled all my apple apps several times.
Please help me.
An unhappy Iphone 3g owner...

What is nipalk.sys and why does it give me the Blue Screen of Death?

Recently I purchased a 6211 USB data acquistion unit. Everything worked fine until one day Windows Explorer crashed (we all know how rare that kind of event is...). When I re-booted, I got the Blue Screen of Death, with a message about nipalk.sys being the culprit. I booted in Safe Mode and re-named this file, and then was able to boot normally and re-install the driver software for the 6211, and everything was fine...for about a week, when Windows Explorer did it again (Oops!).
Does anyone know:
    1. Which exact part of the install supplies nipalk.sys? It is a huge install with multiple parts accross 2 CDs. I could save a lot of time if I could restrict the install to just repairing the damage.
    2. Can I just make a copy of nipalk.sys and tuck it away in some corner of my hard drive to use as a replacement when this happens?
    3. I'm guessing that nipalk.sys is used by the little system tray icon that watches out for DAQ devices to be plugged into my USB. Is this guess correct? Can I turn this feature off for the 99% of the time I'm not using my laptop for data acquisition? Will that protect me against the gorking of nipalk.sys when Explorer goes down?
    4. What is this driver doing that its file disk becomes corrupted during a Windows Explorer crash?

Paul-
OK. When I can afford the time, I will try removing all NI software and re-installing. I have LabVIEW 8.0, DAQmx (of course), NI Vision development, and IMAQ.
I also had LabVIEW 7.1 on my machine because it was too much trouble to
remove it when I upgraded to 8.0 I have since removed 7.1, but I think there are still a lot of older versions of the "extras" that came along with it still lurking on my hard drive....
I was hoping for some guidance for a short-term "work around:"
1. If I just re-install DAQmx, can I make a copy of nipalk.sys and store it somewhere as a back-up to avoid the painfully long 2 CD re-install of DAQmx?
2. If the answer to 1 is "no", then exactly what part of DAQmx installs nipalk.sys? It is a multi-part install, and if I know which part is responsible for nipalk.sys, I can repair just that and save a lot of time.
To answer your questions about version: I'm not sure. I don't have convenient access to the disks at the moment, but they came with my 6211, which I ordered in May of 2007. I would be tempted to call it "the latest", but DAQmx seems to get updated quite frequently, so let's just call it a "recent" version.
Thanks,
-Geoff

Blue screen of death after ram upgrade on a Toshiba Satellite C655 laptop

I ordered an upgrade for a Toshiba Satellite C655(PSC08U-02D037) running Windows 7 Home Premium 64bit. I've trying for a month to get this to work consistently. When I first installed it, it worked fine for the first few days, but then after that I kept getting an error that would pop up "Display has Stopped Responding And Recovered" and the screen would flicker turn to black for a second. It didn't happen a lot at first, but then it got progressively worse to the point that it would crash my browsers, and sometimes when I tried to play certain videos, I would get the blue screen of death, and then the computer would have to restart.
I updated my bios, graphics drivers, I checked to see if maybe I failed to install it properly and reinstalled it, no avail. Finally I just took the ram out, and then I stopped having these issues. Which leads me to believe that it may have something to do with the memory upgrade. I ran the scanner as suggested when I was looking to upgrade, and what was recommended was a ( System 2gb DDR3-1600 Sodimm 1.35v CL11 ) ram stick part number CT6316802, which is the one I ended up ordering. I'm not sure what else to do but assume that what I ordered is either defective or just doesn't work with my laptop.

Hi jinjoe,
I am sorry for the issues you are experiencing with your upgrade. How is this memory installed? Is it just one module or did you purchase two? Did you install it with any exisitng RAM? If you have two modules have you tried installing one module at a time? This would help us determine if the issue is with one defective memory module or both causing the issue.

Satellite A65-S126 - Blue screen of death UNMOUNTABLE-BOOT-VOLUME

Hello,
I am having problems booting into windows. It is stuck in an endless install/boot cycle. Pressing F8 helped me freezeing the blue screen of death, which it says: "A problem has been detected and windows has been shotdown to prevent damage to your computer. UNMOUNTABLE-BOOT-VOLUME." The at the end
Technical information:
Stop: 0x000000ED(0x89B789E0, 0xC000009C, 0x00000000, 0x00000000)
I bought my laptop with the OS XP Home editon already installed.
Thank you and I hope you could help me solving this issue.
Saul
Message was edited by: saviar01

The file system may be corrupted. To fix it, you need to run CHKDSK on C: Drive.
If you cant boot into Safe Mode to run CHKDSK, or if the Recovery Console wont load, you may need to connect the HDD to another PC using a USB Adapter, so you can run CHKDSK on it.
Also test the Hard Disk for errors by using DFT.
DFT Download: http://www.hitachigst.com/hdd/support/download.htm#DFT
Download the ISO File and burn it to a CD-R Disc (There is also a Floppy Disk version if that's easier).
If you dont know how to burn an ISO file, read this guide: http://www.petri.co.il/how_to_write_iso_files_to_cd.htm
Restart your laptop and boot from the DFT Disc.
Choose the "Advanced" Test and let it run (it may take an hour or so).
If you see a red message box, the HDD is faulty.
An error od 0x70 means there are bad sectors and the HDD needs replacing.

Satellite A105-S4284 gets Blue Screen of Death when coming out of standby

MySatellite A105-S4284 runnings Windows XP gets a BSOD after coming out of standby or hibernation. With standby, I'll see the login screen where I enter my password, and then it may show the desktop background or even the open app (Outlook or Word, typically) for a second, afterwhich the BSOC appears. For weeks I was getting a black screen sporadically after standby. Researched the problem and saw recommendations to update BIOS. So I updated the BIOS to the latest version, and then I started getting blue screens of death rather than a black screen. Thought the problem was McAfee, because I'd get crashes right after McAfee became active in the background, sometimes without going into standby. Cancelled McAfee, took it off with the cleaner, used Avast instead, and that seemed to help. But then BSODs came back. I uninstalled non-essential software, clearned registry with CC Cleaner, freed up more HD space and defragged, ran SpyBot, etc - but I still get the BSOD almost every time I go into standby or hibernate.
The stop messages on the BSOD don't show a driver. and all begin with 0x0000007E (0x000000C5, ... and then differ after that. One recent one followed with 0x804E13D5, 0xAA6B9B8C, 0xAA6B9888). Does that mean anything?
I've installed Microsoft's debugging tools to look at the dumps after a BSOD. Here is output for two recent crashes. Doesn't point to a driver. NTKRMLMP.exe is what crashes - do I need to replace that from the I386 folder somehow? I did have my Matsu**bleep**a DVD-CD drive suddenly quit a time or two until the computer was restarted. Should I reinstall the DVD driver? Or the graphics driver? Worried that I might break something by doing that.
Loading Dump File [C:\WINDOWS\Minidump\Mini030809-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Mar 8 16:05:07.187 2009 (GMT-5)
System Uptime: 0 days 4:22:53.890
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
BugCheck 1000007E, {c0000005, 804e13d5, a9860b8c, a9860888}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+7a9 )
Followup: MachineOwner<snip>
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. <SNIP>
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804e13d5, The address that the exception occurred at
Arg3: a9860b8c, Exception Record Address
Arg4: a9860888, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!IopfCallDriver+2d
804e13d5 ff548638        call    dword ptr [esi+eax*4+38h]
EXCEPTION_RECORD: a9860b8c -- (.exr 0xffffffffa9860b8c)
ExceptionAddress: 804e13d5 (nt!IopfCallDriver+0x0000002d)
   ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000070
Attempt to read from address 00000070
CONTEXT: a9860888 -- (.cxr 0xffffffffa9860888)
eax=0000000e ebx=00000001 ecx=87546020 edx=853fe1a0 esi=00000000 edi=f772471c
eip=804e13d5 esp=a9860c54 ebp=a9860ca0 iopl=0         nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000             efl=00010292
nt!IopfCallDriver+0x2d:
804e13d5 ff548638        call    dword ptr [esi+eax*4+38h] ds:0023:00000070=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000070
READ_ADDRESS: 00000070
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+7a9
805517b9 e9e4feffff      jmp     nt!ExAllocatePoolWithTag+0x7bf (805516a2)
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 804e13d9 to 804e13d5
STACK_TEXT:
a9860c6c 804e13d9 8753d018 853fe1a0 00000000 nt!IopfCallDriver+0x2d
a9860ccc 805517b9 00000000 00000002 00000000 nt!IopfCallDriver+0x31
a9860dac 80575723 a9f4533c 00000000 00000000 nt!ExAllocatePoolWithTag+0x7a9
a9860ddc 804ec6d9 f7720ce2 a9f4533c 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!ExAllocatePoolWithTag+7a9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a4044a
STACK_COMMAND: .cxr 0xffffffffa9860888 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+7a9
BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+7a9
Followup: MachineOwner
0: kd> lmvm nt
start    end        module name
804d7000 806ff000   nt       # (pdb symbols)          c:\symbols\ntkrnlmp.pdb\B883868B88CB415A92EC010CF6A115A52\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\symbols\ntkrnlmp.exe\48A4044A228000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Aug 14 05:09:14 2008 (48A4044A)
    CheckSum:         0021B760
    ImageSize:        00228000
    File version:     5.1.2600.5657
    Product version: 5.1.2600.5657
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0401.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   5.1.2600.5657
    FileVersion:      5.1.2600.5657 (xpsp_sp3_gdr.080814-1236)

In safe mode it is not possible to standby. That is disabled. Tried to make it possible with Toshiba's power control service, but it is not available.
In a new account, the BSOD still occurs. I created a new account, logged out of my account, and went to the new one. Tried standby. It came out of standby for a second and then had the blue screen of death.
In checking the event manager, I seen errors shortly before crashes sometimes that involve the CD.
So I went to Toshiba.com and downloaded the DVD RAM driver and ran it, reinstalling the driver, and then restarted. I also saw that there was C-Dilla driver in my drivers. I uninstalled the SafeCast program that I think is associated with C-Dilla, moved the C-Dilla driver out of the drivers to a distant folder, unchecked C-Dilla in MSCONFIG so it won't load (it was still there after removing SafeCast), and then reinstarted. So with a new DVD Ram driver and neutering, I hope, of C-Dilla, I tried things again and the system appeared to be crash free - better than it had been. But then a crash occurred - BSOD - and upon restart, the CD locked up, and crashed again.
After restarting, there was a new dialog that popped up after Windows launched indicating that there had been an error with SONIC DLA. Before the crash, there was an event n the event viewer:
My last error comes from the Plug and Play Manager:
The device 'MAT**bleep**A DVD-RAM UJ-841S' (IDE\CdRomMAT**bleep**A_DVD-RAM_UJ-841S________________1.60____\5&226f6cf2&0&0.0.0) disappeared from the system without first being prepared for removal.
Hmmm. So things are still vulnerable. Any ideas? Buy new CD drive? Or new computer?

Blue Screen of Death - DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL (SynTP.sys) Satellite P55-A5200

Similar Messages

Maybe you are looking for