Could you help prevent crashes and BSOD/Page fault in nonpaged area?

[Arc]

Well, then the next thing will be to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Phrozt]

Sounds fun! I'll let you know the results.

 

[Phrozt]

Well I got one... (rename the attached to .dmp). Looks like it's caused by dne64x.sys. I looked this up and it didn't really surprised me it was cisco VPN related (deterministic network). I've seen problems w/cisco DNE stuff on work computers before.

It would also make sense that I'm seeing a correlation between network issues and a computer freeze at the exact same time.

I'll uninstall Deterministic Network Enhancer from the adapter, but I'm a bit worried that some part of it will stick around, as Cisco has practically become synonymous to malware for me lately. Any tips?

 

[Arc]

OK, have a look in registries as said in Laptop Management

Hopefully it will wipe Deterministic up from the system.

 

[Phrozt]

I'm working on that, but there's a question:
On step 8, it mentions: "The Original Equipment Manufacturer (OEM) enumerations of the dne2000.inf and dne2000.pnf files. The OEM enumeration .inf file is a file called oem<some numeric value\.inf. For example, files could be called oem2.inf and oem2.pnf."

I have oem0 - oem142, so how would I know which ones correlated to the dnf dll? (which, btw, mine was dne64x.sys, not dne2000.sys, and there were no .inf files for it).

Also, I was going fine all morning, but did have another lock up, even after killing DNE. No blue screen, just another lock up. I also just disabled verifier.exe, since it seems it got the only blue screen my system was going to throw.

 

[Arc]

I'm working on that, but there's a question:
On step 8, it mentions: "The Original Equipment Manufacturer (OEM) enumerations of the dne2000.inf and dne2000.pnf files. The OEM enumeration .inf file is a file called oem<some numeric value\.inf. For example, files could be called oem2.inf and oem2.pnf."

I have oem0 - oem142, so how would I know which ones correlated to the dnf dll? (which, btw, mine was dne64x.sys, not dne2000.sys, and there were no .inf files for it).

Search trhough the registry for deterministics ... delete all the items.

Also, I was going fine all morning, but did have another lock up, even after killing DNE. No blue screen, just another lock up. I also just disabled verifier.exe, since it seems it got the only blue screen my system was going to throw.

OK, use the computer normally now, let us know for any further BSOD.

 

[Phrozt]

It has frozen 3 times since the last post. Again, not a BSOD, but a full freeze.

I see several references to deterministic in regedit, but I don't know if I should delete them, and the post you referenced does not mention them.

 

[Arc]

If you think that the leftovers of deterministic is causing the issue, it will be the best to start afresh.
http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

Personally I dont use VPN, so I dont have very much experience about it.

 

[Phrozt]

I'm not so sure it's the DNE... it may be to the point that it's hardware...

 

[Arc]

Let the Driver Verifier to run for one more time?

 

[Phrozt]

I can, but it did freeze while the verifier ran and no dump was created. So whatever is causing the freeze isn't getting triggered and caught by verifier.

 

[Phrozt]

Lasted a day with verifier. Just froze again. No blue screen.. just the freeze and the audio loop.

 

[Phrozt]

I am now 100% certain the freezes are somehow connected to networking. My computer is hardwired to my router (it was to the old router as well). When my computer freezes, the entire internet goes down. The *second* I restart my computer, the internet goes back up. I was able to verify this because my laptop right next to it had a ping window up (ping 8.8.8.8 -t) and I saw this first hand.

Now I just need to figure out how the two are tied...

 

[Arc]

When you discovered the DNE factor associated with the BSODs, it was determined that the issue is networking related.

So it may be the software/driver controlling the network or (most probably not) the networking hardware.

To get rid of the software/hardware related issue in a single go, it will be the best for you to start afresh; specially when the underlying cause is not being caught.

Suggesting it again: http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

Think once again.

 

[Phrozt]

Unfortunately, I really don't have that kind of time, since this is a computer I work from. I have around 150 programs installed, development environments set up, years of updates installed, etc..

DNE was cleared out... there's got to be some other way to figure out what is causing this.

 

[ICIT2LOL]

So why not image the system and do the install and reimage??

 

[Phrozt]

I'm not familiar w/imaging.. but wouldn't that just put things back to the unstable configuration?

 

[ICIT2LOL]

Sorry about the late reply mate have been away. Well not necessarily because you reinstall the OS then get back the stuff you have imaged so if the problem was within the OS then it should be cleared..