BSOD Minidump

[liketearsinrain]

Could someone please take a look at the attached minidump file please and let me know what's causing the odd BSD please. I have tried to read them using KD from prompt but keep getting symbol errors (despite having loaded several different symbol packages now).

Many thanks.

 

[CarlTR6]

This one is a hardware problem, stop error 9C

STOP 0x0000009C: MACHINE_CHECK_EXCEPTION

Usual causes: Hardware error (similar to STOP 0x124)

Read this link and start going down the list. If you have questions, please ask. [2-Int] Stop 0x124 - what it means and what to try

The dump pointed to this driver: intelppm.sys which a processor driver.

While you are troubleshooting, please uninstall your AVG antivirus using this tool > Info > Tool (32bit) - Tool (64 bit) If you are using AVG Identity Protection, remove it with this tool > Info > Tool AVG has been know to cause BSOD's on some Win 7 systems. Once you get your system running smoothly, you can try it again.

Download and install Microsoft Security Essentials.

 

[liketearsinrain]

Carl,

Thanks for the super fast reply. That corresponds with the code that came up on the blue screen itself, but I thought the minidump would provide more specific information. I've pretty much tried most of those things already and had hoped the mini dump might have more info but guess the search continues...

It could well cooling in the PC, given it takes a while to build up... I have been folding pretty hardcore on it, and the case is Micro-ATX... it's not overclocked though (at the moment)...

Thanks again for speedy reply.

 

[CarlTR6]

You are welcome. Refresh your page; I added more.

I recommend that you enable Driver Verifier for at least 36 hours.

Using Driver Verifier to identify issues with Drivers

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/Windows 7 Startup Repair feature).

[FONT=&quot]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 "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. 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.

[/FONT] 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


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Do a CPU stress test as well, using Prime95.

Test your temps with Speedfan.

 

[CarlTR6]

See if you can update these two drivers:

AsUpIO.sys Sun Jul 05 22:21:38 2009 - ASUSTeK Computer Inc.-Support-

jraid.sys Fri Jun 26 03:13:37 2009 - RAID systems are notorious for not getting along with Win 7. See if you can update this driver. JMicron JR036X RAID Driver or JMicron JMB36X RAID Driver belongs to the software JMicron JR036X RAID Driver or JMicron JMB36X RAID Driver by JMicron Technology Corp.

 

[liketearsinrain]

I had enabled driver verifier, and it ran for about 30 hours (30 seems to be the magic number for some reason) before the PC bluescreened again. However, there was no .dmp file after that time - are the .dmps from driver verifier located in a different place possibly? I couldn't see a different location from the link which you provided.

I've also run the memx86 overnight from USB key and memory is okay after several hours of tests (about 5-6 passes if I recall), I haven't done Prime95 yet though so will give that a shot.

I did install CPUID Hardware monitor, but not totally sure if my temps were way outta whack. My CPU maxing around 135-145 F. NB124 F SB106 F. GPU (GTX295SLI on) @ 147-149 F.

I have uninstalled AVG per your instructions and with that removal tool.

I have installed Prime - can you recommend a specific test that will really burn this thing down?

 

[liketearsinrain]

Running the Prime torture test at the moment. Nice to see all cores at 100%.

Also running Folding@Home GPU as that has kept my work units fine without loss after reboots thus far and will push GPU to the max pretty much.

Can't find newer update for that RAID driver but since I don't use RAID I may just disable that controller.

Still looking for that Asus sys update...

 

[CarlTR6]

Thanks for the followup. The Asus driver may not be a problem. You can disable the jraid.sys by renaming it to jraid.bak.

The dump files from Driver Verifier should be in the same location as you other dump files.

 

[liketearsinrain]

Hi,

Just wanted to give an update on progress - had the PC running pretty much 3 days solid now without a reboot and running SMP 4 core folding, GPU folding the whole time and not so much as a blip.

The key seems to have been uninstalling the AVG client through that link you provided (I hadn't deactivated the RAID since not used/wanted to check other stability).

Really put the PC through its paces these last couple of days though, good that it seems bullet proof now <fingers crossed>...

Thanks for your help.

 

[CarlTR6]

Excellent news; the kind we like to hear! AVG will definitely cause some systems to blue screen. That is a simple fix. I hope your problems have gone and that you have smooth computing.