| Home | Forums | Reviews | Articles | Register |
![]() |
| Thread Tools | Rate Thread |
|
|
|
| |
|
Peter Foldes
Guest
Posts: n/a
|
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online MSDN article.) Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, 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. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.) a.. Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP b.. Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP a.. Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP b.. During upgrade to Win XP {KB 311564} Win XP c.. STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP d.. “Stop 0x0000000A” Error Message When You Fast Switch Between Users {KB 310918} Win XP e.. While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP f.. Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806} g.. “Fatal System Error” When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer) h.. Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP i.. STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM) j.. “Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available) k.. How to Use Driver Verifier to Troubleshoot Windows Drivers {KB 244617} Win 2000, Win XP, Server 2003 l.. Error Message When Installing Windows Vista on a Computer With More Than 3 GB of RAM: STOP 0x0000000A {KB 929777} Vista (update patch available) m.. Randomly Stop 0xA Errors in Storport.sys When You Start Windows Vista {KB 930261} Vista (hotfix available) -- Peter Please Reply to Newsgroup for the benefit of others Requests for assistance by email can not and will not be acknowledged. "Al Davis" <(E-Mail Removed)> wrote in message news:2C4E040C-FAB0-4FC9-8E23-(E-Mail Removed)... >I have a Samsung DVD burner, and whenever I try to burn disks with it I'm > sint to the Blue Screen of Death. I captured this memory dump... > > DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) > An attempt was made to access a pageable (or completely invalid) address at an > interrupt request level (IRQL) that is too high. This is usually > caused by drivers using improper addresses. > If kernel debugger is available get stack backtrace. > Arguments: > Arg1: 00000018, memory referenced > Arg2: 00000002, IRQL > Arg3: 00000000, value 0 = read operation, 1 = write operation > Arg4: ba712870, address which referenced memory > > Debugging Details: > ------------------ > > > READ_ADDRESS: 00000018 > > CURRENT_IRQL: 2 > > FAULTING_IP: > atapi!IdePortStartIo+aa > ba712870 8b4818 mov ecx,dword ptr [eax+18h] > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > BUGCHECK_STR: 0xD1 > > PROCESS_NAME: ImgBurn.exe > > LAST_CONTROL_TRANSFER: from 804ef023 to ba712870 > > STACK_TEXT: > b711fb50 804ef023 8a9e2030 89309470 8a9d7e50 atapi!IdePortStartIo+0xaa > b711fb70 ba711c9a 8a9e2030 89309470 00000000 > nt!ExAcquireResourceSharedLite+0x25 > b711fb9c 804ee003 8a9e2030 00309470 8a9d8cd8 atapi!IdePortDispatch+0x4e6 > b711fbb4 804ee003 8aa07aa8 89309470 8a324758 nt!CcAllocateInitializeBcb+0x64 > b711fc08 b81343b2 8a762f40 01a07aa8 895e5cd0 nt!CcAllocateInitializeBcb+0x64 > WARNING: Stack unwind information not available. Following frames may be > wrong. > b711fc34 804ee003 8a762e88 895e5cd0 806d02d0 Aspi32+0x13b2 > b711fc58 80574cdd 8a762e88 895e5cd0 897256d8 nt!CcAllocateInitializeBcb+0x64 > b711fd00 8056d639 000001ec 00000234 00000000 nt!BuildQueryDirectoryIrp+0x2c7 > b711fd34 8053ca48 000001ec 00000234 00000000 nt!NtQueryInformationToken+0xaa9 > b711fd64 7c90eb94 badb0d00 0299f70c 00000000 nt!ObGetSecurityMode+0xa > b711fd68 badb0d00 0299f70c 00000000 00000000 0x7c90eb94 > b711fd6c 0299f70c 00000000 00000000 00000000 swenum!_NULL_IMPORT_DESCRIPTOR > <PERF> (swenum+0xd00) > b711fd70 00000000 00000000 00000000 00000000 0x299f70c > > > STACK_COMMAND: kb > > FOLLOWUP_IP: > atapi!IdePortStartIo+aa > ba712870 8b4818 mov ecx,dword ptr [eax+18h] > > SYMBOL_STACK_INDEX: 0 > > SYMBOL_NAME: atapi!IdePortStartIo+aa > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: atapi > > IMAGE_NAME: atapi.sys > > DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4d > > FAILURE_BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa > > BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa > > Followup: MachineOwner > > The program described here is ImgBurn, but it happens with whatever Cd > burning software I try (Nero, Roxio, anything). > > I did a complete uninstall of that and any other such programs to start from > scratch, but this didn't help either. > > "an interrupt Request Level that is too high...". What does that mean; is > that something I can correct, perhaps in registry or some such? > > Thanks, > Albert Davis > > |
|
||
|
||||
|
Gerry
Guest
Posts: n/a
|
Al
Background information on Stop Error message http://msdn2.microsoft.com/en-us/library/ms795930.aspx 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile. Source: http://aumha.org/a/stop.htm Are there any yellow question marks in Device Manager? Right click on the My Computer icon on your Desktop and select Properties, Hardware,Device Manager. If yes what is the Device Error code? Try Start, Run, type "sigverif.exe" without quotes and hit OK. What drivers are listed as unsigned? Disregard those which are not checked. Are any devices malfunctioning? Select Start, All Programs, Accessories, System Tools, System Information. Open Components under System Summary and click on Problem Devices. Is anything listed there? What version of "The Ultimate Image Burner" do you have? What version of atapi.sys is located at C:\WINDOWS\system32\drivers -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ Al Davis wrote: > I have a Samsung DVD burner, and whenever I try to burn disks with it > I'm > sint to the Blue Screen of Death. I captured this memory dump... > > DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) > An attempt was made to access a pageable (or completely invalid) > address at an interrupt request level (IRQL) that is too high. This > is usually > caused by drivers using improper addresses. > If kernel debugger is available get stack backtrace. > Arguments: > Arg1: 00000018, memory referenced > Arg2: 00000002, IRQL > Arg3: 00000000, value 0 = read operation, 1 = write operation > Arg4: ba712870, address which referenced memory > > Debugging Details: > ------------------ > > > READ_ADDRESS: 00000018 > > CURRENT_IRQL: 2 > > FAULTING_IP: > atapi!IdePortStartIo+aa > ba712870 8b4818 mov ecx,dword ptr [eax+18h] > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > BUGCHECK_STR: 0xD1 > > PROCESS_NAME: ImgBurn.exe > > LAST_CONTROL_TRANSFER: from 804ef023 to ba712870 > > STACK_TEXT: > b711fb50 804ef023 8a9e2030 89309470 8a9d7e50 atapi!IdePortStartIo+0xaa > b711fb70 ba711c9a 8a9e2030 89309470 00000000 > nt!ExAcquireResourceSharedLite+0x25 > b711fb9c 804ee003 8a9e2030 00309470 8a9d8cd8 > atapi!IdePortDispatch+0x4e6 b711fbb4 804ee003 8aa07aa8 89309470 > 8a324758 nt!CcAllocateInitializeBcb+0x64 b711fc08 b81343b2 8a762f40 > 01a07aa8 895e5cd0 nt!CcAllocateInitializeBcb+0x64 WARNING: Stack > unwind information not available. Following frames may be wrong. > b711fc34 804ee003 8a762e88 895e5cd0 806d02d0 Aspi32+0x13b2 > b711fc58 80574cdd 8a762e88 895e5cd0 897256d8 > nt!CcAllocateInitializeBcb+0x64 b711fd00 8056d639 000001ec 00000234 > 00000000 nt!BuildQueryDirectoryIrp+0x2c7 b711fd34 8053ca48 000001ec > 00000234 00000000 nt!NtQueryInformationToken+0xaa9 b711fd64 7c90eb94 > badb0d00 0299f70c 00000000 nt!ObGetSecurityMode+0xa b711fd68 badb0d00 > 0299f70c 00000000 00000000 0x7c90eb94 > b711fd6c 0299f70c 00000000 00000000 00000000 > swenum!_NULL_IMPORT_DESCRIPTOR <PERF> (swenum+0xd00) > b711fd70 00000000 00000000 00000000 00000000 0x299f70c > > > STACK_COMMAND: kb > > FOLLOWUP_IP: > atapi!IdePortStartIo+aa > ba712870 8b4818 mov ecx,dword ptr [eax+18h] > > SYMBOL_STACK_INDEX: 0 > > SYMBOL_NAME: atapi!IdePortStartIo+aa > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: atapi > > IMAGE_NAME: atapi.sys > > DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4d > > FAILURE_BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa > > BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa > > Followup: MachineOwner > > The program described here is ImgBurn, but it happens with whatever Cd > burning software I try (Nero, Roxio, anything). > > I did a complete uninstall of that and any other such programs to > start from scratch, but this didn't help either. > > "an interrupt Request Level that is too high...". What does that > mean; is that something I can correct, perhaps in registry or some > such? > > Thanks, > Albert Davis |
|
||
|
||||
|
Al Davis
Guest
Posts: n/a
|
I found these on my system...
C:\WINDOWS\SYSTEM32\DRIVERS\atapi.sys C:\WINDOWS\SYSTEM32\dllcache\atapi.sys C:\WINDOWS\SYSTEM32\ReinstallBackups\0014\DriverFiles\i386\atapi.sys C:\WINDOWS\SYSTEM32\ReinstallBackups\0015\DriverFiles\i386\atapi.sy C:\WINDOWS\SoftwareDistribution\Download\dd9ab5193501484cf5e6884fa1d22f9e\atapi.sys C:\WINDOWS\$NtServicePackUninstall$\atapi.sys C:\WINDOWS\ServicePackFiles\i386\atapi.sys at least one of them is of a different version than the others - I don't know if my OS actually uses them all or not. For instance No. 3 is version 5.1.2600.5512, while others are version 5.1.2600.2180. Should they all be the same, and which is the correct or most current one? Maybe that's my problem... Thanks, albert "Gerry" wrote: > Al > > Background information on Stop Error message > http://msdn2.microsoft.com/en-us/library/ms795930.aspx > > 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL > The system attempted to access pageable memory using a kernel process > IRQL that was too high. The most typical cause is a bad device driver > (one that uses improper addresses). It can also be caused by caused by > faulty or mismatched RAM, or a damaged pagefile. > Source: http://aumha.org/a/stop.htm > > Are there any yellow question marks in Device Manager? Right click on > the My Computer icon on your Desktop and select Properties, > Hardware,Device Manager. If yes what is the Device Error code? > > Try Start, Run, type "sigverif.exe" without quotes and hit OK. What > drivers are listed as unsigned? Disregard those which are not checked. > > Are any devices malfunctioning? Select Start, All Programs, Accessories, > System Tools, System Information. Open Components under System Summary > and click on Problem Devices. Is anything listed there? > > What version of "The Ultimate Image Burner" do you have? > > What version of atapi.sys is located at C:\WINDOWS\system32\drivers > > -- > > > > Hope this helps. > > Gerry > ~~~~ > FCA > Stourport, England > Enquire, plan and execute > ~~~~~~~~~~~~~~~~~~~ > > Al Davis wrote: > > I have a Samsung DVD burner, and whenever I try to burn disks with it > > I'm > > sint to the Blue Screen of Death. I captured this memory dump... > > > > DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) > > An attempt was made to access a pageable (or completely invalid) > > address at an interrupt request level (IRQL) that is too high. This > > is usually > > caused by drivers using improper addresses. > > If kernel debugger is available get stack backtrace. > > Arguments: > > Arg1: 00000018, memory referenced > > Arg2: 00000002, IRQL > > Arg3: 00000000, value 0 = read operation, 1 = write operation > > Arg4: ba712870, address which referenced memory > > > > Debugging Details: > > ------------------ > > > > > > READ_ADDRESS: 00000018 > > > > CURRENT_IRQL: 2 > > > > FAULTING_IP: > > atapi!IdePortStartIo+aa > > ba712870 8b4818 mov ecx,dword ptr [eax+18h] > > > > CUSTOMER_CRASH_COUNT: 1 > > > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > > > BUGCHECK_STR: 0xD1 > > > > PROCESS_NAME: ImgBurn.exe > > > > LAST_CONTROL_TRANSFER: from 804ef023 to ba712870 > > > > STACK_TEXT: > > b711fb50 804ef023 8a9e2030 89309470 8a9d7e50 atapi!IdePortStartIo+0xaa > > b711fb70 ba711c9a 8a9e2030 89309470 00000000 > > nt!ExAcquireResourceSharedLite+0x25 > > b711fb9c 804ee003 8a9e2030 00309470 8a9d8cd8 > > atapi!IdePortDispatch+0x4e6 b711fbb4 804ee003 8aa07aa8 89309470 > > 8a324758 nt!CcAllocateInitializeBcb+0x64 b711fc08 b81343b2 8a762f40 > > 01a07aa8 895e5cd0 nt!CcAllocateInitializeBcb+0x64 WARNING: Stack > > unwind information not available. Following frames may be wrong. > > b711fc34 804ee003 8a762e88 895e5cd0 806d02d0 Aspi32+0x13b2 > > b711fc58 80574cdd 8a762e88 895e5cd0 897256d8 > > nt!CcAllocateInitializeBcb+0x64 b711fd00 8056d639 000001ec 00000234 > > 00000000 nt!BuildQueryDirectoryIrp+0x2c7 b711fd34 8053ca48 000001ec > > 00000234 00000000 nt!NtQueryInformationToken+0xaa9 b711fd64 7c90eb94 > > badb0d00 0299f70c 00000000 nt!ObGetSecurityMode+0xa b711fd68 badb0d00 > > 0299f70c 00000000 00000000 0x7c90eb94 > > b711fd6c 0299f70c 00000000 00000000 00000000 > > swenum!_NULL_IMPORT_DESCRIPTOR <PERF> (swenum+0xd00) > > b711fd70 00000000 00000000 00000000 00000000 0x299f70c > > > > > > STACK_COMMAND: kb > > > > FOLLOWUP_IP: > > atapi!IdePortStartIo+aa > > ba712870 8b4818 mov ecx,dword ptr [eax+18h] > > > > SYMBOL_STACK_INDEX: 0 > > > > SYMBOL_NAME: atapi!IdePortStartIo+aa > > > > FOLLOWUP_NAME: MachineOwner > > > > MODULE_NAME: atapi > > > > IMAGE_NAME: atapi.sys > > > > DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4d > > > > FAILURE_BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa > > > > BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa > > > > Followup: MachineOwner > > > > The program described here is ImgBurn, but it happens with whatever Cd > > burning software I try (Nero, Roxio, anything). > > > > I did a complete uninstall of that and any other such programs to > > start from scratch, but this didn't help either. > > > > "an interrupt Request Level that is too high...". What does that > > mean; is that something I can correct, perhaps in registry or some > > such? > > > > Thanks, > > Albert Davis > > > |
|
||
|
||||
|
Gerry
Guest
Posts: n/a
|
Al
They will be different as they are there are there for different reasons. What version of atapi.sys is located at C:\WINDOWS\system32\drivers? This the one that counts when investigating your present problem! The version at C:\WINDOWS\ServicePackFiles\i386 is a backup copy and should be the same version as C:\WINDOWS\system32\drivers The copy at C:\WINDOWS\$NtServicePackUninstall$ is the previous version and would used again if you uninstalled the last service pack . The copy at C:\WINDOWS\SYSTEM32\dllcache\ should be the same as the copy at C:\WINDOWS\system32\drivers. The copy at C:\WINDOWS\SYSTEM32\ReinstallBackups\0014\DriverFiles\i386\ would seem to be a backup copy created by BackUp software. I have no idea what created this entry C:\WINDOWS\SoftwareDistribution\Download\dd9ab5193501484cf5e6884fa1d22f9e\atapi.sys -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ Al Davis wrote: > I found these on my system... > > C:\WINDOWS\SYSTEM32\DRIVERS\atapi.sys > C:\WINDOWS\SYSTEM32\dllcache\atapi.sys > C:\WINDOWS\SYSTEM32\ReinstallBackups\0014\DriverFiles\i386\atapi.sys > C:\WINDOWS\SYSTEM32\ReinstallBackups\0015\DriverFiles\i386\atapi.sys > C:\WINDOWS\SoftwareDistribution\Download\dd9ab5193501484cf5e6884fa1d22f9e\atapi.sys > C:\WINDOWS\$NtServicePackUninstall$\atapi.sys > C:\WINDOWS\ServicePackFiles\i386\atapi.sys > > at least one of them is of a different version than the others - I > don't know if my OS actually uses them all or not. For instance No. > 3 is version > 5.1.2600.5512, while others are version 5.1.2600.2180. > Should they all be the same, and which is the correct or most current > one? Maybe that's my problem... > > Thanks, > albert > > > "Gerry" wrote: > >> Al >> >> Background information on Stop Error message >> http://msdn2.microsoft.com/en-us/library/ms795930.aspx >> >> 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL >> The system attempted to access pageable memory using a kernel process >> IRQL that was too high. The most typical cause is a bad device driver >> (one that uses improper addresses). It can also be caused by caused >> by faulty or mismatched RAM, or a damaged pagefile. >> Source: http://aumha.org/a/stop.htm >> >> Are there any yellow question marks in Device Manager? Right click on >> the My Computer icon on your Desktop and select Properties, >> Hardware,Device Manager. If yes what is the Device Error code? >> >> Try Start, Run, type "sigverif.exe" without quotes and hit OK. What >> drivers are listed as unsigned? Disregard those which are not >> checked. >> >> Are any devices malfunctioning? Select Start, All Programs, >> Accessories, System Tools, System Information. Open Components under >> System Summary and click on Problem Devices. Is anything listed >> there? >> >> What version of "The Ultimate Image Burner" do you have? >> >> What version of atapi.sys is located at C:\WINDOWS\system32\drivers >> >> -- >> >> >> >> Hope this helps. >> >> Gerry >> ~~~~ >> FCA >> Stourport, England >> Enquire, plan and execute >> ~~~~~~~~~~~~~~~~~~~ >> >> Al Davis wrote: >>> I have a Samsung DVD burner, and whenever I try to burn disks with >>> it I'm >>> sint to the Blue Screen of Death. I captured this memory dump... >>> >>> DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) >>> An attempt was made to access a pageable (or completely invalid) >>> address at an interrupt request level (IRQL) that is too high. This >>> is usually >>> caused by drivers using improper addresses. >>> If kernel debugger is available get stack backtrace. >>> Arguments: >>> Arg1: 00000018, memory referenced >>> Arg2: 00000002, IRQL >>> Arg3: 00000000, value 0 = read operation, 1 = write operation >>> Arg4: ba712870, address which referenced memory >>> >>> Debugging Details: >>> ------------------ >>> >>> >>> READ_ADDRESS: 00000018 >>> >>> CURRENT_IRQL: 2 >>> >>> FAULTING_IP: >>> atapi!IdePortStartIo+aa >>> ba712870 8b4818 mov ecx,dword ptr [eax+18h] >>> >>> CUSTOMER_CRASH_COUNT: 1 >>> >>> DEFAULT_BUCKET_ID: DRIVER_FAULT >>> >>> BUGCHECK_STR: 0xD1 >>> >>> PROCESS_NAME: ImgBurn.exe >>> >>> LAST_CONTROL_TRANSFER: from 804ef023 to ba712870 >>> >>> STACK_TEXT: >>> b711fb50 804ef023 8a9e2030 89309470 8a9d7e50 >>> atapi!IdePortStartIo+0xaa b711fb70 ba711c9a 8a9e2030 89309470 >>> 00000000 nt!ExAcquireResourceSharedLite+0x25 >>> b711fb9c 804ee003 8a9e2030 00309470 8a9d8cd8 >>> atapi!IdePortDispatch+0x4e6 b711fbb4 804ee003 8aa07aa8 89309470 >>> 8a324758 nt!CcAllocateInitializeBcb+0x64 b711fc08 b81343b2 8a762f40 >>> 01a07aa8 895e5cd0 nt!CcAllocateInitializeBcb+0x64 WARNING: Stack >>> unwind information not available. Following frames may be wrong. >>> b711fc34 804ee003 8a762e88 895e5cd0 806d02d0 Aspi32+0x13b2 >>> b711fc58 80574cdd 8a762e88 895e5cd0 897256d8 >>> nt!CcAllocateInitializeBcb+0x64 b711fd00 8056d639 000001ec 00000234 >>> 00000000 nt!BuildQueryDirectoryIrp+0x2c7 b711fd34 8053ca48 000001ec >>> 00000234 00000000 nt!NtQueryInformationToken+0xaa9 b711fd64 7c90eb94 >>> badb0d00 0299f70c 00000000 nt!ObGetSecurityMode+0xa b711fd68 >>> badb0d00 0299f70c 00000000 00000000 0x7c90eb94 >>> b711fd6c 0299f70c 00000000 00000000 00000000 >>> swenum!_NULL_IMPORT_DESCRIPTOR <PERF> (swenum+0xd00) >>> b711fd70 00000000 00000000 00000000 00000000 0x299f70c >>> >>> >>> STACK_COMMAND: kb >>> >>> FOLLOWUP_IP: >>> atapi!IdePortStartIo+aa >>> ba712870 8b4818 mov ecx,dword ptr [eax+18h] >>> >>> SYMBOL_STACK_INDEX: 0 >>> >>> SYMBOL_NAME: atapi!IdePortStartIo+aa >>> >>> FOLLOWUP_NAME: MachineOwner >>> >>> MODULE_NAME: atapi >>> >>> IMAGE_NAME: atapi.sys >>> >>> DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4d >>> >>> FAILURE_BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa >>> >>> BUCKET_ID: 0xD1_atapi!IdePortStartIo+aa >>> >>> Followup: MachineOwner >>> >>> The program described here is ImgBurn, but it happens with whatever >>> Cd burning software I try (Nero, Roxio, anything). >>> >>> I did a complete uninstall of that and any other such programs to >>> start from scratch, but this didn't help either. >>> >>> "an interrupt Request Level that is too high...". What does that >>> mean; is that something I can correct, perhaps in registry or some >>> such? >>> >>> Thanks, >>> Albert Davis |
|
||
|
||||
|
|
|
| |
![]() |
| Thread Tools | |
| Rate This Thread | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| atapi | =?Utf-8?B?U2hlaXN0eQ==?= | Windows XP Help | 3 | 19th Dec 2005 01:03 AM |
| atapi.sys | amajamar | Windows XP Hardware | 0 | 26th Jan 2004 01:12 PM |
| atapi.sys | Dr D A Jones | Windows XP Performance | 1 | 4th Dec 2003 12:25 AM |
| atapi.sys | Rafael Sanchez | Windows XP Basics | 0 | 25th Sep 2003 07:04 PM |
| Atapi.sys | Denny | Windows XP Hardware | 0 | 8th Sep 2003 01:43 AM |
Powered by vBulletin®. Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
SEO by vBSEO ©2010, Crawlability, Inc. |




