Include the brand and model name of your computer as well in the query.
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. Jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.) Click on the links below to search with Google for updates for these drivers: It is strongly suggested that you check for updates for these drivers on their company websites. A third party driver has been identified to be causing system crashes on your computer. This was probably caused by the following module: jraid.sys (0xFFFFF806B21CBE33)īugcheck code: 0xD1 (0xFFFFE6C0FB40B264, 0x5, 0x0, 0xFFFFF806B21CBE33)Ģ3 crash dumps have been found and analyzed. Possibly this problem is caused by another driver that cannot be identified at this time. The crash took place in the Windows kernel.
Product: Microsoft® Windows® Operating Systemīug check description: The kernel has detected the corruption of a critical data structure.
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)īugcheck code: 0x139 (0x3, 0xFFFFDF80AF418710, 0xFFFFDF80AF418668, 0x0)įile path: C:\WINDOWS\system32\ntoskrnl.exe This was probably caused by the following module: jraid.sys (0xFFFFF80AC43ABE33)īugcheck code: 0xD1 (0xFFFFE1A8D0E2DFBE, 0x5, 0x0, 0xFFFFF80AC43ABE33)Ĭrash dump file: C:\WINDOWS\Minidump\011017-8968-01.dmp This was probably caused by the following module: jraid.sys (0xFFFFF80D8D47BE33)īugcheck code: 0xD1 (0xFFFFDACFED4999CF, 0x5, 0x0, 0xFFFFF80D8D47BE33)Ĭrash dump file: C:\WINDOWS\Minidump\011017-9000-01.dmp
It is suggested you look for an update for the following driver: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.).
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.Ī third party driver was identified as the probable root cause of this system error. This was probably caused by the following module: jraid.sys (0xFFFFF80563074356)īugcheck code: 0xD1 (0xFFFFBF8D6C6A1ECA, 0x9, 0x0, 0xFFFFF80563074356)įile path: C:\WINDOWS\system32\drivers\jraid.sysīug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. Hardware: X58A-UD3R, Gigabyte Technology Co., Ltd.ĬPU: GenuineIntel Intel(R) Core(TM) i7 CPU 930 2.80GHz Intel586, level: 6Ĭrash dump directory: C:\WINDOWS\MinidumpĬrash dumps are enabled on your computer.Ĭrash dump file: C:\WINDOWS\Minidump\011717-14781-01.dmp Windows version: Windows 10, 10.0, build: 14393 Hardware Abstraction Layer Version = "3.206" F5, īaseBoard Manufacturer Gigabyte Technology Co., Ltd. Processor Intel(R) Core(TM) i7 CPU 930 2.80GHz, 2794 Mhz, 4 Core(s), 8 Logical Processor(s)īIOS Version/Date Award Software International, Inc. System Manufacturer Gigabyte Technology Co., Ltd. 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? Is it just a simple driver update issue? If so can you please help me work out what I need to do next. I have swapped ports on HDD etc, absolutely no luck at all. I have tried various solutions as a few forums lead me to think it was a SATA HDD port issue. Over the past year I have had the same BSOD continually. Also removed my DVD rom and have had the same bsod.I have moved this thread to WIN 10 as still had no reply or any luck.