I've been searching everywhere to see if I could find a solution to my problem and nothing worked. I've tried memtest, chkdsk, updating drivers, relocating RAM to different slots, etc...I have no clue beyond this point, however, I still find it odd that the BSOD occurs only when I'm installing a new game with Steam (Re-installing did not help). Perhaps I missed an important driver to update, something was corrupted, or even kernel issues. Either way, I have not the slightest idea of how to fix the BSOD. This is my last attempt before I will do a clean install of Windows, I hope someone will help me save some time.
Heres a few information about my BSOD;
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
OS Version: 6_1_7601
Service Pack: 1_0
Ah, this is very interesting. First time I saw this program...Here are the selected drives that were red; ndis.sys, ntkrnlpa.exe, nvmf6232.sys. Odd, I uninstalled the NVIDIA networking driver, not sure why it's still there. What can I do about the other two? Also, one DMP didn't have the ntkrnlpa error, instead there was an error with ntoskrnl.exe.
ndis.sys is part of your network driver. Try updating your network driver. ntkrnlpa.exe has to do with your power settings (sleep/hibernate). Perhaps your motherboard doesn't handle S3 or S4 properly or again, possibly a driver like the HAL. Try changinging sleep/power settings in the bios.
Unfortunately, this is one of those hard to nail down problems, but now that you know which modules are causing problems, you can try googling for answers or hopefully some others will post possible solutions.
After tinkering around, the issue has been solved...At least that I know if. I am safely installing games with not more crashes.
Thankfully the fix was easy and fast, all I did was re-install my nvidia network drive. Thank you for helping me isolate the problem.
Well, IRQL errors are either RAM or driver related problem. Memtest tends to eliminate RAM...
ndis.sys and ntkrnlpa.exe are system drivers, and almost certainly NOT the source of the crash, just the module that got hammered as the result of memory corruption that resulted. Nvmf6232.sys is the NVIDIA networking driver, and may be the root cause of the issue, especially if you thought you uninstalled it...
For now, moniter for reoccurance. Anything RAM related will come and go until the root problem is solved.
Well...I re-installed my nvidia network driver and that fixed the issue for a few days....Now it's happening again. this is really frustrating. What could cause my network to trip up and bsod like this? Another clue; when I run a minecraft server for a few hours the bsod occurs, along with the same problem while installing games on steam. I am at a loss.
Next question: With the NVIDIA networking driver uninstalled, did you get the BSOD?
I'm trying to determine if the NVIDIA driver is at fault, or if that driver crashed through random chance [with memory corruption, just about anything could end up crashing].
Another step in the short term would be to run with a single stick of RAM. Memtest is good at catching hard memory failures, less so if the error comes and goes [occasionally stuck bit, for instance]. If the error occurs, try a different stick [in a different DIMM, just for kicks]. If it occurs on two sticks of RAM, almost certainly software.
Running Prime95's blend test [watch temps!] would be a secondary way to test memory subsystem. Might just have a mobo that needs a bit more juice then normal for stability. Prime does a better job at stressing the entire memory subsystem then memtest does...
If all else fails, you can try a format. Won't solve a HW problem, but if something did mess up SW side...
It's definitely the nvidia network ethernet driver. Just re-installed the driver and I'm able to do the following stated above with out crashing. Now this is where it gets tricky..Over time, the problem will occur again just like before. What could cause this to happen after a re-install of the driver?
Question: Do you have one ethernet output port on your mobo, or two? Most modern mobo's have two, each with their own driver. You could potentially use the other one, and disable the NVIDIA one, which should solve the issue.
Hmm...I don't like the DRIVER_VERIFIER_VIOLATION_DETECTED BSOD, especially since its coming from the ATI driver.
Whats worrying me is that so many low level things are breaking [NVIDIA Networking driver, Intel CPU Driver, ATI Driver, ATA Bus Driver] that its hard to really narrow down where the problem is. For now, use a different version of the ATI driver, just to be safe.
Also, I know you ran one already, but run another memtest86, just to be safe.