rewasd driver causing BSOD

[zhubaohi01@gmail.com]

My PC encountered a BSOD while gaming and after analizing the dump files, it points to the driver r1710map.sys, which should be the rewasd remapping driver. Here's the report of the BSOD.

[strokel]

Hey there!

Please check for errors in Event Viewer by following the steps below:
1. Press the Windows button, type [Event Viewer], and press Enter.
2. Choose [Windows Logs] in the upper left corner, then choose [Application].
3. Check out the panel on the right side: there's a [Find] option. Click it, and type "reWASD" to search for related errors.
4. Once you find one or multiple events, please right-click and "Save selected events..." on every one of them, and send us the file(s).

[Support Agent]

Please also include the minidump file.

[Lonesurvivalist]

wanted to report the same issue. I don't have any event viewer logs that look suspect but I do have a dump file if you need it unfortunately is too big to upload though

[Lonesurvivalist]

when I open the dump file an analyze it I get the following: SYMBOL_NAME: r1710map+140be

MODULE_NAME: r1710map

IMAGE_NAME: r1710map.sys

STACK_COMMAND: .cxr 0xffff9200371728e0 ; kb

BUCKET_ID_FUNC_OFFSET: 140be

FAILURE_BUCKET_ID: AV_r1710map!unknown_function

[Support Agent]

Lonesurvivalist How big are we talking? If you can't upload it to the forum, you can try using any cloud storage service with public access.

[Lonesurvivalist]

Shion its approximately 6 mb in size. Ill compress it and upload it looks like less than a MB now

[zhubaohi01@gmail.com]

Please also include the minidump file.

Hi, here's the minidump file.

https://drive.google.com/file/d/100QgxP5BbwnCA3pJwrSctWlG5hge5kPa/view?usp=drive_link

Nothing shows up in the event viewer during the BSOD.

[strokel]

Hi zhubaohi01@gmail.com

We do not have access to download the file.

[DevX]

We checked this and found it is really old problem reproduced only if you use Driver Verifier and some addition verification options (NDIS specific).
The code where crash happens is executed when you use Xbox Wireless dongle, but we did not find any bugs there and it is used very actively, so in case of real bug it would cause crash almost for anyone.
We had only several such reports in many years, but only from people who used additional (beyond standard) verifier options to "stress" their system.
So we assumed it is more like "false alarm" caused by some combination of verifier options in Microsoft drivers.
Do you use Driver Verifier too?

[zhubaohi01@gmail.com]

We checked this and found it is really old problem reproduced only if you use Driver Verifier and some addition verification options (NDIS specific).
The code where crash happens is executed when you use Xbox Wireless dongle, but we did not find and bugs there and it is used very actively, so in case of real bug it would cause crash
almost for anyone. We had only several such reports in many years, but only from people who used additional (beyond standard) verifier options to "stress" their system.
So we assumed it is more like "false alarm" caused by some combination of verifier options in Microsoft drivers.
Do you use Driver Verifier too?

I don't, but since the crash is not very often I'll see if it happens again in the future. Maybe it's just a false alarm. I mean sometimes blue screen happens for no reason at all.

[DevX]

Even if you don't use it, there is a chance some verifier options could be enabled by other programs on your PC. To be sure, run verifier.exe from C:\Windows\System32 folder under administrator.
This is standard Microsoft tool for setting driver verification options. Now select 'Delete existing settings', press 'Finish' and reboot your system.
This will get rid of any settings. This tool is intended to be used by driver developers only and any verifier option will also slow down your system significantly! So make sure you have nothing enabled there unless instructed by support.

[zhubaohi01@gmail.com]

Even if you don't use it, there is a chance some verifier options could be enabled by other programs on your PC. To be sure, run verifier.exe from C:\Windows\System32 folder under administrator.
This is standard Microsoft tool for setting driver verification options. Now select 'Delete existing settings', press 'Finish' and reboot your system.
This will get rid of any settings. This tool is intended to be used by driver developers only and any verifier option will also slow down your system significantly! So make sure you have nothing enabled there unless instructed by support.

Thanks for the tip. When I used the delete existing settings, it says "No settings are changed". Should indicate that I didn't have anything set up prior to this.
But I did it and reboot anyways to make sure.