Download here: http://gg.gg/nvxu0/1
JMICRON JMB363 CONTROLLER DRIVERS FOR WINDOWS 7 - Anyway, you can erase the flash chip, so that no option ROM is executed and the card is rendered non-bootable anymore. Hard drive is SATA. As for me, I no. Operating System: Microsoft Windows 10 (64-bit) After entering the serial # for my laptop on hp.com, no Windows 10 drivers are offered for the JMicron Media Card Reader. I used the one for Windows 8.1 (sp57014) with no errors, but has a later driver been released? Why cant i download adobe flash player on my mac.
*I have moved this thread to WIN 10 as still had no reply or any luck
*Also removed my DVD rom and have had the same bsod.. any help sincerely appreciated.
*Please help. Over the past year I have had the same BSOD continually. See crash dump file below. JMICRON raid driver. I have tried various solutions as a few forums lead me to think it was a SATA HDD port issue. I have swapped ports on HDD etc, absolutely no luck at all. Is it just a simple driver update issue? If so can you please help me work out what I need to do next. Appreciate any help. Everytime it crashes it reboots which is extremely frustrating when I lose info etc..I did notice the BIOS vers 2010, does it have anything to do with an outdated driver?
SPECS
OS Name Microsoft Windows 10 Home
Version 10.0.14393 Build 14393
System Manufacturer Gigabyte Technology Co., Ltd.
System Model X58A-UD3R
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz, 2794 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F5, 3/11/2010
SMBIOS Version 2.4
Embedded Controller Version 255.255
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
Hardware Abstraction Layer Version = ’10.0.14393.206’
Installed Physical Memory (RAM) 6.00 GB
System Information (local)
Computer name: JASON-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:WINDOWS
Hardware: X58A-UD3R, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4293382144 bytes total
Crash Dump Analysis
Crash dump directory: C:WINDOWSMinidump
Crash dumps are enabled on your computer.
On Tue 1/17/2017 5:42:00 PM your computer crashed
crash dump file: C:WINDOWSMinidump011717-14781-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF80563074356)
Bugcheck code: 0xD1 (0xFFFFBF8D6C6A1ECA, 0x9, 0x0, 0xFFFFF80563074356)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 1/17/2017 5:20:43 PM your computer crashed
crash dump file: C:WINDOWSMinidump011717-12546-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF80D8D47BE33)
Bugcheck code: 0xD1 (0xFFFFDACFED4999CF, 0x5, 0x0, 0xFFFFF80D8D47BE33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 1/10/2017 4:21:30 PM your computer crashed
crash dump file: C:WINDOWSMinidump011017-9000-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF80AC43ABE33)
Bugcheck code: 0xD1 (0xFFFFE1A8D0E2DFBE, 0x5, 0x0, 0xFFFFF80AC43ABE33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 1/10/2017 1:57:38 PM your computer crashed
crash dump file: C:WINDOWSMinidump011017-8968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFDF80AF418710, 0xFFFFDF80AF418668, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 1/10/2017 12:58:38 PM your computer crashed
crash dump file: C:WINDOWSMinidump011017-10312-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF806B21CBE33)
Bugcheck code: 0xD1 (0xFFFFE6C0FB40B264, 0x5, 0x0, 0xFFFFF806B21CBE33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
Conclusion
23 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it’s not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it’s suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
locu5t, Jan 17, 2017
#1
*
locu5tThread Starter
Joined:
Jan 17, 2017
Messages:
2
Possible cause and solution.
https://www.eightforums.com/drivers-hardware/39285-incompatibility-jmicron-jmb36x-windows-8-1-a.html
I am not very confident deleting registry values. I will try to disconnect my DVD rom for a time and see if it solves the issue.
You might try looking through the Linux kernel sources to see if the driver for the 88SE gives any clues as to how the chip works…. Why do you want to avoid the on-board SATA controller? Here is the link: Actually, there is only one sata connexion, not two. All times are GMT These configuration registers seem to control the hardware directly. The last byte of the file is used as a checksum.Uploader:GolkreeDate Added:20 May 2015File Size:36.46 MbOperating Systems:Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/XDownloads:43423Price:Free* [*Free Regsitration Required]
Hot-plugging the PCIe card never worked for me. Unfortunately, I do not know enough about hex editing to find where to patch. Johng1 Win7 home premium 64bit 6 posts. I have read through this page and start to comprehend the edits needed.
I replaced 3 bytes with b1 02 I did have some issues with the card being seated properly in the PCIe slot. Duufus, I had in the past this card: I want to create an AHCI patched verson of 1. Please work with the latest bios and share it. When running XP, all is well. Many thanks for the modded ROM.JMicron JMB Add-on Card AHCI mode « Blog
Win7 home premium 64bit. Option ROM sets this to either 0xf1 or 0x Sanvean Windows 7 Professional 64 posts Northwestern Pennsylvania.
Both ports on Motherboard. Find More Posts by Sanvean. Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. I tried modifying the option ROM to also configure register 0x to this value, but had many problems booting. At first boot windows installed drivers for this contrkller which I didn’t want to do.JMicron JMB36X SATA Controller Driver Driver – TechSpotJmb363 Driver
It is not a data table containing some form of initial register values. The last byte of the file is used as a checksum.
Blog Random stuff… Comments Posts. There is indeed a checksum byte.
How can I update bios? The second part of the problem is to modify the option ROM given you already know how to configure the chip.
We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Welcome to Windows 7 Forums.
Now how do I uninstall the windows drivers? Linux sets register 40 bit 2 to enable the IDE port?JMicron JMB363 Add-on Card AHCI mode
I used the newest version of the option ROM 1. The option ROM loads, correctly reports connected drives, and allows booting from them.
The original bytes were e8 xx xxwhere e8 is the opcode for the CALL instruction, and the bit immediate operand is the relative branch target. Could you pass on a link please of your setup? They seem important, causing PCI config register bits 0xed[5: I had some help from the option ROM release noteswhich gave some hints as to what the PCI config registers do or at least, supposed to do after being interpreted by the option ROM.
The hang does not occur if the option ROM is skipped by setting 0xdf[6], so I use 0xa1 to be closer to what Linux does, although I notice no other differences between 0xf1 jmicro 0xa1. I even tried running under admin dirrectly but no difference.Jmicron Pcie Drivers Windows 10Last Drivers
Download here: http://gg.gg/nvxu0/1
https://diarynote-jp.indered.space
JMICRON JMB363 CONTROLLER DRIVERS FOR WINDOWS 7 - Anyway, you can erase the flash chip, so that no option ROM is executed and the card is rendered non-bootable anymore. Hard drive is SATA. As for me, I no. Operating System: Microsoft Windows 10 (64-bit) After entering the serial # for my laptop on hp.com, no Windows 10 drivers are offered for the JMicron Media Card Reader. I used the one for Windows 8.1 (sp57014) with no errors, but has a later driver been released? Why cant i download adobe flash player on my mac.
*I have moved this thread to WIN 10 as still had no reply or any luck
*Also removed my DVD rom and have had the same bsod.. any help sincerely appreciated.
*Please help. Over the past year I have had the same BSOD continually. See crash dump file below. JMICRON raid driver. I have tried various solutions as a few forums lead me to think it was a SATA HDD port issue. I have swapped ports on HDD etc, absolutely no luck at all. Is it just a simple driver update issue? If so can you please help me work out what I need to do next. Appreciate any help. Everytime it crashes it reboots which is extremely frustrating when I lose info etc..I did notice the BIOS vers 2010, does it have anything to do with an outdated driver?
SPECS
OS Name Microsoft Windows 10 Home
Version 10.0.14393 Build 14393
System Manufacturer Gigabyte Technology Co., Ltd.
System Model X58A-UD3R
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz, 2794 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F5, 3/11/2010
SMBIOS Version 2.4
Embedded Controller Version 255.255
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
Hardware Abstraction Layer Version = ’10.0.14393.206’
Installed Physical Memory (RAM) 6.00 GB
System Information (local)
Computer name: JASON-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:WINDOWS
Hardware: X58A-UD3R, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4293382144 bytes total
Crash Dump Analysis
Crash dump directory: C:WINDOWSMinidump
Crash dumps are enabled on your computer.
On Tue 1/17/2017 5:42:00 PM your computer crashed
crash dump file: C:WINDOWSMinidump011717-14781-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF80563074356)
Bugcheck code: 0xD1 (0xFFFFBF8D6C6A1ECA, 0x9, 0x0, 0xFFFFF80563074356)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 1/17/2017 5:20:43 PM your computer crashed
crash dump file: C:WINDOWSMinidump011717-12546-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF80D8D47BE33)
Bugcheck code: 0xD1 (0xFFFFDACFED4999CF, 0x5, 0x0, 0xFFFFF80D8D47BE33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 1/10/2017 4:21:30 PM your computer crashed
crash dump file: C:WINDOWSMinidump011017-9000-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF80AC43ABE33)
Bugcheck code: 0xD1 (0xFFFFE1A8D0E2DFBE, 0x5, 0x0, 0xFFFFF80AC43ABE33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 1/10/2017 1:57:38 PM your computer crashed
crash dump file: C:WINDOWSMinidump011017-8968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFDF80AF418710, 0xFFFFDF80AF418668, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 1/10/2017 12:58:38 PM your computer crashed
crash dump file: C:WINDOWSMinidump011017-10312-01.dmp
This was probably caused by the following module: jraid.sys (0xFFFFF806B21CBE33)
Bugcheck code: 0xD1 (0xFFFFE6C0FB40B264, 0x5, 0x0, 0xFFFFF806B21CBE33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:WINDOWSsystem32driversjraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
Google query: JMicron Technology Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL
Conclusion
23 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it’s not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it’s suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
locu5t, Jan 17, 2017
#1
*
locu5tThread Starter
Joined:
Jan 17, 2017
Messages:
2
Possible cause and solution.
https://www.eightforums.com/drivers-hardware/39285-incompatibility-jmicron-jmb36x-windows-8-1-a.html
I am not very confident deleting registry values. I will try to disconnect my DVD rom for a time and see if it solves the issue.
You might try looking through the Linux kernel sources to see if the driver for the 88SE gives any clues as to how the chip works…. Why do you want to avoid the on-board SATA controller? Here is the link: Actually, there is only one sata connexion, not two. All times are GMT These configuration registers seem to control the hardware directly. The last byte of the file is used as a checksum.Uploader:GolkreeDate Added:20 May 2015File Size:36.46 MbOperating Systems:Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/XDownloads:43423Price:Free* [*Free Regsitration Required]
Hot-plugging the PCIe card never worked for me. Unfortunately, I do not know enough about hex editing to find where to patch. Johng1 Win7 home premium 64bit 6 posts. I have read through this page and start to comprehend the edits needed.
I replaced 3 bytes with b1 02 I did have some issues with the card being seated properly in the PCIe slot. Duufus, I had in the past this card: I want to create an AHCI patched verson of 1. Please work with the latest bios and share it. When running XP, all is well. Many thanks for the modded ROM.JMicron JMB Add-on Card AHCI mode « Blog
Win7 home premium 64bit. Option ROM sets this to either 0xf1 or 0x Sanvean Windows 7 Professional 64 posts Northwestern Pennsylvania.
Both ports on Motherboard. Find More Posts by Sanvean. Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. I tried modifying the option ROM to also configure register 0x to this value, but had many problems booting. At first boot windows installed drivers for this contrkller which I didn’t want to do.JMicron JMB36X SATA Controller Driver Driver – TechSpotJmb363 Driver
It is not a data table containing some form of initial register values. The last byte of the file is used as a checksum.
Blog Random stuff… Comments Posts. There is indeed a checksum byte.
How can I update bios? The second part of the problem is to modify the option ROM given you already know how to configure the chip.
We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Welcome to Windows 7 Forums.
Now how do I uninstall the windows drivers? Linux sets register 40 bit 2 to enable the IDE port?JMicron JMB363 Add-on Card AHCI mode
I used the newest version of the option ROM 1. The option ROM loads, correctly reports connected drives, and allows booting from them.
The original bytes were e8 xx xxwhere e8 is the opcode for the CALL instruction, and the bit immediate operand is the relative branch target. Could you pass on a link please of your setup? They seem important, causing PCI config register bits 0xed[5: I had some help from the option ROM release noteswhich gave some hints as to what the PCI config registers do or at least, supposed to do after being interpreted by the option ROM.
The hang does not occur if the option ROM is skipped by setting 0xdf[6], so I use 0xa1 to be closer to what Linux does, although I notice no other differences between 0xf1 jmicro 0xa1. I even tried running under admin dirrectly but no difference.Jmicron Pcie Drivers Windows 10Last Drivers
Download here: http://gg.gg/nvxu0/1
https://diarynote-jp.indered.space
コメント