PCI7412: PCI7412

Hello,

Is the Windows driver for PCI7412 already installed?
The Windows driver for PCI7412 was designed for operating systems prior to Windows Vista, so I wouldn't be surprised if it crashes on Windows 10.
Driver support for the PCI7412 is no longer provided.

If the crash is occurring before installing the Windows driver, it most likely is a problem with your PCIe to PCI bridge.

Regards,
Jorge

Hello,
We do not install any special PCI7412 Driver. It is Microsoft default driver.
The failure occurs in both WIN 10 and WIN7 as well.
The failure is not constant- it may boot O.K. for three days every boot, than after 2 days or week it fails all the time.
It seems that the WIN10 crash(dump) during boot or windows 7 blue screen(dump) during boot occurs during enumeration phase
before loading driver - but we are not sure.
In most cases of failure - boot to DOS is O.K. and PCI7412 exists.

A successful boot to WIN 10 shows the following driver details:
Texas Instruments PCI-8X12/7X12/6X12 CardBus Controller
Driver provider: Microsoft
Driver date: 6/21/2006
Driver version 10.0.14393.0

Driver details:
C\Windows\System32\drivers\PCI.SYS
C\Windows\System32\Drivers\PCMCIA.SYS

***

Hello,

Are you using the Flashmedia instance of the PCI7412? or this instance is disabled?

Can you please send us a kernel memory dump when the problem occours?

Regards,
Roberto.

Hello,
We are not using the Flashmedia instance.
We don't know how to disable the Flashmedia function.
We shall appreciate it very much if we can get an E2PROM Read/Write/Edit tool in order to disable the Flashmedia function and how to disable it.

We have a kernel memory dump file. We need to know how we can send it via mail or upload to this post.
Sincerely Yours
Avi

Hello Avi,

You can send us your kernel dump using https://app.box.com/login

If the driver is causin a creash you should contact MSFT who is the ouner of this driver. unfortunatelly we are not able to modify it.

Regards,
Roberto

Hello Roberto
I have already uploaded the kernel dump in zip file in post dated Sept 5 2017 080217-4234-01.7z
Thank you,
Avi

Hello Avi,

If the driver is causing a crash you should contact MSFT who is the owner of this driver. unfortunately, we are not able to modify it.

Regards,
Roberto

Hello Roberto
The problem happens in safe mode as well. We have uploaded the zipped kernel using reach text mode option of this site.
The problem does not appear constantly. One week it boots O.K. and the second week it may always fail.
We use Cardbus Card function only. We don't need Firewire OHCI or any Flash Media option.
Regards,
Avi

Dear Roberto

Thank you.

Does the kernel dump that I had uploaded shows that it is a crash in the driver?

Sincerely Yours

Avi

Hello Avi,

This is the dump output,

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff800f780b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 16e5

STACK_TEXT:
fffff800`f9536e08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x149f90


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

*** Memory manager detected 5861 instance(s) of page corruption, target is likely to have memory corruption.

0: kd> lmvm GenuineIntel
start end module name
0: kd> lmvm nt
start end module name
fffff800`f780b000 fffff800`f802b000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Fri Jul 15 21:16:17 2016 (578998F1)
CheckSum: 0077AC55
ImageSize: 00820000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


Regards,
Roberto