Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD every 2 Hours, Clean Install Pro X64


26 Oct 2009   #1

Windows 7 Pro (x64)
 
 
BSOD every 2 Hours, Clean Install Pro X64

I just did a fresh installed Windows 7 (x64) yesterday, got all the updates downloaded and no problems until last night when I heard the system restart. There was a message that the system had recovered from a error. As the day has progressed it seems to happen every two hours give or take, I cant figure out what the issue is. I found the .dmp files, it had made one every time, but i do not how to get it on here to be able to read.

Any help would be greatly appreciated, Joey


*This is what it says in the event viewer, same thing everytime.
Error 10/26/2009 4:18:23 PM SNMP 1500 None
Error 10/26/2009 4:18:19 PM BugCheck 1001 None
Error 10/26/2009 4:18:16 PM Eventlog 1101 Event processing
Critical 10/26/2009 4:18:05 PM Kernel-Power 41 (63)


My System SpecsSystem Spec
.

26 Oct 2009   #2

Win7x64
 
 

Quote   Quote: Originally Posted by Exclamation View Post
I found the .dmp files, it had made one every time, but i do not how to get it on here to be able to read.
Copy the contents of the \Windows\Minidump folder to another location on your machine. Zip up that copy. Upload the zip archive here using the "paperclip" (attachment) link in a new post window.
My System SpecsSystem Spec
26 Oct 2009   #3

Windows 7 Pro (x64)
 
 
Here is the Mini dump folder

Here's the folder
My System SpecsSystem Spec
.


26 Oct 2009   #4

Win7x64
 
 

Bunch of different exotic crashes: some critical process terminations (CSRSS, winint), some APC errors...

I'd be very suprised if this turned out to be anything but a hardware-layer problem. Suggestions:

1) Don't overclock anything.
2) Ensure adequate cooling.
3) Make sure the BIOS is up to date.
4) Run memory diagnostics (MDSCHED, memtest86).
My System SpecsSystem Spec
26 Oct 2009   #5

Windows 7 Pro (x64)
 
 

Thanks for the help. Let me know if there is anything else i can try or do that may help.

1.) I do not overclock so that's not a worry
2.) Case is an Antec NSK 4000 With two 120mm fans front and back, CPU cooling fan is an Asus Triton 85 W/ 120mm fan. Cooling has never been an issue w/ Vista Ultimate x64
3.) I checked on the Asus website and i do have the up to date BIOS installed already
4.) I just did the Memory test and it said it did not find any problems...
My System SpecsSystem Spec
26 Oct 2009   #6

Win7x64
 
 

Quote   Quote: Originally Posted by Exclamation View Post
Thanks for the help. Let me know if there is anything else i can try or do that may help.

1.) I do not overclock so that's not a worry
2.) Case is an Antec NSK 4000 With two 120mm fans front and back, CPU cooling fan is an Asus Triton 85 W/ 120mm fan. Cooling has never been an issue w/ Vista Ultimate x64
3.) I checked on the Asus website and i do have the up to date BIOS installed already
4.) I just did the Memory test and it said it did not find any problems...
In that case, I'd suggest another "vanilla" reinstall of the OS - don't install any apps, games, updates... nothing at all that doesn't come from the Windows disc. If you can use it without crashes, start installing other things slowly. Updates first. Run it for a few hours in between major additions so that you can get a feel for what may have caused it, should the problems resurface.

Otherwise, if the vanilla install continues to BSOD with CSRSS & wininit crashes, the hardware is broken.
My System SpecsSystem Spec
27 Oct 2009   #7

Windows 7 Pro (x64)
 
 

I had a similar thought but kinda backwards, i started uninstalling the last programs that i had installed. Regardless it did not help because it just happened again.

I included the .dmp along with screen shots of the event viewer and the detailed event windows. I tried to include everything that may help in tracking down the culprit before jumping on the re-install wagon.

Here is what the message said after the re-start.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8006471060
BCP3: FFFFFA8006471340
BCP4: FFFFF80002BDB240
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102609-36254-01.dmp
C:\Users\J!V\AppData\Local\Temp\WER-57361-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My System SpecsSystem Spec
27 Oct 2009   #8

Win7x64
 
 

Every time the stop code is an 0xF4, you can take it for granted that CSRSS crashed. On a new install, that is almost always a sign of underlying hardware problems.

In "official" terminology:

Bugcheck 0xF4 = CRITICAL_OBJECT_TERMINATION

"A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function."


Since this crash is entirely similar to many of the previous ones, I think it's safe to conclude that the uninstalling effort you've undertaken has not hit upon the culprit.

As far as the events you attached (as screenshots):

41: Just a side-effect of the fact that the machine woke up and noticed that it had previously crashed.
1001: Reporting the crash, in this instance a stop 0xF4.
1101: Safe to ignore in this case,
1500: Curious, but almost certainly unrelated to the BSODs.
6008: "Is it OK to tell MS about your problems? Yes/No"

None of them are causal. They're all either unrelated or just attempts to tell you that your machine just BSODded, in case you didn't notice.
My System SpecsSystem Spec
27 Oct 2009   #9
Microsoft MVP

 
 

FWIW, this outdated driver will frequently cause BSOD's in Windows 7:
Quote:
ASACPI.sys Sun Mar 27 22:30:36 2005
Asus has updated Windows 7 drivers for your system if this is applicable in your case - either by installing the Windows 7 version of the Asus AISuite or Asus PCProbe
My System SpecsSystem Spec
27 Oct 2009   #10

Windows 7 Pro (x64)
 
 

Quote   Quote: Originally Posted by usasma View Post
FWIW, this outdated driver will frequently cause BSOD's in Windows 7:
Quote:
ASACPI.sys Sun Mar 27 22:30:36 2005
Asus has updated Windows 7 drivers for your system if this is applicable in your case - either by installing the Windows 7 version of the Asus AISuite or Asus PCProbe

Can you tell me what this driver applies to and where i could go about finding the Windows 7 version? I'm not sure what it's for. I appreciate the point in the right direction.
My System SpecsSystem Spec
Reply

 BSOD every 2 Hours, Clean Install Pro X64




Thread Tools



Similar help and support threads for2: BSOD every 2 Hours, Clean Install Pro X64
Thread Forum
BSOD following clean install BSOD Help and Support
BSoD hours after clean Win7 install, rig is "seasonally unstable" BSOD Help and Support
BSOD 41(63), Second clean install BSOD Help and Support
BSOD - After clean install BSOD Help and Support
Clean Install BSOD BSOD Help and Support
BSOD even after clean install BSOD Help and Support
Random BSOD after a few Hours of a fresh install BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:14 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33