FreeNAS-11.2 BETA2 causes Blue Screen on Windows 7 when plugging/refreshing the USB drive #1188
Comments
|
I'll try to test this when I get a chance, but can you please test what happens when you win32diskimager on Windows to write that image? I strongly doubt this has anything to do with Rufus and even less with something that we can fix as, as the image writing process is exceedingly basic and straightforward: write every block of data as is. If Windows parses the data we send to the drive (could be a Windows Defender issue), and then crashes, whereas all we are doing, really, is send it sequentially, there really doesn't exist much of anything to fix. Also, is there a reason why you used the I'll see whether I can replicate the issue once I have downloaded that image. |
|
Tested on Windows 10 x64, and saw no issue: I'm not sure I have a build 14393 of Windows 10 64-bit anywhere to test. Possibly this was an OS bug that Microsoft fixed in subsequent Windows 10 updates... |
|
Hello thank you for your reply, I forgot to mention the system affected is a Windows 7 Pro x64. I also tested on Windows 10 x64 on a laptop and got the same if not very similar result as you. I just did the standard "find the download and flash the iso" and frankly did not find out about a ".txz" file. So ill try it when I get a chance. And Yes I already confirmed the sha256 hash using rufus. |
|
Please try win32diskimager or any other |
|
Also, another thing you can try: Can you try writing to a VHD? See here for how you can create a VHD to use with Rufus. This would tell us if your issue has anything to do with sending data over the USB bus. |
|
Aha, looks like this is a pure Windows 7 issue with how it parses the USB data when you plug the drive. And the kicker is, the same behaviour happened even when using As soon as I plug the drive created under Linux using Isn't that nice? You have found a way to make any Windows 7 instantly bluescreen, just by plugging a USB Flash drive... 😅 Now, to be fair, I was aware of a similar issue affecting Windows XP and Windows Vista with some *BSD images (on which FreeNAS is based). But I had yet to see a similar problem for Windows 7. So:
|
pbatard
changed the title
|
It's been quite a while since I ever saw the BSOD... Did you see if Refreshing the USB Stack Drivers resolves your BSOD issue? If your interested, I attached a txt file (to print as well if needed) with some simple (hopefully understandable) steps on how to do this. Refreshing-USB-Stack-Driver.txt Good Luck! ~Ibuprophen |
|
Well isn't that interesting...? Anyways, thank y'all for the replies however, the Refreshing USB Stack Driver did not help, I think I may have done it wrong but i proceed to step 2 and still didn't work. I also tried using Win32Disk and a crash happened with that software too. I also contacted Microsoft Support, of course they were clueless and I have no way of reporting this besides the forum. Thanks for the help but I'm not sure if there's anything more to do. Thoughts appreciated though! =) |
|
Do you have any driver conflicts within your Device Manager (via your Control Panel)? ~Ibuprophen |
|
Not seeing any at the moment. |
|
Did you try to obtain any updated drivers from the manufacturer of the USB/Chipset? ~Ibuprophen |
|
@ibuprophen1, I'd like to remind you that I too am seeing the BSOD on a vanilla Windows 7 system, with only USB 2.0 (hence using native Microsoft USB drivers), and, from what I suspect, the issue most likely has to do with Windows trying to parse a partition table that it doesn't know how to properly process, during a kernel-mode operation. This is unlikely to have anything to do with the USB stack. I've seen Windows (10 for that matter) declare an USB Flash Drive as completely inaccessible, no matter what you try (reboot, etc.) on account of a GPT table being set in a manner that Microsoft probably didn't expect (whereas Linux had no issue with the same drive, and, unlike Windows, could repartition/reformat it without any issue), so I have some doubts about the ability of Windows to properly handle all cases of partitioning. Instead, it would seem to me like Microsoft are patching their poor handling of partition tables as they go along, which would explain why Windows 7 crashes. At any rate, if you want to take the matter further up, and considering that we have established that this has nothing to do with Rufus, I will encourage you to do so on a Microsoft forum, as this is a pure Windows problem. As such, I will close this issue. |
|
@pbatard, understood! I too had seen this about a year ago +/- on the same Windows 7 build and had cleared it up within a few days involving both the GPT and MBR as well as an incompatible driver that Windows had defaulted to. My apologies for this and no further comments regarding this issue will be made. ~Ibuprophen |
|
@ibuprophen1 @pbatard Thank you for the help though. Really appreciate it! |
|
I just wanted to update @pbatard and @ibuprophen1 that after downgrading to FreeNAS' "STORAGE ONLY CONFIGURATIONS" or FreeNAS 11.1 works using Rufus. Sorry I didn't test this out earlier but that doesn't crash the system. |
|
I have the same issue and now when I put the usb stick into any windows 7 devices I get the BSOD and a win auto reboot. If I try to boot from the USB it flashes op something (too quick to read) and reboots!! Probably I have given up on Free NAS (I'll set up the PC on a Lan and use team viewer for remote access) BUT how the hell do I recover my USB stick since every time I insert it in win 7 device I get the BSOD?? |
|
ok so I have now partially answered my own question. USB recovered as follows: loaded old copy of Zorin (linux derivative) from another mem stick and the original stick was then readable (which tends to suggest it is a win 7 issue) |
Sorry if that sounds a bit harsh, but you shouldn't piggyback on an issue opened with regards to a specific application (Rufus) to ask support for software that is unrelated to that application (FreeNAS), especially if that issue is closed. If you have a query on how to configure a bootable thumb drive for FreeNAS, then please ask that question on the FreeNAS forums, as it will be A LOT more helpful for others who may have the same question if you do so there (as very few FreeNAS people are expected to check closed issues on unrelated software to find out if their bootable drive is configured properly). Thanks. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
While trying to put FreeNAS 11.2 BETA 2 on a SanDisk Cruzer Blad 8GB Flash Drive gives me a Blue Screen error called APC_INDEX_MISMATCH, while I have factory reset my system, the problem still persists on ONLY this iso. I've tested CentOS and XCP-ng on the same USB Drive. Below is a log tested on a different computer and the log has the following output. Note I couldn't retrive the log for the system it crashed. I've also taken the issue to Microsoft Community which can be found here to see if this issue can be resolved.
Any Thoughts?
Log
The text was updated successfully, but these errors were encountered: