Reefboi16 Posted May 6, 2017 Share Posted May 6, 2017 As the title states I have been fighting with this problem for some time now. I have uninstalled and reinstalled CUE and its causing nothing but issues. I ran verifier to drill down to the problem and I BSOD upon boot and the cause is the Corsair virtual device driver file version 3.0.65. I have all windows updates I am on Microsoft Windows 10 Pro, Version 1703 OS build 15063.250. I will include dump file below.050617-15437-01.zip Link to comment Share on other sites More sharing options...
Reefboi16 Posted May 6, 2017 Author Share Posted May 6, 2017 And if I posted here is because when I uninstall CUE it does not BSOD then I install CUE that's when I have the problem. Link to comment Share on other sites More sharing options...
red-ray Posted May 6, 2017 Share Posted May 6, 2017 A device driver attempting to corrupt the system has been caught. Use !analyze -v to get detailed debugging information. BugCheck C4, {2000, fffff8081d031757, 0, 43514d4b} *** WARNING: Unable to verify timestamp for CorsairVBusDriver.sys *** ERROR: Module load completed but symbols could not be loaded for CorsairVBusDriver.sys Probably caused by : CorsairVBusDriver.sys ( CorsairVBusDriver+1757 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx) Arg2: fffff8081d031757, The address in the driver's code where the error was detected. Arg3: 0000000000000000, Pool Type. Arg4: 0000000043514d4b, Pool Tag (if provided). Debugging Details: ------------------ BUGCHECK_P1: 2000 BUGCHECK_P2: fffff8081d031757 BUGCHECK_P3: 0 BUGCHECK_P4: 43514d4b BUGCHECK_STR: 0xc4_2000 CPU_COUNT: 4 CPU_MHZ: db0 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 5e CPU_STEPPING: 3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10240.9 amd64fre LAST_CONTROL_TRANSFER: from fffff8009a779fff to fffff8009a178fd0 STACK_TEXT: ffffc380`00ac81f8 fffff800`9a779fff : 00000000`000000c4 00000000`00002000 fffff808`1d031757 00000000`00000000 : nt!KeBugCheckEx ffffc380`00ac8200 fffff800`9a25aaef : fffff808`1d031700 fffff800`9a77198a fffff800`9a2c4210 00000000`00000003 : nt!VerifierBugCheckIfAppropriate+0x6b ffffc380`00ac8240 fffff800`9a771870 : 00000000`43514d4b fffff800`9a34b3a0 fffff808`1d031757 ffffc380`00ac82b8 : nt!VfReportIssueWithOptions+0x103 ffffc380`00ac8290 fffff800`9a76f6c1 : 00000000`43514d4b ffffd480`bb5856f0 00000000`00000000 fffff800`9a78bd12 : nt!VfCheckPoolType+0x90 ffffc380`00ac82d0 fffff808`1d031757 : ffffd480`bb585840 ffffd480`bb585840 ffffd480`bb585840 00000000`00000000 : nt!VerifierExAllocatePoolEx+0x21 ffffc380`00ac8320 ffffd480`bb585840 : ffffd480`bb585840 ffffd480`bb585840 00000000`00000000 ffffbf0f`7b1ded00 : CorsairVBusDriver+0x1757 ffffc380`00ac8328 ffffd480`bb585840 : ffffd480`bb585840 00000000`00000000 ffffbf0f`7b1ded00 00000000`003436b4 : 0xffffd480`bb585840 ffffc380`00ac8330 ffffd480`bb585840 : 00000000`00000000 ffffbf0f`7b1ded00 00000000`003436b4 00000000`00000000 : 0xffffd480`bb585840 ffffc380`00ac8338 00000000`00000000 : ffffbf0f`7b1ded00 00000000`003436b4 00000000`00000000 fffff808`1d031c8f : 0xffffd480`bb585840 STACK_COMMAND: kb FOLLOWUP_IP: CorsairVBusDriver+1757 fffff808`1d031757 4885c0 test rax,rax SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: CorsairVBusDriver+1757 FOLLOWUP_NAME: MachineOwner MODULE_NAME: CorsairVBusDriver IMAGE_NAME: CorsairVBusDriver.sys DEBUG_FLR_IMAGE_TIMESTAMP: 587e4d4d BUCKET_ID_FUNC_OFFSET: 1757 FAILURE_BUCKET_ID: 0xc4_2000_VRF_CorsairVBusDriver!Unknown_Function BUCKET_ID: 0xc4_2000_VRF_CorsairVBusDriver!Unknown_Function PRIMARY_PROBLEM_CLASS: 0xc4_2000_VRF_CorsairVBusDriver!Unknown_Function ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xc4_2000_vrf_corsairvbusdriver!unknown_function FAILURE_ID_HASH: {e57096e8-bc09-fbc5-0391-a63fca5731b3} Followup: MachineOwner --------- Link to comment Share on other sites More sharing options...
Reefboi16 Posted May 6, 2017 Author Share Posted May 6, 2017 Any suggestions? Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted May 9, 2017 Corsair Employee Share Posted May 9, 2017 An older version of CUE would trigger a BSOD but we resolved it since 2.10 if I recall. Please try using 2.13 that I uploaded today. PS: I don't monitor the forums often as these are user forums. If you need quicker assistance, contact our support team. Link to comment Share on other sites More sharing options...
Reefboi16 Posted May 11, 2017 Author Share Posted May 11, 2017 Negative. I was on the latest CUE version and it was giving me a boss. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted May 12, 2017 Corsair Employee Share Posted May 12, 2017 Let me pass your BSOD to the devs and review it. Does this happen 10:10 times? Also, I need a breakdown of your hardware specs. Link to comment Share on other sites More sharing options...
Reefboi16 Posted May 12, 2017 Author Share Posted May 12, 2017 Let me pass your BSOD to the devs and review it. Does this happen 10:10 times? Also, I need a breakdown of your hardware specs. I just updated to the latest CUE and still same thing. Yes I can confirm it BSOD's twice a day. As soon as I uninstall CUE and it's drivers bsod stops. Intel i5 6600k (not OC'd) MSI PC MATE Z170A 18gb DDR4 Kingston 1tb ssd GTX 1070 ASUS DUAL 8gb ddr5 Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted May 17, 2017 Corsair Employee Share Posted May 17, 2017 Thanks for the logs Reef. Our devs have confirmed the issue and have already removed that part of the code from the driver to prevent your issue (and to solve another). The updated driver will be a part of 2.14. Ping me on Friday and I can give you a beta drop so you can try it out. Link to comment Share on other sites More sharing options...
Reefboi16 Posted May 19, 2017 Author Share Posted May 19, 2017 Thanks for the logs Reef. Our devs have confirmed the issue and have already removed that part of the code from the driver to prevent your issue (and to solve another). The updated driver will be a part of 2.14. Ping me on Friday and I can give you a beta drop so you can try it out. Awesome to hear. I will hit you up tomorrow. Link to comment Share on other sites More sharing options...
Vercinger Posted June 15, 2017 Share Posted June 15, 2017 Hello, I've been getting more and more BSODs as of late, so I did a driver verification and the culprit was/is corsairvbusdriver.sys I've tried updating CUE to the latest version, but I am still getting BSODs from that driver. i7 7700k MSI z270 carbon gaming pro CORSAIR Vengance 32 GB 250 GB SSD SAMSUNG MSI GTX 1080 Windows 10 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.