BSOD - Constant reboots on new system

[RichTJ99]

Hi,

I just installed Win 7 64 Professional retail on a new OCZ SSD. I have been having issues with the system rebooting & I was convinced it was the old SSD. Since i have come back to my PC twice within 12 hours to find it had "recovered from a serious error", I am wondering if its something else (ram)?

Any ideas what it could be?

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64 bit
- the original installed OS on the system? Windows 7 Pro 64
- an OEM or full retail version? Retail
- What is the age of system (hardware)? Brand new build
- What is the age of OS installation (have you re-installed the OS?) 24 hours

I7 960 processor
12 gigs ram (I bought a 6gig pack twice by mistake)
Asus P6X58D Premium mobo
OCZ Agility2 60 gig drive
ATI HD5XXX video card.

Thanks,
Rich

 

[usasma]

First, please visit the Asus support website and download/install the latest version of the ATK0110 ACPI Utility driver - it'll either be under the ATK or the Utility sections on the downloads page. The version on your system now (from 2005) is a known BSOD cause in Windows 7. Then see if you continue to get BSOD's.

One of the errors is a STOP 0x109 - and it's commonly associated with memory problems (RAM, CPU, mobo, video memory). As such I'd start with these free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

The second error is a STOP 0x3B - and is commonly associated with driver issues - so I'd suggest running Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 12:35:09.641 2010 (UTC - 4:00)
System Uptime: 0 days 2:56:38.719
BugCheck 109, {a3a039d8a09108e4, 0, 584cde1deb700492, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 09:36:10.637 2010 (UTC - 4:00)
System Uptime: 0 days 0:25:51.715
BugCheck 3B, {c0000005, fffff8000285d414, fffff8800a762e00, 0}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerStreamContextInternal+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mscorsvw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[RichTJ99]

Hi,

I am starting at the top of your list: ATK0110 ACPI -- Your correct, mine was very out of date (April 2004), it is now updated using 7/16/2009 as the dated version (driver version 1043.6.0.0). It was not a driver that was listed on the Asus support site.

I will be running the memtest overnight tonight. I hope the 12 gigs wont be an issue.

As far as driver verifier goes, I have no problem chancing that my system wont recover. I have reinstalled this system a number of times over the last few weeks.

I have been wondering if I should remove 6 gigs of ram & see if that makes a difference.

I will keep you updated as I try things out.

THanks,
Rich

 

[usasma]

I've got 12 gB of RAM also - so running Memtest overnight is a requirement.
Make sure that it's completed 3 passes (when I did it I only got 5 passes overnight)

It's my opinion that 6gB of the RAM is wasted (I've monitored the RAM usage on my system) - but since you've already purchased it you might as well leave it in. When I build the wife's next system, she'll get 6 gB of my RAM. There's just nothing that I do that requires all that memory.

Good luck!

 

[RichTJ99]

So far i just updated that driver. So far the machine hasnt rebooted which is impressive so far. I have a SSD (60gb) so storage is at a premium. I changed the hibernation to off & I changed the page file from 12gb to 2 gb (I figure that it wont go over 14gb of ram).

I think the splitting the ram is a good idea. I would give it to a friend but I want to make sure it works so I dont get calls about problems down the line.

 

[usasma]

I'd suggest leaving the pagefile at Windows Managed - that way it'll be dynamic in size and you won't have to worry about it.

 

[RichTJ99]

I am not sure if my system rebooted. I think i turned off error notifications so I am not 100% sure.

I did buy an additional 6 gigs of ram for another persons PC. I may end up swaping that memory in just to see if I still have problems.

EDIT: I removed 8 gigs of ram & am testing 2 gigs at a time. So far so good.

 

[RichTJ99]

So I just started running memtest86 v4.0 & it already picked up 65,000+ errors within 4 minutes. The list keeps growing & growing.

I am guessing something is wrong with version 4.0.

Do you have another suggestion on how to test 12gb of ram (6x2gb sticks)?

 

[usasma]

I'm guessing that there's a problem with at least one stick of your RAM.

Around paragraph 6 or 7 is the technique for ruling out sticks and slots in your system:
Memory Diagnostics (read the details at the link)

 

[RichTJ99]

Well I noticed that my ram wasnt running at the 1600mhz DDR 3 speed (closer to 1066) so I changed that in the bios & I am rerunning the tests.

What I cant figure out for sure is if I get an error message saying the error was at meg 5980
5981
5982
to
5999

Does that mean the error came from stick 3 (the being meg roughly 4000-6000)?

For some other reason, my system wont boot at all if there is no ram in slots 1,2,3 & it makes it hard to just test slots 4,5,6 with no ram in 1,2,3. I was hoping to test the slots to see if that was the issue.

The results at the slower speed were I thought I found my bad stick & when I tried it again, it gave no errors for the first few passes. I will have to run in over night.

If I have 6 sticks of ram, is it recommended to test each stick over night during a 6 day period?

Thanks,
Rich

 

[usasma]

I recommend that you test all sticks together.
If that fails, then you test each stick separately in the same slot.
Once you find a good stick, then you can test all of the slots with that one good stick.

If the mobo requires other slots to be full, just test each one as you add another stick
Fill slot 1 with a good stick and test
Then fill slot 2 with a good stick and test
Then fill slot 3 with a good stick and test
Then you can move onto the other slots with other, known good sticks.

 

[RichTJ99]

Well, I am RMA'ing all the ram. 6 gigs seems to work at the 1066mhz speed (vs the 1600mhz). When i set it for hte rated speed, i get freezes after 10 minutes. At the under rated speed, the system works fine. The other 6 gigs seems to be a problem.

Fortunately, I have a second P6T mobo that takes the same ram so I can do some testing when the new ram comes. I can also test my current mobo with the new ram as well (different brand).

 

[usasma]

Thanks for letting us know!

 

[RichTJ99]

I am hoping that the new ram solves the problem otherwise its either the board, or i guess the CPU?

 

[usasma]

It's hard to say with the P6 series of boards.
I have 2 problems with mine:
- an issue with BSOD's when trying to sleep/hibernate
- an issue with the CPU fan controller

Either one of these errors can resemble CPU or motherboard issues - so then it's just your best guess.
Good luck!