0x0000003b BSoD

[Pyr0]

Ever since installing my Phenom II x4 840 into my Gigabyte MA770-ud3 I've been getting loads of BSoDs. If I revert back to my old Athlon x64 everything appears to work. This is the second CPU I have tried as I thought the first one was faulty but this one is doing the exact same as well.

I have updated my motherboards firmware to ensure it supports Phenom IIs (FKb).

I've attached the zipped file which contains both the Perfmon and windows_NT6BSOD_jcgriff2 files.

Running Windows 7 x64 OEM
OS age around about a year and hardware is mixed as self build. Mostly about a year as well apart from the CPU.

Any help would be very much appreciated thanks.

 

[Pyr0]

I should also have added that one of the BSoDs mentioned dxgkrnl.sys however dxdiag seems to find no problems. I've also attached this file in case it helps.

 

[JMH]

Ever since installing my Phenom II x4 840 into my Gigabyte MA770-ud3 I've been getting loads of BSoDs. If I revert back to my old Athlon x64 everything appears to work. This is the second CPU I have tried as I thought the first one was faulty but this one is doing the exact same as well.

I have updated my motherboards firmware to ensure it supports Phenom IIs (FKb).

I've attached the zipped file which contains both the Perfmon and windows_NT6BSOD_jcgriff2 files.

Running Windows 7 x64 OEM
OS age around about a year and hardware is mixed as self build. Mostly about a year as well apart from the CPU.

Any help would be very much appreciated thanks.

Hi Pyr0 and welcome

There appear to be at least 5 types of crashes but I think they are all pointing to hardware. Specifically I suspect the RAM. Please run the tests indicated below


1-Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.



2-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.

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.



3-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"
- 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).

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.

 

[Pyr0]

Thanks JMH

I will do as you asked and post some results tomorrowm, apart from the drive verifier, will let that run longer.

Any idea why it should only happen with a Phenom II installed rather than my trusty old Athlon though?

 

[Pyr0]

Ok System file check came back with no integrity violations. However I ran Memtest and ended up with 120 errors in one pass.

I have since replaced the Phenom II with my Athlon 64 and no errors in Memtest?

Although the CPU is AM3 my motherboard supports AM2+. I do currently have 2x PC2-5300 1GB installed into it. So why should the PC work fine with the Athlon installed and not the Phenom?