- Thread Author
-
- #1
Hi,
Computer recently started giving me the BSOD.
I've tried the following;
Fresh windows install
All drivers have been updated
Registry files have been cleaned using CCleaner.
Hopefully you can help me decipher the DEBUG file.
Link Removed
Debug analysis below:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this BugCheck.
Arguments:
Arg1: 0000000000000008, An operation occurred on a DMA transaction object while it
was not in the correct state.
Arg2: 000039f7caf1c348, Reserved.
Arg3: 0000000000000007, Reserved.
Arg4: ffffc6082ff86d70, Reserved.
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3327
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 22255
Key : Analysis.Init.CPU.mSec
Value: 358
Key : Analysis.Init.Elapsed.mSec
Value: 6421
Key : Analysis.Memory.CommitPeak.Mb
Value: 95
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: 121321-9609-01.dmp
BUGCHECK_CODE: 10d
BUGCHECK_P1: 8
BUGCHECK_P2: 39f7caf1c348
BUGCHECK_P3: 7
BUGCHECK_P4: ffffc6082ff86d70
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff804`3c6053e8 fffff804`4244c6cc : 00000000`0000010d 00000000`00000008 000039f7`caf1c348 00000000`00000007 : nt!KeBugCheckEx
fffff804`3c6053f0 fffff804`42438ccb : ffffc608`350e3cb0 ffffc608`350e3e80 00000000`00000200 00000000`00000003 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
fffff804`3c605430 fffff804`42433daf : ffffc608`2ff86d70 00000000`00000200 00000001`28f51080 00000000`00000001 : Wdf01000!FxDmaTransactionBase::CancelResourceAllocation+0xff [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionbase.cpp @ 736]
fffff804`3c605480 fffff804`57726bf6 : ffffc608`350e3cb0 00000000`00000001 fffff804`57732110 00000000`00000000 : Wdf01000!imp_WdfDmaTransactionCancel+0x7f [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionapi.cpp @ 1257]
fffff804`3c6054c0 ffffc608`350e3cb0 : 00000000`00000001 fffff804`57732110 00000000`00000000 ffffc608`342df610 : iaLPSS2_I2C_CNL+0x16bf6
fffff804`3c6054c8 00000000`00000001 : fffff804`57732110 00000000`00000000 ffffc608`342df610 fffff804`423e36f3 : 0xffffc608`350e3cb0
fffff804`3c6054d0 fffff804`57732110 : 00000000`00000000 ffffc608`342df610 fffff804`423e36f3 ffffc8cf`5d0c5282 : 0x1
fffff804`3c6054d8 00000000`00000000 : ffffc608`342df610 fffff804`423e36f3 ffffc8cf`5d0c5282 fffff804`57725d2f : iaLPSS2_I2C_CNL+0x22110
SYMBOL_NAME: iaLPSS2_I2C_CNL+16bf6
MODULE_NAME: iaLPSS2_I2C_CNL
IMAGE_NAME: iaLPSS2_I2C_CNL.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 16bf6
FAILURE_BUCKET_ID: 0x10D_8_iaLPSS2_I2C_CNL!unknown_function
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3a301fa3-89b5-c930-fd1f-a499b6c5b298}
Followup: MachineOwner
---------
Computer recently started giving me the BSOD.
I've tried the following;
Fresh windows install
All drivers have been updated
Registry files have been cleaned using CCleaner.
Hopefully you can help me decipher the DEBUG file.
Link Removed
Debug analysis below:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this BugCheck.
Arguments:
Arg1: 0000000000000008, An operation occurred on a DMA transaction object while it
was not in the correct state.
Arg2: 000039f7caf1c348, Reserved.
Arg3: 0000000000000007, Reserved.
Arg4: ffffc6082ff86d70, Reserved.
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3327
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 22255
Key : Analysis.Init.CPU.mSec
Value: 358
Key : Analysis.Init.Elapsed.mSec
Value: 6421
Key : Analysis.Memory.CommitPeak.Mb
Value: 95
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: 121321-9609-01.dmp
BUGCHECK_CODE: 10d
BUGCHECK_P1: 8
BUGCHECK_P2: 39f7caf1c348
BUGCHECK_P3: 7
BUGCHECK_P4: ffffc6082ff86d70
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff804`3c6053e8 fffff804`4244c6cc : 00000000`0000010d 00000000`00000008 000039f7`caf1c348 00000000`00000007 : nt!KeBugCheckEx
fffff804`3c6053f0 fffff804`42438ccb : ffffc608`350e3cb0 ffffc608`350e3e80 00000000`00000200 00000000`00000003 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
fffff804`3c605430 fffff804`42433daf : ffffc608`2ff86d70 00000000`00000200 00000001`28f51080 00000000`00000001 : Wdf01000!FxDmaTransactionBase::CancelResourceAllocation+0xff [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionbase.cpp @ 736]
fffff804`3c605480 fffff804`57726bf6 : ffffc608`350e3cb0 00000000`00000001 fffff804`57732110 00000000`00000000 : Wdf01000!imp_WdfDmaTransactionCancel+0x7f [minkernel\wdf\framework\kmdf\src\dma\base\fxdmatransactionapi.cpp @ 1257]
fffff804`3c6054c0 ffffc608`350e3cb0 : 00000000`00000001 fffff804`57732110 00000000`00000000 ffffc608`342df610 : iaLPSS2_I2C_CNL+0x16bf6
fffff804`3c6054c8 00000000`00000001 : fffff804`57732110 00000000`00000000 ffffc608`342df610 fffff804`423e36f3 : 0xffffc608`350e3cb0
fffff804`3c6054d0 fffff804`57732110 : 00000000`00000000 ffffc608`342df610 fffff804`423e36f3 ffffc8cf`5d0c5282 : 0x1
fffff804`3c6054d8 00000000`00000000 : ffffc608`342df610 fffff804`423e36f3 ffffc8cf`5d0c5282 fffff804`57725d2f : iaLPSS2_I2C_CNL+0x22110
SYMBOL_NAME: iaLPSS2_I2C_CNL+16bf6
MODULE_NAME: iaLPSS2_I2C_CNL
IMAGE_NAME: iaLPSS2_I2C_CNL.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 16bf6
FAILURE_BUCKET_ID: 0x10D_8_iaLPSS2_I2C_CNL!unknown_function
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3a301fa3-89b5-c930-fd1f-a499b6c5b298}
Followup: MachineOwner
---------
Solution
The dump file isn't actually accessible by the way, though i may not need.
iaLPSS2_I2C_CNL.sys is the driver file that is actually causing the crash, with searching it looks like a intel serial io driver.
You said the drivers seemed okay, did you reinstall it from the manufacturers website?
Did this start up after a recent windows update as well?
iaLPSS2_I2C_CNL.sys is the driver file that is actually causing the crash, with searching it looks like a intel serial io driver.
You said the drivers seemed okay, did you reinstall it from the manufacturers website?
Did this start up after a recent windows update as well?
- Thread Author
-
- #3
Thanks for the suggestions.Can you open command prompt and type “sfc /scannow” then if that doesnt help go onto your drives in explorer, right click them and go to properties, click the tools and the check for errors.
Let’s see if that helps first.
No errors found from system file checker. Also all driver seem to be running as they should.
Meowkatt
Member
- Joined
- Dec 12, 2021
- Messages
- 47
The dump file isn't actually accessible by the way, though i may not need.
iaLPSS2_I2C_CNL.sys is the driver file that is actually causing the crash, with searching it looks like a intel serial io driver.
You said the drivers seemed okay, did you reinstall it from the manufacturers website?
Did this start up after a recent windows update as well?
iaLPSS2_I2C_CNL.sys is the driver file that is actually causing the crash, with searching it looks like a intel serial io driver.
You said the drivers seemed okay, did you reinstall it from the manufacturers website?
Did this start up after a recent windows update as well?
Last edited:
Similar threads
- Solved
- Replies
- 4
- Views
- 4K
- Solved
- Replies
- 12
- Views
- 6K
- Solved
- Replies
- 1
- Views
- 2K