Recent content by nyknicks8

Thanks jmv2009 and richc46. I'll try to find updates for those drivers you listed. As a last resort I'll do a clean boot and working from there enabling drivers and services one at a time.

Unfortunately another BSOD even after I disabled the tv tuner in device manager. It is another 0x9f. Please let me know if the minidump provides any additional details. I am at a loss as to what is causing this. Any other ideas? Thanks again for your help.

Thanks. I will disable the tv tuner in device manager. This is a pretty frustrating problem. I don't quite recall having so much trouble solving an issue like this one. I wish the BSOD would occur more frequently making it easier to troubleshoot.

Unfortunately the original BSOD occurred again. I have attached the minidump. I actually put in my replacement motherboard a few days back. So it seems to be unrelated to any motherboard components. I would appreciate if anyone can tell me if this minidump provides any new clues. I'm thinking...

Just to update. I reinstalled AI Suite (Asus software) and ran verifier again and it did not BSOD. So therefore it was powerdvd that was causing the BSOD with verifier running. Now hopefully it was also the cause of the intermittent BSOD I got with hal.dll.

That did it! I uninstalled powerdvd and Asus software suite and now with verifier enabled there isn't a BSOD on startup. Now the only thing is that even after I uninstalled the asus software, the driver Asupio.sys is still active. I ended up renaming it to .bak. Searching online it seems to be...

Yes i am going not uninstall powerdvd and the asus software. I'm doing a system image backup just in case these uninstalls do not solve the problem I can reinstall windows 8 and run verifier with no programs installed.

It BSOD w/ verifier with all drivers enabled. Selectively disabling drivers did not do the trick and it would still BSOD until I disabled ntoskrnl.exe from being verified in verifier then it would not BSOD. Upgrade assistant came out fine. It just said Secure Boot isn't compatible with my PC.

Okay so now there is only one driver that is causing the BSOD on startup with driver verification enabled and its ntoskrnl.exe. If I disable that, there's no BSOD with driver verification enabled. So what could be the cause of this? Edit1: I wanted to clarify that all other drivers were enabled...

I disabled all non-essential devices in device manager, and with driver verifier enabled it still gave the same BSOD. I'll now try selectively disabling driver verification.

Even with the verifier enabled, it does not BSOD in safe mode. Once in safe mode I disable the verifier and can restart the computer normally. Now with the original BSOD w/ hal.dll, that occurs intermittently and about once in every few days.

The problem th running it for 36 hours is that immediately upon startup I get a blue screen with the mini dump I last uploaded. It occurs every time I startup with driver verifier enabled. I would have to go into safe mode to disable driver verifier in order to get back to the desktop.

I didn't know different methods to read dumps given different results. I'm not familiar with BSOD and how to read them, but what do you suggest I try next? Do you still think its a hardware issue based on these new BSOD? Should I still try to run driver verifier adding on one driver at a time to...

What do you mean? I used bluescreenview and it showed it as volmgrx.sys. Anything else I should do?

I've ran the driver verifier. And I'm constantly blue screening on volmgrx.sys upon every startup. Does this narrow down the issue any bit? I've attached the minidump. Thanks for your help. Here are the details: ================================================== Dump File ...