Frequent BSODs - W7 64-bit

pongolo

New member
Local time
4:32 PM
Messages
6
This is a custom build computer (built last year) with an full retail installation of W7 Professional 64 bit with SP1 installed. The OS is the only one that has ever been installed on this PC. I had an issue late last year (http://www.sevenforums.com/crashes-debugging/130318-help-dump-file.html and replaced the file as instructed. The computer is having issues again with many BSOD (almost daily when the PC is used).

Attached is the Windows_NT6_BSOD_jcgriff2 zip file as requested for BSOD analysis.

Appreciate any help!

Thanks,
Freddie
 

My Computer My Computer

At a glance

W7 Professional 64 bit
OS
W7 Professional 64 bit
This is a custom build computer (built last year) with an full retail installation of W7 Professional 64 bit with SP1 installed. The OS is the only one that has ever been installed on this PC. I had an issue late last year (http://www.sevenforums.com/crashes-debugging/130318-help-dump-file.html and replaced the file as instructed. The computer is having issues again with many BSOD (almost daily when the PC is used).

Attached is the Windows_NT6_BSOD_jcgriff2 zip file as requested for BSOD analysis.

Appreciate any help!

Thanks,
Freddie

Hi Freddie.



First major problem is asacpi.sys


1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

Second problem that most of the Crashes point to is memory mangement.

Please run these two tests


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.



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.
 

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Zigzag3143,

Thanks for your quick reply!

I checked the ASACPI.SYS file and it is dated Dec 2010. I did not update it as it is newer than the one on the ASUS website.

I ran MEMTEST86 for two passes before your reply and it did not find any problems with the memory. I will run it again today while I'm at work. Should be quite a few passes before I come home and then afterwards I will run the driver verifier.

Did you spot any other potential issues on the log files?

Thanks,
Freddie
 

My Computer My Computer

At a glance

W7 Professional 64 bit
OS
W7 Professional 64 bit
Zigzag3143,

After my post above, I ran Memtest86+ and got a bunch of errors. I then reran Memtest86 and got even more errors. I researched the memory issue a little more and my problems stem from an issue AMD Phenom II CPUs have with DDR3 1600 memory (I'm not sure if it's only limited to the GSkill memory brand). An entry in the GSkill forum website (AMD CPU + G.Skill DDR3-1600 - GSKILL TECH FORUM) states to set the DRAM frequency to DDR3-1333 instead of DDR3-1600 along with a few other settings.

I changed the DRAM frequency in the BIOS and ran 4 passes of Memtest86 without a single error. I'm also running Memtest86+ and so far have no errors with pass #1 almost complete.

I'll post back if the BSOD continue after these changes but I'm hopeful this was the source of the frequent BSODs.

Thanks,
Freddie
 

My Computer My Computer

At a glance

W7 Professional 64 bit
OS
W7 Professional 64 bit
Back
Top