Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
All kind of crashes under Windows 7 64 bits
Message
From
26/07/2010 01:49:39
 
 
To
26/07/2010 01:29:30
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01473824
Message ID:
01473870
Views:
30
>>Normal is 0 errors. You have bad RAM.
>>
>>When I ran the test with my formerly bad RAM, it came up with about 200 errors (IIRC) in the first few seconds. I knew if it was failing that fast, I definitely had a bad stick. Sounds like yours is even worse.
>>
>>I have seen some intermittent RAM failures that required running that utility overnight for errors to show up.
>>
>>Hopefully the errors are limited to one of the 4 sticks you currently have in the computer, and the error messages should point out which stick it is. You can remove that stick, and its partner and run with only 4GB until you get replacement RAM. Be sure to test again if you do this.
>>
>>There is one other slight possibility - incorrect RAM settings in the BIOS - either on purpose, or by mistake.
>>
>>Some unscrupulous system builders will overclock RAM to squeeze a little extra performance, or to save a little money by using slower, cheaper parts. Or, if they don't know what they're doing they may have set the speed of the RAM beyond its specifications.
>>
>>If you bought your system or components from a reputable and competent dealer this is not likely the problem. But if you suspect this may be the case, in most system BIOSs there is a command to "Load safe defaults" or words to that effect - load a conservative configuration that should be reliable. You may try that. If you do so, be sure to record your existing settings on all screens. Since you can't do print screens or captures in the BIOS, one way is to use a digital camera.
>
>Thanks

For lurkers, I should qualify the "load safe defaults" option I mentioned above. You may not want to do this if you know you're running a drive array using a motherboard RAID controller. Loading safe defaults may disable this controller, or change its setting to "compatible", thus breaking the array and making your system boot improperly, or not at all.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Previous
Reply
Map
View

Click here to load this message in the networking platform