krraaak Posted August 6, 2007 Share Posted August 6, 2007 I'm running VISTA Home Premium on a new PC (IBM ThinkCentre A55, Duo 2 Core, 2GB RAM) and i have the following problem:After starting up the PC (cold boot) it's running for about 3 to 5 minutes and then the blue screen pops up. This doesn't happen randomly though it's only after a cold boot and after about 3 to 5 minutes. After restart (hot boot) everything is fine. As long as i don't turn off the PC there are no errors anymore.Most of the time it's the following error code: (see screen shot)Following actions have already been taken but no solution yet:Hardware:- changed the motherboard- checked and changed the harddrive- checked and changed the RAM- upgraded the BIOS- installed latest drivers for all hardware components (Upgrade driver function)- booting without ASUS wireless USB device (used to connect to my router)(fyi, the video card is embedded in the motherboard)Software:- I've also read that the anti-virus product could be a problem. So i disabled Trend Mirco (also in "Control Panel -> Services")What's left is: - changing the CPU. But CPU failure is very rare (so i'm told)- using the computer to throw at the next IBM tech guy that comes thought the door ...... unless any of you has any other idea's. Link to comment Share on other sites More sharing options...
bluescreens Posted August 6, 2007 Share Posted August 6, 2007 Sounds hardware-ish, but I'd be happy to look. Run MPSReports (setup-perf version) - from Microsoft, and send me the contents of c:\windows\minidump. Send the mpsreports .cab output file and the dumpfiles to bluescreens at gmail dot com in a zipfile. Link to comment Share on other sites More sharing options...
krraaak Posted August 6, 2007 Author Share Posted August 6, 2007 Okie Bluescreens. Done. Although Vista wasn't very happy when i ran the .exe file. After installing Vista wanted me to re-install with "recommended settings" (you know, the 3 options window that appears in Vista when user control is running). Maybe because on the Microsoft site it's not mentioned it's compatible with Vista, only XP and lower. But it worked anyway.Sending everything to you after this. I have been looking at those minidump files myself a few days ago with WinDbg but it says nothing much to me. Anyway, already thanks for your help and support. Link to comment Share on other sites More sharing options...
Brando569 Posted August 6, 2007 Share Posted August 6, 2007 i see they updated the BSOD to "the nice white screen of death" lol, one of the features i do like in vista is how helpful (well compared to the other versions) it is when it comes to problems and errors. Link to comment Share on other sites More sharing options...
bluescreens Posted August 6, 2007 Share Posted August 6, 2007 Sounds hardware-ish, but I'd be happy to look. Run MPSReports (setup-perf version) - from Microsoft, and send me the contents of c:\windows\minidump. Send the mpsreports .cab output file and the dumpfiles to bluescreens at gmail dot com in a zipfile.Open up the system event log, text version from that .cab file (use winrar to explode it) and do a find for memory.dmp.You have what, 8 I think, dumps in the past 7 days. That's a disaster. And they're all (or almost all) different. To me this is a hardware problem. If you'd mailed all the other minidumps I could be more sure, but that looks like a hardware issue. Link to comment Share on other sites More sharing options...
krraaak Posted August 7, 2007 Author Share Posted August 7, 2007 Sounds hardware-ish, but I'd be happy to look. Run MPSReports (setup-perf version) - from Microsoft, and send me the contents of c:\windows\minidump. Send the mpsreports .cab output file and the dumpfiles to bluescreens at gmail dot com in a zipfile.Open up the system event log, text version from that .cab file (use winrar to explode it) and do a find for memory.dmp.You have what, 8 I think, dumps in the past 7 days. That's a disaster. And they're all (or almost all) different. To me this is a hardware problem. If you'd mailed all the other minidumps I could be more sure, but that looks like a hardware issue.I saved alle the minidumps. I'll send them over. The date they happened is infront of the filename.8 dumps, well, it's just like i told you. Starting up with a cold boot gives the problem. So that's about 8 days ago the problem started.According to the MS reply after reporting the problem it's most likely the following:- CPU- Power Supply- Memory- System board(To be sure we need more info..)... so basically, what Bill & Co are saying is: we don't know, replace everything .... :) Link to comment Share on other sites More sharing options...
bluescreens Posted August 7, 2007 Share Posted August 7, 2007 Sounds hardware-ish, but I'd be happy to look. Run MPSReports (setup-perf version) - from Microsoft, and send me the contents of c:\windows\minidump. Send the mpsreports .cab output file and the dumpfiles to bluescreens at gmail dot com in a zipfile.Open up the system event log, text version from that .cab file (use winrar to explode it) and do a find for memory.dmp.You have what, 8 I think, dumps in the past 7 days. That's a disaster. And they're all (or almost all) different. To me this is a hardware problem. If you'd mailed all the other minidumps I could be more sure, but that looks like a hardware issue.I saved alle the minidumps. I'll send them over. The date they happened is infront of the filename.8 dumps, well, it's just like i told you. Starting up with a cold boot gives the problem. So that's about 8 days ago the problem started.According to the MS reply after reporting the problem it's most likely the following:- CPU- Power Supply- Memory- System board(To be sure we need more info..)... so basically, what Bill & Co are saying is: we don't know, replace everything .... Outside of a few CPU and memory errors (bitflips and the like, plus parity issues) it's really tough for your OS to tell you what bits in your hardware have a problem without running manufacturer supplied diagnostics programs. Blaming MS is silly. Looked at the other dumps. Still think you have a HW problem. Link to comment Share on other sites More sharing options...
deaden Posted August 7, 2007 Share Posted August 7, 2007 Run some CPU and memory tests. Prime95 and Memtest are good choices. Also, can you try upping the voltage to the cpu just a little bit? Is that even an option?Startup problems relating to the psu flakin out usually happen quicker and cause POST errors. PSU related errors after post usually require a heavy load and enough time for it to reach a certain hot point. Are the voltages on the rails steady or do you see fluctuation?Also disabling Trend Micro in the BIOS might not disable all components. The only way to rule it out is a complete uninstall.Otherwise you might want to wait for SP1 to come out..... Link to comment Share on other sites More sharing options...
krraaak Posted August 7, 2007 Author Share Posted August 7, 2007 Run some CPU and memory tests. Prime95 and Memtest are good choices. Also, can you try upping the voltage to the cpu just a little bit? Is that even an option?Startup problems relating to the psu flakin out usually happen quicker and cause POST errors. PSU related errors after post usually require a heavy load and enough time for it to reach a certain hot point. Are the voltages on the rails steady or do you see fluctuation?Also disabling Trend Micro in the BIOS might not disable all components. The only way to rule it out is a complete uninstall.Otherwise you might want to wait for SP1 to come out.....I don't think it's Trend Micro. The PC came standard with Norton IS and it happened then already, so before installing TM. (I have a TM license from my employer, that's why i'm using it)Anyway, let me try those tests you suggest and see. The CPU was changed today but the problem is still there. Not much is left now except the power supply unit.What i'm gonne do is uninstall my wireless router + it's drivers (ASUS brand). In the system event log i often see an error concerning ASWLSVC (.exe). When i look it up, it seems to be ASUS wireless LAN related. Bluescreens certainly also saw that in the logs i send him/her over.If all of that fails, the IBM guys are gone give me a temporay PC replacement and take my machine for extensive testing... So i hope if they do find the problem that's causing this, that they will share it with me so i can share it with you guys. Link to comment Share on other sites More sharing options...
krraaak Posted August 7, 2007 Author Share Posted August 7, 2007 Run some CPU and memory tests. Prime95 and Memtest are good choices.Btw, are these tests compatible with Vista? Link to comment Share on other sites More sharing options...
fizban2 Posted August 7, 2007 Share Posted August 7, 2007 Krraak, configure your computer to do a full memory dump when the error occurs,system properties => advanced => start up and recovery settings => configure it to do a full memory dump. when the machine blues screens again let me know know. Link to comment Share on other sites More sharing options...
erpdude8 Posted August 10, 2007 Share Posted August 10, 2007 (edited) Run some CPU and memory tests. Prime95 and Memtest are good choices.Btw, are these tests compatible with Vista?Memtest should work fine under Vista if you can boot from a bootable CD that loads Memtest.Download the Memtest ISO image and burn it onto a CD or DVD at one of these sites-MemTest86+http://www.memtest.org/original MemTest86http://www.memtest86.com/Prime95, on the other hand, may or may not work under Vista so follow the directions from this page:http://www.mersenne.org/freesoft.htm Edited August 10, 2007 by erpdude8 Link to comment Share on other sites More sharing options...
gosh Posted August 13, 2007 Share Posted August 13, 2007 a stop 50 is usually bad ram. You say you've tried different sticks of ram and another motherboard, but i wonder if that was done correctly.-gosh Link to comment Share on other sites More sharing options...
un4given1 Posted August 13, 2007 Share Posted August 13, 2007 Krraak, configure your computer to do a full memory dump when the error occurs,system properties => advanced => start up and recovery settings => configure it to do a full memory dump. when the machine blues screens again let me know know.This is definately the best advice so far. Link to comment Share on other sites More sharing options...
krraaak Posted August 13, 2007 Author Share Posted August 13, 2007 Hi guys,Thanks for all the support.I finally figured out the problem. Well i think it's the following: a service called aswlsvc.exe it's installed when one installs the cdrom that comes with ASUS WLAN. Disabling the service doesn't work. Every instance has to be removed from the registry manually exept for the legacy keys referring to the service. As you know: one can't delete legacy keys (there's ways around that but pretty dangerous i guess)What the service does is unclear but it's installed automatically. So the best way to install the drivers for the WLAN is just not autorun the CD but let Vista look for the drivers then only the drivers are installed and not that weird service. And that fixed the problem.Maybe it's some kind of interaction at boot between the hardware blue tooth device and software... i don't really know. The only thing i know is that i did what i did and there's no more blue screens. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now