BSOD with new system build, any help appreciated!

[barkmann]

Hi there,

I built a new system last week and ever since have been getting random bsods, one every day or so. I have read the forum and tried some of the items suggested - memtest seems ok, system check and chkdsk are fine. Attached are my diag files, any help gratefully received!

- Windows 7 Home Premium x64
- the original installed OS on the system? yes, clean install
- an OEM or full retail version? OEM
- What is the age of system (hardware)? brand new, all of it.
- What is the age of OS installation (have you re-installed the OS?) age is a few days, clean install on new equipment


cheers, Chris

 

[zigzag3143]

Hi there,

I built a new system last week and ever since have been getting random bsods, one every day or so. I have read the forum and tried some of the items suggested - memtest seems ok, system check and chkdsk are fine. Attached are my diag files, any help gratefully received!

- Windows 7 Home Premium x64
- the original installed OS on the system? yes, clean install
- an OEM or full retail version? OEM
- What is the age of system (hardware)? brand new, all of it.
- What is the age of OS installation (have you re-installed the OS?) age is a few days, clean install on new equipment


cheers, Chris

ASACPI.SYS A huge problem that almost always caused bsod's

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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).

That is probably the only problem but we cant tell till it is removed




Ken J

 

[barkmann]

thanks for the info - I ran the asacpi.sys update prior to running the diag process and I checked that the file in system32 is the 2009 version - should it have updated somewhere else but didn't, perhaps?

cheers Chris

 

[barkmann]

another BSOD this morning unfortunately. Attached is the diag files - any help appreciated!

cheers Chris

 

[Jonathan_King]

Hello,

I suggest that you run some hardware tests. Start out with RAM: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I also suspect your hard drive may be at fault. Can you install Windows on a partition on the WD drive, and see what happens?

...Summary of the dumps

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 23 16:35:03.638 2010 (UTC - 5:00)
System Uptime: 0 days 0:57:51.652
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 21:55:40.364 2010 (UTC - 5:00)
System Uptime: 0 days 5:08:38.268
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+114 )
PROCESS_NAME:  MsMpEng.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+114
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[barkmann]

thanks to all those who responded with suggestions - in the end I narrowed the issue down to a faulty motherboard - once replaced, the system is nice and stable - thank goodness!

cheers Chris

 

[Jonathan_King]

Thanks for the report!

I'm glad if our suggestions helped get you on your way, too bad we couldn't have figured that out right away.

At least it's working now...let us know if you need anything else!