Re: Irda.sys bsod

As I understand it, irda.sys is a class driver. This means that Microsoft
writes most of the driver stack, and a 3rd party will often write a small
portion of the stack via a device driver that has hardware specific code.

You can see a graphic representation of this model for CIR:

http://msdn.microsoft.com/en-us/library/cc264525.aspx

What is likely happening is that the 3rd party code is passing bad data to
irda.sys. Do you have a crash dump file that I can take a look at?



"Tae Song" <> wrote in message
news:B7B48D8D-4C8C-46B7-8496-...
>
> "RedLars" <> wrote in message
> news:cb6ac3ab-b12a-4f70-92ac-...
>> Bought an USB 2.0 IrDA Dongle from STLab (http://www.st-lab.com/) and
>> installed their driver. Then tried to use it via Polar ProTrainer 5
>> and ... bsod.
>>
>> Using Vista Home Premium.
>>
>> I opend the memory.dmp file in windbg and here is some info;
>>
>> 1: kd> !analyze -v
>> ************************************************** *****************************
>> *
>> *
>> * Bugcheck
>> Analysis *
>> *
>> *
>> ************************************************** *****************************
>>
>> 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: ffffffec, memory referenced
>> Arg2: 00000002, IRQL
>> Arg3: 00000000, value 0 = read operation, 1 = write operation
>> Arg4: 0139b30f, address which referenced memory
>>
>> Debugging Details:
>> ------------------
>>
>> READ_ADDRESS: ffffffec
>>
>> CURRENT_IRQL: 2
>>
>> FAULTING_IP:
>> +139b30f
>> 0139b30f ?? ???
>>
>> PROCESS_NAME: System
>>
>> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>>
>> BUGCHECK_STR: 0xD1
>>
>> TRAP_FRAME: 8c3dfa78 -- (.trap 0xffffffff8c3dfa78)
>> ErrCode = 00000000
>> eax=5054047a ebx=00000000 ecx=8b08ab57 edx=00001351 esi=00000000
>> edi=869ce780
>> eip=0139b30f esp=8c3dfaec ebp=8c3dfaf8 iopl=0 nv up ei pl nz
>> ac po cy
>> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
>> efl=00010213
>> 0139b30f ?? ???
>> Resetting default scope
>>
>> LAST_CONTROL_TRANSFER: from 0139b30f to 82049374
>>
>> STACK_TEXT:
>> 8c3dfa78 0139b30f badb0d00 00001351 00000f43 nt!KiTrap0E+0x2ac
>> WARNING: Frame IP not in any known module. Following frames may be
>> wrong.
>> 8c3dfae8 8c3dfb30 852f4200 00000006 8c3dfb14 0x139b30f
>> 8c3dfaf8 8239b500 8b089002 8c3dfb30 8c3dfb30 0x8c3dfb30
>> 8c3dfb14 8239b6c9 865fb880 8c3dfb30 82036f25 hal!
>> HalpCheckForSoftwareInterrupt+0x64
>> 8c3dfb20 82036f25 82398d00 00000072 8c3dfc08 hal!HalEndSystemInterrupt
>> +0x73
>> 8c3dfb20 9c58b9a3 82398d00 00000072 8c3dfc08 nt!KiChainedDispatch+0x65
>> 8c3dfc08 9c597e1a 85bfc9f8 84eb58f8 8c3dfcb0 irda!SlotTimerExp+0x1c
>> 8c3dfc7c 9c58d043 85bfc9f8 8c3dfcb0 84eb58f8 irda!
>> ProcessMACControlConf
>> +0xbb
>> 8c3dfc90 9c597315 85bfc9f8 8c3dfcb0 9c594000 irda!IrlapUp+0x45
>> 8c3dfd10 9c583f48 84eb58f8 84eb59bc 84eb59b8 irda!MediaSenseExp+0x69
>> 8c3dfd28 8dc3a060 84eb59b8 84eb5960 820f563c irda!IrdaTimerExpFunc
>> +0x5b
>> 8c3dfd44 8206a08a 84eb5960 00000000 8441a020 TDI!CTEpEventHandler+0x32
>> 8c3dfd7c 821afbf9 84eb59b8 8c3d4680 00000000 nt!ExpWorkerThread+0xfd
>> 8c3dfdc0 8209a3a6 82069f8d 00000001 00000000 nt!PspSystemThreadStartup
>> +0x9d
>> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>>
>> STACK_COMMAND: kb
>>
>> FOLLOWUP_IP:
>> nt!KiTrap0E+2ac
>> 82049374 833d00f8118200 cmp dword ptr [nt!KiFreezeFlag
>> (8211f800)],0
>>
>> SYMBOL_STACK_INDEX: 0
>>
>> SYMBOL_NAME: nt!KiTrap0E+2ac
>>
>> FOLLOWUP_NAME: MachineOwner
>>
>> MODULE_NAME: nt
>>
>> IMAGE_NAME: ntkrnlmp.exe
>>
>> DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8c09
>>
>> FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>>
>> BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>>
>> Followup: MachineOwner
>>
>> 1: kd> lmv mirda
>> start end module name
>> 9c582000 9c5a0000 irda (pdb symbols) c:\symbols
>> \irda.pdb\D94057B826FA4A9CA3F1FDCC8A0AE6C22\irda.p db
>> Loaded symbol image file: irda.sys
>> Image path: \SystemRoot\system32\DRIVERS\irda.sys
>> Image name: irda.sys
>> Timestamp: Thu Nov 02 09:57:09 2006 (4549B2E5)
>> CheckSum: 0001EA89
>> ImageSize: 0001E000
>> Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
>>
>> irda.sys is a microsoft IRDA protocol driver.
>>
>> Any clues ?
>
>
> Which one do you have? I see they have have 3 different IRDA models...
>
> USB IRDA (probably not it) phased out
> USB 2.0 IRDA-4210 (4 Mbit) phased out
> USB 2.0 IRDA-4220 (16 Mbit)
>
> Did you look for a newer driver on their website?

"RedLars" <> wrote in message
news:49475fdd-78e7-4ec3-8963-...
> On 5 Jun, 10:53, "Tae Song" <tae_s...@hotmail.com> wrote:
>> "RedLars" <Liverpool1...@gmail.com> wrote in message
>>
>> news:cb6ac3ab-b12a-4f70-92ac-...
>>
>>
>>
>>
>>
>> > Bought an USB 2.0 IrDA Dongle from STLab (http://www.st-lab.com/) and
>> > installed their driver. Then tried to use it via Polar ProTrainer 5
>> > and ... bsod.
>>
>> > Using Vista Home Premium.
>>
>> > I opend the memory.dmp file in windbg and here is some info;
>>
>> > 1: kd> !analyze -v
>> > ************************************************** ******************************
>> > *
>> > *
>> > * Bugcheck
>> > Analysis *
>> > *
>> > *
>> > ************************************************** ******************************
>>
>> > 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: ffffffec, memory referenced
>> > Arg2: 00000002, IRQL
>> > Arg3: 00000000, value 0 = read operation, 1 = write operation
>> > Arg4: 0139b30f, address which referenced memory
>>
>> > Debugging Details:
>> > ------------------
>>
>> > READ_ADDRESS: ffffffec
>>
>> > CURRENT_IRQL: 2
>>
>> > FAULTING_IP:
>> > +139b30f
>> > 0139b30f ?? ???
>>
>> > PROCESS_NAME: System
>>
>> > DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>>
>> > BUGCHECK_STR: 0xD1
>>
>> > TRAP_FRAME: 8c3dfa78 -- (.trap 0xffffffff8c3dfa78)
>> > ErrCode = 00000000
>> > eax=5054047a ebx=00000000 ecx=8b08ab57 edx=00001351 esi=00000000
>> > edi=869ce780
>> > eip=0139b30f esp=8c3dfaec ebp=8c3dfaf8 iopl=0 nv up ei pl nz
>> > ac po cy
>> > cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
>> > efl=00010213
>> > 0139b30f ?? ???
>> > Resetting default scope
>>
>> > LAST_CONTROL_TRANSFER: from 0139b30f to 82049374
>>
>> > STACK_TEXT:
>> > 8c3dfa78 0139b30f badb0d00 00001351 00000f43 nt!KiTrap0E+0x2ac
>> > WARNING: Frame IP not in any known module. Following frames may be
>> > wrong.
>> > 8c3dfae8 8c3dfb30 852f4200 00000006 8c3dfb14 0x139b30f
>> > 8c3dfaf8 8239b500 8b089002 8c3dfb30 8c3dfb30 0x8c3dfb30
>> > 8c3dfb14 8239b6c9 865fb880 8c3dfb30 82036f25 hal!
>> > HalpCheckForSoftwareInterrupt+0x64
>> > 8c3dfb20 82036f25 82398d00 00000072 8c3dfc08 hal!HalEndSystemInterrupt
>> > +0x73
>> > 8c3dfb20 9c58b9a3 82398d00 00000072 8c3dfc08 nt!KiChainedDispatch+0x65
>> > 8c3dfc08 9c597e1a 85bfc9f8 84eb58f8 8c3dfcb0 irda!SlotTimerExp+0x1c
>> > 8c3dfc7c 9c58d043 85bfc9f8 8c3dfcb0 84eb58f8 irda!
>> > ProcessMACControlConf
>> > +0xbb
>> > 8c3dfc90 9c597315 85bfc9f8 8c3dfcb0 9c594000 irda!IrlapUp+0x45
>> > 8c3dfd10 9c583f48 84eb58f8 84eb59bc 84eb59b8 irda!MediaSenseExp+0x69
>> > 8c3dfd28 8dc3a060 84eb59b8 84eb5960 820f563c irda!IrdaTimerExpFunc
>> > +0x5b
>> > 8c3dfd44 8206a08a 84eb5960 00000000 8441a020 TDI!CTEpEventHandler+0x32
>> > 8c3dfd7c 821afbf9 84eb59b8 8c3d4680 00000000 nt!ExpWorkerThread+0xfd
>> > 8c3dfdc0 8209a3a6 82069f8d 00000001 00000000 nt!PspSystemThreadStartup
>> > +0x9d
>> > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>>
>> > STACK_COMMAND: kb
>>
>> > FOLLOWUP_IP:
>> > nt!KiTrap0E+2ac
>> > 82049374 833d00f8118200 cmp dword ptr [nt!KiFreezeFlag
>> > (8211f800)],0
>>
>> > SYMBOL_STACK_INDEX: 0
>>
>> > SYMBOL_NAME: nt!KiTrap0E+2ac
>>
>> > FOLLOWUP_NAME: MachineOwner
>>
>> > MODULE_NAME: nt
>>
>> > IMAGE_NAME: ntkrnlmp.exe
>>
>> > DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8c09
>>
>> > FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>>
>> > BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>>
>> > Followup: MachineOwner
>>
>> > 1: kd> lmv mirda
>> > start end module name
>> > 9c582000 9c5a0000 irda (pdb symbols) c:\symbols
>> > \irda.pdb\D94057B826FA4A9CA3F1FDCC8A0AE6C22\irda.p db
>> > Loaded symbol image file: irda.sys
>> > Image path: \SystemRoot\system32\DRIVERS\irda.sys
>> > Image name: irda.sys
>> > Timestamp: Thu Nov 02 09:57:09 2006 (4549B2E5)
>> > CheckSum: 0001EA89
>> > ImageSize: 0001E000
>> > Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
>>
>> > irda.sys is a microsoft IRDA protocol driver.
>>
>> > Any clues ?
>>
>> Which one do you have? I see they have have 3 different IRDA models...
>>
>> USB IRDA (probably not it) phased out
>> USB 2.0 IRDA-4210 (4 Mbit) phased out
>> USB 2.0 IRDA-4220 (16 Mbit)
>>
>> Did you look for a newer driver on their website?– Skjul sitert tekst –
>>
>> – Vis sitert tekst –
>
>
> Using USB 2.0 IRDA-4210.
>
> Downloaded driver from their website 4 days ago.

Did you read my last message? Use the drivers that came with Vista. The
ones from the website only support Windows up to XP. The downloaded drivers
aren't for Vista.

"RedLars" <> wrote in message
news:50e776f7-7791-4a5b-99bd-...
>
> Im a bit confussed. The web site does state "OS Supports: Windows 98SE/
> ME/2000/XP/Vista" for USB 2.0 IRDA-4210 (4Mbps). If Vista only
> requires the built in driver, what does the setup file at their
> website then include? Is this for early OSes? Another thing, looking
> at the call stack from my first post, it only refers to irda.sys which
> is a microsoft driver, there are no references to any stlab driver as
> far I see.
>
> Will of course try to uninstall the stlab software and reinstall the
> usb dongle with microsoft driver once I get back home as you
> suggested.
>

I downloaded the drivers and it doesn't mention Vista, I checked. It only
supports up to XP. Apparently, Vista has new code in place to directly
handle USB 2.0 to IRDA and doesn't require 3rd party drivers.

"RedLars" <> wrote in message
news:cb6ac3ab-b12a-4f70-92ac-...
> Bought an USB 2.0 IrDA Dongle from STLab (http://www.st-lab.com/) and
> installed their driver. Then tried to use it via Polar ProTrainer 5
> and ... bsod.
>
> Using Vista Home Premium.
>
> I opend the memory.dmp file in windbg and here is some info;
>
> 1: kd> !analyze -v
> ************************************************** *****************************
> *
> *
> * Bugcheck
> Analysis *
> *
> *
> ************************************************** *****************************
>
> 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: ffffffec, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 0139b30f, address which referenced memory
>
> Debugging Details:
> ------------------
>
> READ_ADDRESS: ffffffec
>
> CURRENT_IRQL: 2
>
> FAULTING_IP:
> +139b30f
> 0139b30f ?? ???
>
> PROCESS_NAME: System
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> BUGCHECK_STR: 0xD1
>
> TRAP_FRAME: 8c3dfa78 -- (.trap 0xffffffff8c3dfa78)
> ErrCode = 00000000
> eax=5054047a ebx=00000000 ecx=8b08ab57 edx=00001351 esi=00000000
> edi=869ce780
> eip=0139b30f esp=8c3dfaec ebp=8c3dfaf8 iopl=0 nv up ei pl nz
> ac po cy
> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> efl=00010213
> 0139b30f ?? ???
> Resetting default scope
>
> LAST_CONTROL_TRANSFER: from 0139b30f to 82049374
>
> STACK_TEXT:
> 8c3dfa78 0139b30f badb0d00 00001351 00000f43 nt!KiTrap0E+0x2ac
> WARNING: Frame IP not in any known module. Following frames may be
> wrong.
> 8c3dfae8 8c3dfb30 852f4200 00000006 8c3dfb14 0x139b30f
> 8c3dfaf8 8239b500 8b089002 8c3dfb30 8c3dfb30 0x8c3dfb30
> 8c3dfb14 8239b6c9 865fb880 8c3dfb30 82036f25 hal!
> HalpCheckForSoftwareInterrupt+0x64
> 8c3dfb20 82036f25 82398d00 00000072 8c3dfc08 hal!HalEndSystemInterrupt
> +0x73
> 8c3dfb20 9c58b9a3 82398d00 00000072 8c3dfc08 nt!KiChainedDispatch+0x65
> 8c3dfc08 9c597e1a 85bfc9f8 84eb58f8 8c3dfcb0 irda!SlotTimerExp+0x1c
> 8c3dfc7c 9c58d043 85bfc9f8 8c3dfcb0 84eb58f8 irda!
> ProcessMACControlConf
> +0xbb
> 8c3dfc90 9c597315 85bfc9f8 8c3dfcb0 9c594000 irda!IrlapUp+0x45
> 8c3dfd10 9c583f48 84eb58f8 84eb59bc 84eb59b8 irda!MediaSenseExp+0x69
> 8c3dfd28 8dc3a060 84eb59b8 84eb5960 820f563c irda!IrdaTimerExpFunc
> +0x5b
> 8c3dfd44 8206a08a 84eb5960 00000000 8441a020 TDI!CTEpEventHandler+0x32
> 8c3dfd7c 821afbf9 84eb59b8 8c3d4680 00000000 nt!ExpWorkerThread+0xfd
> 8c3dfdc0 8209a3a6 82069f8d 00000001 00000000 nt!PspSystemThreadStartup
> +0x9d
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> nt!KiTrap0E+2ac
> 82049374 833d00f8118200 cmp dword ptr [nt!KiFreezeFlag
> (8211f800)],0
>
> SYMBOL_STACK_INDEX: 0
>
> SYMBOL_NAME: nt!KiTrap0E+2ac
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: nt
>
> IMAGE_NAME: ntkrnlmp.exe
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8c09
>
> FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>
> BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>
> Followup: MachineOwner
>
> 1: kd> lmv mirda
> start end module name
> 9c582000 9c5a0000 irda (pdb symbols) c:\symbols
> \irda.pdb\D94057B826FA4A9CA3F1FDCC8A0AE6C22\irda.p db
> Loaded symbol image file: irda.sys
> Image path: \SystemRoot\system32\DRIVERS\irda.sys
> Image name: irda.sys
> Timestamp: Thu Nov 02 09:57:09 2006 (4549B2E5)
> CheckSum: 0001EA89
> ImageSize: 0001E000
> Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
>
> irda.sys is a microsoft IRDA protocol driver.
>
> Any clues ?


Which one do you have? I see they have have 3 different IRDA models...

USB IRDA (probably not it) phased out
USB 2.0 IRDA-4210 (4 Mbit) phased out
USB 2.0 IRDA-4220 (16 Mbit)

Did you look for a newer driver on their website?

"Timothy Davis [MSFT]" <> wrote in message
news:F3D7D4BE-3F20-4985-9490-...
> As I understand it, irda.sys is a class driver. This means that Microsoft
> writes most of the driver stack, and a 3rd party will often write a small
> portion of the stack via a device driver that has hardware specific code.
>
> You can see a graphic representation of this model for CIR:
>
> http://msdn.microsoft.com/en-us/library/cc264525.aspx
>
> What is likely happening is that the 3rd party code is passing bad data to
> irda.sys. Do you have a crash dump file that I can take a look at?
>
>
>


After further research... the only driver support is already built into
Vista.

All you need to do is plug it in and let Vista install the drivers from it's
library. If you did this and you are still having problems with it, return
it.

Maybe get a different brand or wait for Microsoft to fix whatever is the
problem.

https://sftus.one.microsoft.com/choo...6-3ff0310886f6

Password (no quotes): "mDL4yV89a%_#In"


"RedLars" <> wrote in message
news:01e7f542-18b0-47d5-8d1c-...
On 4 Jun, 23:35, "Timothy Davis [MSFT]" <tida...@microsoft.com> wrote:
> As I understand it, irda.sys is a class driver. This means that Microsoft
> writes most of the driver stack, and a 3rd party will often write a small
> portion of the stack via a device driver that has hardware specific code.
>
> You can see a graphic representation of this model for CIR:
>
> http://msdn.microsoft.com/en-us/library/cc264525.aspx
>
> What is likely happening is that the 3rd party code is passing bad data to
> irda.sys. Do you have a crash dump file that I can take a look at?
>
> "Tae Song" <tae_s...@hotmail.com> wrote in message
>
> news:B7B48D8D-4C8C-46B7-8496-...
>
>
>
>
>
> > "RedLars" <Liverpool1...@gmail.com> wrote in message
> >news:cb6ac3ab-b12a-4f70-92ac-...
> >> Bought an USB 2.0 IrDA Dongle from STLab (http://www.st-lab.com/) and
> >> installed their driver. Then tried to use it via Polar ProTrainer 5
> >> and ... bsod.
>
> >> Using Vista Home Premium.
>
> >> I opend the memory.dmp file in windbg and here is some info;
>
> >> 1: kd> !analyze -v
> >> ************************************************** ******************************
> >> *
> >> *
> >> * Bugcheck
> >> Analysis *
> >> *
> >> *
> >> ************************************************** ******************************
>
> >> 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: ffffffec, memory referenced
> >> Arg2: 00000002, IRQL
> >> Arg3: 00000000, value 0 = read operation, 1 = write operation
> >> Arg4: 0139b30f, address which referenced memory
>
> >> Debugging Details:
> >> ------------------
>
> >> READ_ADDRESS: ffffffec
>
> >> CURRENT_IRQL: 2
>
> >> FAULTING_IP:
> >> +139b30f
> >> 0139b30f ?? ???
>
> >> PROCESS_NAME: System
>
> >> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> >> BUGCHECK_STR: 0xD1
>
> >> TRAP_FRAME: 8c3dfa78 -- (.trap 0xffffffff8c3dfa78)
> >> ErrCode = 00000000
> >> eax=5054047a ebx=00000000 ecx=8b08ab57 edx=00001351 esi=00000000
> >> edi=869ce780
> >> eip=0139b30f esp=8c3dfaec ebp=8c3dfaf8 iopl=0 nv up ei pl nz
> >> ac po cy
> >> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> >> efl=00010213
> >> 0139b30f ?? ???
> >> Resetting default scope
>
> >> LAST_CONTROL_TRANSFER: from 0139b30f to 82049374
>
> >> STACK_TEXT:
> >> 8c3dfa78 0139b30f badb0d00 00001351 00000f43 nt!KiTrap0E+0x2ac
> >> WARNING: Frame IP not in any known module. Following frames may be
> >> wrong.
> >> 8c3dfae8 8c3dfb30 852f4200 00000006 8c3dfb14 0x139b30f
> >> 8c3dfaf8 8239b500 8b089002 8c3dfb30 8c3dfb30 0x8c3dfb30
> >> 8c3dfb14 8239b6c9 865fb880 8c3dfb30 82036f25 hal!
> >> HalpCheckForSoftwareInterrupt+0x64
> >> 8c3dfb20 82036f25 82398d00 00000072 8c3dfc08 hal!HalEndSystemInterrupt
> >> +0x73
> >> 8c3dfb20 9c58b9a3 82398d00 00000072 8c3dfc08 nt!KiChainedDispatch+0x65
> >> 8c3dfc08 9c597e1a 85bfc9f8 84eb58f8 8c3dfcb0 irda!SlotTimerExp+0x1c
> >> 8c3dfc7c 9c58d043 85bfc9f8 8c3dfcb0 84eb58f8 irda!
> >> ProcessMACControlConf
> >> +0xbb
> >> 8c3dfc90 9c597315 85bfc9f8 8c3dfcb0 9c594000 irda!IrlapUp+0x45
> >> 8c3dfd10 9c583f48 84eb58f8 84eb59bc 84eb59b8 irda!MediaSenseExp+0x69
> >> 8c3dfd28 8dc3a060 84eb59b8 84eb5960 820f563c irda!IrdaTimerExpFunc
> >> +0x5b
> >> 8c3dfd44 8206a08a 84eb5960 00000000 8441a020 TDI!CTEpEventHandler+0x32
> >> 8c3dfd7c 821afbf9 84eb59b8 8c3d4680 00000000 nt!ExpWorkerThread+0xfd
> >> 8c3dfdc0 8209a3a6 82069f8d 00000001 00000000 nt!PspSystemThreadStartup
> >> +0x9d
> >> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
> >> STACK_COMMAND: kb
>
> >> FOLLOWUP_IP:
> >> nt!KiTrap0E+2ac
> >> 82049374 833d00f8118200 cmp dword ptr [nt!KiFreezeFlag
> >> (8211f800)],0
>
> >> SYMBOL_STACK_INDEX: 0
>
> >> SYMBOL_NAME: nt!KiTrap0E+2ac
>
> >> FOLLOWUP_NAME: MachineOwner
>
> >> MODULE_NAME: nt
>
> >> IMAGE_NAME: ntkrnlmp.exe
>
> >> DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8c09
>
> >> FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>
> >> BUCKET_ID: 0xD1_nt!KiTrap0E+2ac
>
> >> Followup: MachineOwner
>
> >> 1: kd> lmv mirda
> >> start end module name
> >> 9c582000 9c5a0000 irda (pdb symbols) c:\symbols
> >> \irda.pdb\D94057B826FA4A9CA3F1FDCC8A0AE6C22\irda.p db
> >> Loaded symbol image file: irda.sys
> >> Image path: \SystemRoot\system32\DRIVERS\irda.sys
> >> Image name: irda.sys
> >> Timestamp: Thu Nov 02 09:57:09 2006 (4549B2E5)
> >> CheckSum: 0001EA89
> >> ImageSize: 0001E000
> >> Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
>
> >> irda.sys is a microsoft IRDA protocol driver.
>
> >> Any clues ?
>
> > Which one do you have? I see they have have 3 different IRDA models...
>
> > USB IRDA (probably not it) phased out
> > USB 2.0 IRDA-4210 (4 Mbit) phased out
> > USB 2.0 IRDA-4220 (16 Mbit)
>
> > Did you look for a newer driver on their website?– Skjul sitert tekst –
>
> – Vis sitert tekst –

I have the memory.dmp from the last bsod that you can look at. Where
do I send it? (unsure of the size of the file).