Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with NETIO.SYS causing BSOD #487

Open
GoogleCodeExporter opened this issue Jun 19, 2015 · 0 comments
Open

Conflict with NETIO.SYS causing BSOD #487

GoogleCodeExporter opened this issue Jun 19, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Install Windows 8 or 8.1 x64 onto system with 64GB RAM
2. Configure peer blocker 1.2 to auto start and browse web
3. To expedite issue enable Driver Verifier and launch peer blocker 

What is the expected output? What do you see instead?
Many BSOD's.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced 
memory at 0x%08lx. The memory could not be %s.
FAILURE_BUCKET_ID:  0xc9_7_pbfilter+2a30

What version of PeerBlock are you using? On what operating system? 32- or
64-bit? Windows ENT 8.1 x64


Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

I have attached all my minidumps since a clean rebuild a few months back, they 
should provide a good history during which I have updated BIOS, pcie bios for 
SSD and firmware for SATA SSD's. Also logged a ticket with some MVP's to review 
and let them draw same conclusion by themselves. You can view this thread and 
their analysis over here--> 
http://social.technet.microsoft.com/Forums/windows/en-US/db86aaa9-3741-4b69-940b
-df44280a48ed/kmodeexceptionnothandled-1e-netiosys-netiortlgetnextexpiredtimerwh
eelentryfe?forum=w8itprogeneral&prof=required

This has been causing me grief for over 16 months during which time I replace 
my entire 64GB of RAM for slower kit and at great expense. I hope it helps you 
guys out.

I would love if you could fix it but I am not counting on it especially anytime 
soon. Good luck and thank you for a fantastic product. 

Original issue reported on code.google.com by [email protected] on 10 Jul 2014 at 1:49

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant