New
#71
Service
start run type services.msc
Last edited by computersplus; 05 Jan 2010 at 22:57.
Windows 7 64bit BSOD
-
-
New #72
I do not recommend the use of Registry scanners/cleaners - they cause more problems than they are worth (and, IMO, they really don't help things out anyway).
Memory dumps point to core Windows files - which is unlikely because you'd have lot's of other issues if the core files were corrupted. So, please try this:
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"
- 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.
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.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
-
New #73
-
New #74
@WishmasterExcellent!! However, to be more accurate, youll want to change stress level form Standard --> Very High or Maximum.
it will take longer to run though, but would be advisable, especially considering you have 8GB RAm
Have the problems seemed to have disappeared for now, or usually take longer to show up?
well, at 1066 the tighter timings may just be fine.
At 1333 it may causing issues.
If you want, you can try and revert to 1333, as is, and do the test again. just to see what results you get.
if it fails, then try to change timings to 9-9-9-24 and run again to see what that shows.
If you get failures at 133, then we know why and what is causing your problems :)
I have let my PC run for more then 24hours already @1066 speed. So far no crashes like i mentioned earlier. I will try to revert back to 1333 and run the stress test and see if there is any chances of failing. If yes i will change the timings like you have mentioned.
-
New #75
It seems this was the root of your issue. Depending on the board, the MAX rated RAM speed does tend to be changed when you populate all 4 slots.
You may or may not be able to run all 4 slots at 1333, or may just take voltage tweaks to stabilize it.
At this point you can leave as is, or try to attempt getting 1333 speeds. You may need to loosen timings
((Keep in mind the timings you currently have, as if you decide to stay at 1066, the tighter timings will help you just slightly -- and we know its happy here))
Stress with IBT MAX load.
If that doesnt work, NB voltages etc may be in order.
The bad thing is with RAM unstable it probably has caused much deeper issues overall for your windows install.
Chances of file corruption are really bad (nearly 100%) even if it all of it isnt immediatley apparent, as pointed out.
Especially if it was unstable when you initially installed Windows.
If it were me, I would make sure its perfectly stable, and happy with it, and then do a clean install.
However, others here may be more adept at helping you track down and repair these issues so no re-install is needed. I wouldn't really know where to start myself, other than clean install.
Im glad you got the issue resolved (or at least pin pointed) :) But still more to be done
-
New #76
So wat is your best advice for my situation. So i just leave it as it is 1066 and do a clean install of Win 7 again. Since i do not require all the high speeds or overclockings etc since im not into gaming. Mine is just for Office use and some applications. Other then that there isnt anything much of use with my PC.
So what would you suggest?
-
New #77
Ram speed
remember that a lot of boards list the memory spec with 1066 1333(OC) this means that the board will run the ram at 1066 at a stock FSB in order to achieve the 1333 you must overlock the the FSB which will increase the Ram speed it dosen't mean you just put in some ram rated at 1333 and it just runs at that
-
New #78
If the issue is resolved you may consider leaving as is for what you do.So wat is your best advice for my situation. So i just leave it as it is 1066 and do a clean install of Win 7 again. Since i do not require all the high speeds or overclockings etc since im not into gaming. Mine is just for Office use and some applications. Other then that there isnt anything much of use with my PC.
So what would you suggest?
Even gaming however, the higher RAM speed will not make any significant difference.
You can try 1333, and the lower timings, however this is your call.
I would clean install,
BUT ...Before you do a clean install, I would check with others to see what their opinion is. They may be able to help you find and repair any corruption caused.
I do not know if its possible, or not honestly.
-
New #79
if in doubt
if in doubt format and reinstall you have to make sure that bios and hardware are correct BEFORE you install OS!
-
New #80
I have set my RAM to run at 1333 and ran the IntelBurn test. Its passed strangely?
Quote
Related Discussions