I'm at a loss

Recommended settings gave 1.9 on vdimm I lowered to cpuz 1.8

Changed to 7 7 7 7 18 command 2T 1.82 Volts

Let's wait and see.

Thanks again to you and John.

:)

The first error is a STOP 0x124 - which usually points to a hardware/compatibility problem.
The next error is a STOP 0x1E in the intelppm.sys driver dated Mon Jul 13 19:19:25 2009 - this is the same version as I have on my system from the original Windows Update installation (I don't have a lot of faith in that).

I wonder if the intelppm driver is to blame - because of the previous STOP 0x124 error, which is usually reported to Windows by the processor.

Have you tried running the Windows 7 Upgrade Advisor to see if there's something incompatible that's interfering? It's available for free from here: http://www.microsoft.com/downloads/d...displaylang=en

If that doesn't fix it, then I'd suggest running Driver Verifier. I haven't had much success with STOP 0x124's and Driver Verifier - but this case is unusual enough that I'd think it'd be worth a try. Please follow these instructions when using it:

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.


So, 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 Startup Repair feature).


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"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then 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.


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.


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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

John,

I tried verifier.

That's what got me those BSODs so quickly and what you read is what the dump picked up.

Torrent has a point with the mem and the Intel driver could just make things worst.

Patriot Viper is a tough mem and harder to set on Bone trail Intel boards. So I downclocked a bit to CPUZ specs just to see what happens. If worst comes to worst, I can always use my OCZ XPM mem. It's clocked @1066

Slower but safer.

Well,

I just wanted to let you know that after many attemps and verification, it was the Video card that was faulty. I changed the card and the problems are gone. It was running at 70C idle not normal at all.

Anyways, this is just to show that debugging when it's material related is very tough.

Thanks to all for your help.