Windows VistaPost your Windows Vista related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
--------------------------------------------------------------------------
I searched around a bit and someone mentioned it could be a RAM problem. I had my laptop with me. So I took my 2 ram sticks out, put them in her computer, and we get the same exact issue. I believe our RAM has the same stats.
What we've tryed to fix the issue:
Formatting. This has been a problem for about 3 months. I had reformatted her computer, and we get the same issue right off the bat. Aside from that, she did download and install some software immediately after formatting that may be causing issues - limewire, itunes, etc. etc. I've done disk check a few times that took hours and didn't help any. I downloaded a registry cleaner/fixer full version that didn't fix it. Virus scan, etc. etc. same issue.
About the BIOS settings. I'm not sure where I can change the settings. Upon startup we have option to F2 for setup, or F12 for Advanced Settings or something. F12 will show me a lot of things, with Memory being one of them but it says the settings are not changeable. So, I don't know where to set the RAM settings on the computer.
Another possible cause: She had an issue connecting to the internet on her computer a while ago before the bluescreen problems. Dell doesn't have a wi-fi switch, but yet a key combination you have to push. They have a FN key which I didn't try - I tryed the CTRL, and ALT keys with the wi-fi button and it wasn't until AFTER I reformatted I tryed the combination. BUT, she had contacted dell, and dell looked far past the basics and assumed it was an issue with her wi-fi adapter. They sent her a new one and someone replaced the wi-fi adapter in her computer with another one from dell. I don't know what a wi-fi adapter looks like, nor where it is located in her computer. So, I can't remove it to test and see if that's what's causing the issue. All the computer techs around here charge over 75 dollars an hour for labor plus extra fee's! That's nuts!
Anyways, what can you fine folks around here recommend we do next? Note that formatting again is very unwanted at this point.
Thank you!
Didn't find the information you thought to find? Check out these Similar Threads
We are not that keen on working in parallel with another forum as it is not time efficient (for either forum) and we are all volunteers here.
That said a 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED errors are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).
If you are able to start in Safe Mode without issue it is more likely to be a driver problem than hardware, although this remains a possibility.
I suggest two courses of action .....
Check out the RAM - using the original supplied - it is not wise to swap willy nilly between computers unless you are 100% certain that the other RAM is compatible. You can use the Memory Diagnostic function of Vista if you like, but note this ....
Quote:
Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
Better to try running with one RAM stick, switch between slots and repeat for the other stick. This checks out individual sticks and individual slots.
Secondly download our Dump Data Collection tool and debug the memory dump - given that one is produced, and post the log here .....
These logs require expert knowledge to analyze and there are only 2 members (who occasionally visit WindowsBBS.com) that have the depth of knowledge necessary. Other members can make observations and suggestions as to how you might proceed toward finding the cause ....
First, the only other forum I posted on was a vistahelpforum which hasn't responded. The link you stated is totally unfamiliar. Someone may have posted my problem elsewhere to see if they could find help, and then reply with answers?
Anyways,
I will do what you say as far as recommendations. But first - you stated that it was most likely a hardware or driver issue. You said it is fine in safe mode so you think most likely a driver issue... But then you went on suggesting things to do with the RAM. If the RAM turns out fine, what could I do for the drivers? Windows Update doesn't work in safe mode I don't think. ANd I don't know how to test all the drivers or anything like that.
It is always a good idea to check RAM whenever BSOD's appear.
Never use Windows Update to obtain updated drivers - past history tells that this often spells disaster. Always go to the manufacturer's web site.
Quote:
We are getting bluescreen every single time we boot up in normal startup
This implies that a program loading at startup is likely to be causing the problem. As you presumably cannot boot at all into normal mode boot into Safe Mode and go ....
Start > Run > msconfig > Enter
Go to the Startup tab and disable all startup items. Reboot as requested - if the computer reboots into Normal mode without bluescreening go back into msconfig and re-enable each startup item one at a time, rebooting inbetween until the bluescreening reappears. The last item you enabled is causing the problem.
BTW it is highly underirable and completely insecure to install Limewire - you have no idea how badly the computers you latch onto are infected and what you may pick up. Just my 2 pence worth, which would be echoed by our spyware gurus
Yes, I had done msconfig before. I actually went to the services tab, hide all microsoft services, and disabled all the other ones. Then, went to the startup tab and disabled all there as well. Same issue.
As far as limewire, I told her numerous times over and over NOT to install limewire. I don't have a huge problem with p2p programs but I HATE limewire. So, when I get over to her place today I'll uninstall it!
One thing about msconfig... - Althought I disabled all startup and services, There are like 2 or 3 startup programs that wouldn't stop. I think it was AOL Loader and Google and something else. But I can't disable it through msconfig. I think the program itself has settings to start at startup and I'll have to go into there to change it.
Anyways, I will do the RAM tests in a little bit, post the results, and take your advice for uninstalling limewire and checking dell's site for driver updates.
Things got worse. Starting up in normal mode lasts about 1 minute max. And, while in any safe mode, I can't install or uninstall any programs. I would get errors about windows installer. Which means, I was unable to install any programs such as the logger and other programs you listed. So, I eventually just gave up and reformatted her computer. It's working fine now.
Thanks for all the help Pete! I really appreciate it! Have a great 08
After reformatting, everything worked great. I installed AIM's latest version - no problems. I gave her a lecture on how NOT to download ANYTHING and if she was going to, to ask me first! She didn't listen, and downloaded Adobe's Flash Active X Control, and Quicktime/ITunes. She started getting the BSOD again. So, I just uninstalled everything. Apple Update, Quicktime Update, something called Bonjour that was related to Quicktime, and then Quicktime and ITunes. Deleted the program files, app data files, and out of the registry, restarted, and no more BSOD. SO - I think something in Quicktimes software is causing the error.
Anyways, thanks again for the help and looks like that's what was causing it all along.
