[SOLVED] UNEXPECTED_KERNEL_MODE_TRAP

Hi markanini. :welcome:
Did you under-overclocked your machine?
When have you cleaned your heatsinks, fans and their "breathers"/"air slits"(???) last time? And put a new layer of thermal past on the processor?
Has your pc got a firewire port? And are you using it?
 
Heatsinks and fans are in good shape, I'm monitoring temps. I have a audio interface connected to the firewire port.
 
Hi Markanini,

The reason I assume Xilolee asked about the firewire port is because one of the two minidumps references 1394ohci.sys, a firewire device driver.

Code: 
# Child-SP          RetAddr           Call Site00 fffff802`e251e278 fffff802`e07ccfe9 nt!KeBugCheckEx
01 fffff802`e251e280 fffff802`e07cb7c7 nt!KiBugCheckDispatch+0x69
02 fffff802`e251e3c0 fffff802`e06252d6 nt!KiPageFault+0x247
03 fffff802`e251e550 fffff802`e06115c5 hal!HalpDmaNextContiguousPieceV2+0x18e
04 fffff802`e251e5a0 fffff802`e0629825 hal!HalpDmaFlushScatterTransferV2+0x6d
05 fffff802`e251e600 fffff802`e0628627 hal!IoFlushAdapterBuffersV2+0x15add
06 fffff802`e251e640 fffff801`9499afdc hal!HalPutScatterGatherList+0x18ae7
07 fffff802`e251e6a0 fffff801`9499c3ea Wdf01000!FxDmaScatterGatherTransaction::PutScatterGatherList+0x40
08 fffff802`e251e6d0 fffff801`9499a32e Wdf01000!FxDmaScatterGatherTransaction::TransferCompleted+0x1a
09 fffff802`e251e700 fffff801`94998321 Wdf01000!FxDmaTransactionBase::DmaCompleted+0x182
0a fffff802`e251e780 fffff801`98695aa3 Wdf01000!imp_WdfDmaTransactionDmaCompletedFinal+0x51
0b fffff802`e251e7b0 fffff801`9869dd8c [COLOR=#ff0000][B]1394ohci!IoWorkers::FlushWdfDmaTransaction+0x37[/B][/COLOR]
0c fffff802`e251e7f0 fffff801`94944325 1394ohci!IsochRx::WdfEvtNotificationDpc+0x1bc
0d fffff802`e251e880 fffff802`e06c9df0 Wdf01000!FxDpc::DpcHandler+0xd5
0e fffff802`e251e8c0 fffff802`e06c9509 nt!KiExecuteAllDpcs+0x270
0f fffff802`e251ea10 fffff802`e07c521a nt!KiRetireDpcList+0xe9
10 fffff802`e251ec60 00000000`00000000 nt!KiIdleLoop+0x5a

For troubleshooting purposes, try disconnecting your firewire device or disabling it through Device Manager, and see if that corrects your issue. The 1394ohci drivers are managed by Windows Update, so I would also suggest ensuring your instance of Windows is fully up to date.
 
markanini said:
I was indeed able to avoid the crash by disabling the FW host controller device.
Click to expand...
I just experienced a crash similar to OP. Disabling the FW controller has made it less frequent though for sure. Should I upload a new SysnativeFileCollectionApp.zip?
 
markanini said:
markanini said:
I was indeed able to avoid the crash by disabling the FW host controller device.
Click to expand...
I just experienced a crash similar to OP. Disabling the FW controller has made it less frequent though for sure. Should I upload a new SysnativeFileCollectionApp.zip?
Click to expand...

Sure, I'd be happy to take a look tomorrow if the collection has new dump files.
 
Hmm, there doesn't appear to be any dump files in your new collection. Did the computer still bluescreen with the same error(s), or did it just crash?
 
Xer said:
Hmm, there doesn't appear to be any dump files in your new collection. Did the computer still bluescreen with the same error(s), or did it just crash?
Click to expand...
You're right, it just crashed without the blue screen while carrying out operations in the same software as in OP. Sorry for being vague.
 
markanini said:
Xer said:
Hmm, there doesn't appear to be any dump files in your new collection. Did the computer still bluescreen with the same error(s), or did it just crash?
Click to expand...
You're right, it just crashed without the blue screen while carrying out operations in the same software as in OP. Sorry for being vague.
Click to expand...

No worries, though there's not much I can say without the computer having produced something to analyse. My only thought would be if there's a separate firewire driver showing under the USB heading, it could be related. I'm not exactly sure what it would show up as, but you could check the Universal Serial Bus Controllers portion of the Device Manager for anything seemingly named/relating to firewire/1394.

Past that, you could try running Verifier, but I'm not sure that it would be any more likely to produce a proper dump.

If the program does crash again on its own and you get a bluescreen/dump file (either C:\Windows\MEMORY.DMP or anything under C:\Windows\minidump\), feel free to post it here.
 
Too slow to make it an edit: Is your firewire device a PreSonus? From the last collection you posted, I see that the driver pae_1394 is present. I assume that whatever you disabled probably works off of it, but it's worth checking. From Device Manager, right-click on the firewire device you had disabled > properties > "Driver" tab > Driver Details > and see if pae_1394.sys is loaded by it (also pae_avs_x64.sys, but I didn't see that listed). If not, there might be something else on the system present that's calling that driver. I'd also suggest you try running a different version for your device from their downloads site if possible.
 
I disabled the FW controller device in BIOS under integrated peripherals and it's no longer showing up in device manager. Do you think that's sufficient?
 
Yes, that should be sufficient to determine if it's caused by that device or something else. Just post an update to the thread if you get another crash. If you do, hopefully it's a bluescreen. Good luck!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top