Well, I went searchin for new drivers. Could not find new replacement for nvm62x64.sys or pcouffin.sys. removed RTCore64.sys and updated Razerlow. tried downloading new drivers for motherboard and lost network access completely. I'll wait and see and keep you posted. Thx for the help. See you in the forums.....
Well son of a ........ Woke up this a.m. and it had crashed overnite. i thought i had it fixed so i was doing a backup on my backup drive. not even sure if the backup completed. I'm including another SF dump rar with only the last 2 crashed: 1 before I found you fine gentlemen, and the 1 last nite after i change a couple of drivers. But there are no newer drivers for my mobo. What if that's the problem?
Please enable driver verifier:
Using Driver Verifier to identify issues with Drivers
Have you done memtest86 with at least 7 passess?
Code:BugCheck 4E, {99, 5d35c, 2, 5d35a} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- BugCheck 4E, {7, e17a, e14e, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16dc6 ) Followup: MachineOwner ---------
Memory corruption can also be caused by a low voltage situation on the memory controller. Very common when upgrading to Windows 7.
i did the Memtest with 7 passes and found 0 errors. can i do the verifier and ONLY select the couple of drivers I suspect? i dont want 2 get into a situation where i can even get back into the system. Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
My knees are knocking at the thought of it.
yes you can do that, please read the instruction. You can do system restore in case you can't get back into system (Safe mode)
~Tuan
Another option might be hard drive issues. I recently resolved some issues that looked like mem issues and yet it was actually a combination of some OS corruption and some lost allocated mem on hard drives. Trying running checkdisk. Also run "sfc /scannow" from an elevated command prompt.
I agree with running checkdisk.
Post your results.CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Read this for more in depth hard drive checking.
HD Diagnostic
Quote