• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Occasional Vista BSOD at boot

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
It is interesting that our motherboards are both based upon the same chipset with about the same processor and memory along with the same OS and we both have the same issue.
 
Yeah, I haven't been able to find anyone else on the many times I've searched that has the same problem that occurs under the same conditions.
 
Well my bios does not have a setting for the timings that I could just find (I thought I had set it by hand, at least the command rate) and the speed is set to auto. Cpuz shows my memory running at 4-4-4-12 with 2T command rate.

There was also no crash log from todays crash.
 
Grr...I completely forgot i had to hit CTRL-F1 to get to the memory timings. They are now set to the SPD auto of 5-5-5-18 for my Crucial Memory.
 
I just found this comment on newegg's site for the memory I have:
Cons: Many sporadic blue screens along with few second system ""hangs"" when PC wakes up from sleep to memory. No problems when swapping with some OCZ memory. I just got off the phone with Crucial and there is a known problem with this chip revision and Intel's P35 chipsets on various brands of motherboards. They are working on the issue as we speak and told there should be a new revision out in a few weeks. They want me to call back to see if the new revision is available after July 1st and will swap out my memory without a problem. Hopefully they get it resolved with the popularity of P35 boards. If you've got the same problem as my motherboard, save the trouble of returns to the store you bought it from since you won't likely get info on what revision they will be sending you and end up with the same frustrations.
 
Well it wasn't the memory settings at 4-4-4-12 since my computer Blue screened tonight with it using the SPD settings.
 
Ugh..3 BSODS within 20 minutes, I think this is a new record and I don't knwo what is going wrong since dump files are not being created.
 
That is the only ram I have that I can use. I wish I could get a minidump file so that I could attempt to find out what driver (if any) is causing the problem.
 
Well, I have ntfs.sys often cited as the culprit but I've gotten this with 3 different hard drives, the component ntfs.sys usually points to so nothing's for certain even from the minidump files.

It hasn't happened again since I reset my timings though.
 
I think I may know why I don't get minidump files. I didn't have a pagefile on my windows drive (C🙂. I had that one turned off and had the page file on on another drive.
 
I have now gone 6 days without a BSOD at boot by going to the lastest released bios and hand setting the timings for my memory and upping the voltage to 2.1 while running at 4-4-4-12. Hopefully my machine will run stable now.
 
you prob have 2 maybe 4 sticks in? I had this same issue and found that it was my motherboard didnt like 4 sticks. After RMA im running perfect, though my mobo did work perfect with 2 sticks. So my advice if you havent tried, try 1 stick at a time and/or 2 sticks at a time.

I believe i got memtest errors though back when i had issues. Vista is very picky with the ram, prob cause it actually uses it. I would say try 1 stick, and if you can a different stick. If that doesnt work it might be your mobo.

Also how are you voltages? the 12, 5, and 3.3?
 
I have 4 sticks in there and all passed memtest for a couple of hours. Changing the timing and voltage may have done the trick to keep the BSOD's away. The next thing I need to do is to try to speed up the memory timings a bit.
 
Back
Top