BSODs new Win732 on amd/nvidia chipset ck804 w fernandos drivers

Tried rebuilding a new case from old parts. Keep getting various crashes and also som appcrashes in ie9. have tried cleaning/reinstalling drivers in SAFE mode, sfc /scannow (fixed some files), and have updated all drivers/windows. been failing 4 days to fix it.


System Manufacturer/Model Number builtatfrys
OS Windows 7 hom prem sp1 x32
CPU amd 64 ada3800pbox
Motherboard ga-kn8pro-sli
Memory 4gb
Graphics Card(s) bfg 9400 gt 1gb No Sound Card
Monitor(s) Displays acer wide screen 6x9 res
Hard Drives wd 2000 jd caviar se
PSU antec trio 430
Case cheiftac dragon
Cooling amd out-of-box
Keyboard dell usb Mouse logitech wheel usb
Internet Speed dsl
Other Info fernando's windows 7 nforce4 drivers for ck804 Win7/Vista: Optimized nForce Driver Packs • nForcersHQ.com
in the attachments i put the minidump files in a zipfile and erased them from \windows sub before i could runi the griff report. they are in there with the griff and sys reports. hope thats ok. thanks for the help.

These crashes were caused by memory corruption probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+






Driver Verifer

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.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

zigzag

thanks for your assistance.

i had forgotten to list in my original post that i ran memtest as well as the western digital drive diag before posting, neither reported any problems.

when i started verifier as advised, the good news (i think) it only took about 1 minute to crash. however, windows could not load and the system is now trying to repair automatically.

once a restore point is put back, i guess whatever data verifier would have given would be gone. i will try to immediately rerun & do the delete settings but it seems thisis a dead end. i will post again with any verifier data if available.

there was nothing in the \windows\minidump folder but found several attached event logs from today, if usable.

bam12 said:

there was nothing in the \windows\minidump folder but found several attached event logs from today, if usable.

Absolutely nothing in event viewer but 17 unexpected shut down errors. We need the DMP files

Sorry, i wasnt sure if those reports would help. i will try rerunning verifier to obtain dumps but if it goes into repair mode again i do not know what to do to get the dumps - or any next step, except reinstall windows over again (i did get a nero image so i could recover my data).

I don't know if its important but immediately after repairing windows, device manager reinstalled my USB drivers. And, earlier, attempting to make the boot cd, my writer failed (a power stability fault). should I focus somehow on USB drivers as the problem?


thanks again zigzag for sharing your expertise with me.

zigzag

i am attaching two zipfiles. i got minidumps from 3 runs of verifier: the first (in time) crashed instantly;, the 2nd crashed after i got into ie9, disabled all addons, then browsed a couple websites; the third after i opened n360, ran a few of the maintenance procs (cleanup, monitor, and startup anayzer -when it died). the other zip file is lan diagnostic information when failing at first to copy the dumpfile zip over to this pc so i could post it.

bam12 said:

zigzag

i am attaching two zipfiles. i got minidumps from 3 runs of verifier: the first (in time) crashed instantly;, the 2nd crashed after i got into ie9, disabled all addons, then browsed a couple websites; the third after i opened n360, ran a few of the maintenance procs (cleanup, monitor, and startup anayzer -when it died). the other zip file is lan diagnostic information when failing at first to copy the dumpfile zip over to this pc so i could post it.

Driver verified and related to luafv.sys (MS virtualization driver) read here.
The deal with LUAFV.SYS - Of Filesystems And Other Demons - Site Home - MSDN Blogs

zigZag, thanks for finding thevirtualizationproblem for me. i went into thecontrol panel and discovered 2 drivers set wrong. soundman and one was a windows driver. disabled this. i setup the verifier again to include windows drivers also and caught another bsod, so there may be some other problem still. also, my browser keeps dropping out so i attach log files to show you, as there was no dumpfile produced.

thanks again for all your help. hopefully coming to an extermination point soon.

bam12 said:

zigZag, thanks for finding thevirtualizationproblem for me. i went into thecontrol panel and discovered 2 drivers set wrong. soundman and one was a windows driver. disabled this. i setup the verifier again to include windows drivers also and caught another bsod, so there may be some other problem still. also, my browser keeps dropping out so i attach log files to show you, as there was no dumpfile produced.

thanks again for all your help. hopefully coming to an extermination point soon.

This related to memory corruption. I am betting its Norton. I would remove and replace it with MSE

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows