Windows 10 Keeps Scanning and repairing F drive (local disk, no OS)

[Dracrushla]

Hi,
after running my memory at 85% for a few days now thanks to google chrome and a ton a tabs opened in it. I started getting problems on my pc. One was the system_service_exception (netio.sys) on startup of windows 10, the other is my motherboard kept giving out a continuous beeping sound, which indicated a memory error according to the Gigabyte support site and the last problem is that the scanning and repairing F dfrive loop.

After I reset my computer the beeping sound was stopped and I didn't get the system_service_exception (netio.sys) anymore. But I keep getting the the scanning and repairing F drive.

My questionis how do I Fix this?
Do I need to fix it or can I just ignore it?
C drive is windows 10
D drive is windows 7
E drive DVD RW
F Drive Local Disk, File system = Raw, Status =Healty( primary partition), capacity and free space 100MB

My specs are
Gigabyte 990fx UDA3
WD Black 1T
G Skill Ripjaws X. 1866
AMD FX 8350
Radeon R9 280x Sapphire Vapor X second hand
EVGa 1300 wats

 

[Colif]

I assume you are letting it finish??
Do you have two drives or just 3 partitions?

Maybe if you format F windows will ignore it. or delete the partition in drive management since its so big. I have 129mb of unallocated space on my 2tb drive, its not like I miss it.

download http://www.resplendence.com/whocrashed
run a scan and it will tell you all it can about netio.sys
paste here if its unclear

motherboards don't normally beep because they lonely

 

[Dracrushla]

I've let it finish quite a few times but it just keeps coming back.
I have 3 partitions of which D is the one I made, C which was always there and F who just popped up at some point.

I don't know if deleting the F is good idea. My windows 10 default partition software gives me
File system = Raw, Status =Healty( primary partition), capacity and free space 100MB
but my EaseUS Partition master shows that the F drive is
system reserved 57MB used and 42 unused, status = none, Type Primary.
http://www.easeus.com/partition-manager/ I use the free trail

These are the 3 crash reports I got, they were all from after I reset my pc,the ones from before don't seem to be here. Considering that these are all network/ wifi errors doesn't that mean that technically I won't get anymore netsio.sys crashes until I install some bad drivers?



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 3/25/2016 8:40:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032516-49484-01.dmp
This was probably caused by the following module: ae1200w764.sys (AE1200w764+0xA77CE)
Bugcheck code: 0xF7 (0x8080AF7F5FFE5F1F, 0xF80031726088, 0xFFFF07FFCE8D9F77, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\drivers\ae1200w764.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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: ae1200w764.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation DRIVER_OVERRAN_STACK_BUFFER



On Fri 3/25/2016 8:40:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ae1200w764.sys (AE1200w764+0xA77CE)
Bugcheck code: 0xF7 (0x8080AF7F5FFE5F1F, 0xF80031726088, 0xFFFF07FFCE8D9F77, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\drivers\ae1200w764.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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: ae1200w764.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation DRIVER_OVERRAN_STACK_BUFFER



On Wed 3/23/2016 3:46:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032316-37703-01.dmp
This was probably caused by the following module: ae1200w764.sys (AE1200w764+0xA77CE)
Bugcheck code: 0xF7 (0xFFFFD00132729060, 0xF800BABFD3B5, 0xFFFF07FF45402C4A, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\drivers\ae1200w764.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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: ae1200w764.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation DRIVER_OVERRAN_STACK_BUFFER

 

[Colif]

BSOD sure follow a theme, If anything new drivers might fix that error, but wait and see if it happens again, I guess. You can test the dump files now anyway.

Yeah, leave it alone:

Because the boot loader files are stored on it, Windows won’t boot properly if you delete this partition.

http://www.howtogeek.com/192772/what-is-the-system-reserved-partition-and-can-you-delete-it/

One solution I found was assign it a letter, let it do the scan and then remove the letter once its finished. It seems in Win 7 it liked running at start up and this fired it at that time.

 

[Dracrushla]

BSOD sure follow a theme, If anything new drivers might fix that error, but wait and see if it happens again, I guess. You can test the dump files now anyway.

Yeah, leave it alone:

Because the boot loader files are stored on it, Windows won’t boot properly if you delete this partition.

http://www.howtogeek.com/192772/what-is-the-system-reserved-partition-and-can-you-delete-it/

One solution I found was assign it a letter, let it do the scan and then remove the letter once its finished. It seems in Win 7 it liked running at start up and this fired it at that time.

So the F drive is important and I need it so the best option is to disable the Scanning and repairing function, right? I read somewhere that that is possible. And to avoid extra problems I should let scan once every month or few months. Does this seem like a solution to my problem. I found the respective commands.

1
down vote
Find command prompt and launch as administrator. run the command chkntfs /x c: (Replace c: with the appropriate drive letter) To undo this run chkntfs /d

http://superuser.com/questions/578523/how-to-cancel-windows-8-drive-repair

 

[Colif]

It looks like it should: https://support.microsoft.com/en-us/kb/160963 but I am not sure, I am trying to figure out what a volume dirty bit is. Is it something to be concerned about that your system reserved partition has one or can you just hide it and ignore it?

Given the purpose of the drive, I am not in a rush to do something that stops you booting altogether.