BSOD with windows startup

Aaron Freed · 02 Dec 2009

I hope I get all the etiquette right (newbie)...

I keep getting BSOD with windows 7 64 bit home with all startups.

I have tried reloading windows, checked ram with memtest and burn in software, checked the CPU, etc. All temperatures low to normal.

I have included last 6 crashes zipped from minidump... If anyone could take a look
it would be much appreciated.

All computer components listed in profile

Thanks

Aaron

Lordbob75 · 02 Dec 2009

Seems to be all driver and memory errors. Take out all but one stick of RAM and try that.

~Lordbob

usasma · 02 Dec 2009

The 2005 version of this driver frequently causes issues in Windows 7:
ASACPI.sys Sun Mar 27 22:30:36 2005
It's usually installed automatically when you install Windows 7 (it's stored in the Windows Update driver repository).

I would suggest visiting the Asus website for your motherboard ( ASUSTeK Computer Inc.-Support- download_item_mkt )and downloading and installing the latest version of the Asus PCProbe for Windows 7 64 bit from the Utilities section.

My only other suggestion at this time would be MemTest - but you've stated that you've run it already. As long as you've done a minimum of 3 complete passes then all should be well.

Should the BSOD's recur, please post back and we'll have a shot at running Driver Verifier to see if we can coax the system to spit out the name of the offending driver.

Here's the summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 27 12:08:14.007 2009 (GMT-5)
System Uptime: 0 days 0:00:25.708
BugCheck F4, {3, fffffa8006df2b30, fffffa8006df2e10, fffff80002bc7240}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 28 12:16:42.432 2009 (GMT-5)
System Uptime: 0 days 0:00:53.759
BugCheck 1, {7741ff2a, 0, fffe, fffff88003a4dca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 28 12:14:17.657 2009 (GMT-5)
System Uptime: 0 days 0:00:49.984
BugCheck 1A, {5003, fffff70001080000, 384, 476000008e8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+297b1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  runonce.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 29 11:12:55.345 2009 (GMT-5)
System Uptime: 0 days 1:27:42.260
BugCheck 50, {fffffac0076724b0, 0, fffff80002a0841d, 5}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+36d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 18:51:20.015 2009 (GMT-5)
System Uptime: 0 days 7:52:14.341
BugCheck 1A, {5003, fffff70001080000, 213c, 2177000042f6}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+297b1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec  2 14:18:48.030 2009 (GMT-5)
System Uptime: 0 days 0:00:40.731
BugCheck 50, {fffff88045376bd0, 0, fffff800028dd324, 5}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

Aaron Freed · 03 Dec 2009

Thank you guys for all the work and help...
I will try all suggestions one at a time then get back to you with the results.

I really appreciate the help. Microsoft support was useless for me... they should hire you guys as trouble shooters.

Aaron

torrentg · 03 Dec 2009

usasma said:

ASACPI.sys Sun Mar 27 22:30:36 2005
It's usually installed automatically when you install Windows 7 (it's stored in the Windows Update driver repository).

Wow, based on all the bsod from this, seems Microsoft dropped the ball on this one by including it. It appears so many times in crash dumps and I always point it out as being potentially troublesome, based on the date.

usasma · 03 Dec 2009

FWIW - it doesn't always cause BSOD's. But it does this frequently enough that it's a known problem. It was updated in 2006 and then again in 2007 - and most recently it was updated twice in 2009 (once for Vista and once for Win7).

Additionally, it's a utility that functions on a very low level in the OS (like an antivirus or firewall) - so the chance of experiencing compatibility issues is significant.

FYI - my Asus P6T Deluxe has the 2005 version installed on it (it came when I installed the RTM on it) - and I haven't experienced any issues with it. So it's not a 100% sure thing that it will result in a BSOD.