Bluescreen on start up
- Hey,
I have a Dell Studio 1555 that I just bought recently, and I am running Windows Vista Home Premium 62-bit.
I have had a problem where I would constantly get a blue screen on start up, and my system rebooting after dumping physical memory, and the proccess repeats, disabling me from entering the operating system.
I have contacted Dell about the problem and they suggested that it was because my RAM was fried, so I sent it in about 3-4 weeks ago. Now the problem has come back, only it happens randomly and will eventually go away if I enter safe mode and restart from safe mode.
Please help, I am using this laptop for university and I am worried that one day I might not be able to enter my OS again, losing all of my assignments and data, and a computer to work with!
Thanks in advance,
NoliaM1 person got this answerI do too
Answers
- Hi,
Yes I would be talking to Dell to get replacement.
Rob - Bicycle - Mark Twain said it right.- Marked As Answer byEdgar - Support EngineerMSFT, ModeratorMonday, November 23, 2009 3:23 AM
All Replies
- Hi,
Do you know what Dell did? Did they just reload Windows on it?
We need more info to help :
Can you Access Safe Mode - repeatedly tap F8 as you boot - last known good configuration OR System Restore?
How to Do a System Restore in Vista
http://www.vistax64.com/tutorials/76905-system-restore-how.html
Look in the Event Viewer to see if anything is reported about those reboots.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm
-------------------------------------------------------------------------
This is my generic troubleshooter and can probably give a little more specific help when you give the BCC codes.
Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info that would
help. Such as the BCC and the other 4 entries on the lower left. And any other error information such as STOP
codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.
As examples :
BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002or in this format :
Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000
This is an excellent tool for posting Blue Screen Error Information
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the
information about all crashes in one table - Free
http://www.nirsoft.net/utils/blue_screen_view.html
Many BlueScreens are caused by old or corrupted drivers, especially video drivers however there are other causes.
You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or Recovery Options if your
system has that installed by the maker.
This tells you how to access the System Recovery Options and/or from a Vista DVD
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx
You can try a System Restore back to a point before the problem started if there is one.
How to Do a System Restore in Vista
http://www.vistax64.com/tutorials/76905-system-restore-how.html
-------------------------------------------------------------------------
Start - type this in Search Box -> COMMAND find at top and RIGHT CLICK - RUN AS ADMIN
Enter this at the prompt - sfc /scannow
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log
http://support.microsoft.com/kb/928228
The log might give you the answer if there was a corrupted driver. (Does not tell all the possible driver issues).
Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Vista
http://www.vistax64.com/tutorials/67612-check-disk-chkdsk.html
-------------------------------------------------------------------------
Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party keyboard and
mouse, as well as other major device drivers.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htmHow to Install a Device Driver in Vista Device Manager
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.htmlHow To Disable Automatic Driver Installation In Windows Vista - Drivers
This tells you how to access the System Recovery Options and/or from a Vista DVD
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx
-------------------------------------------------------------------------
How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
http://support.microsoft.com/kb/958233
Troubleshooting Vista Blue Screen, STOP Errors
http://www.chicagotech.net/vista/vistabluescreen.htm
Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692
Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033
-------------------------------------------------------------------------
In some cases this might be required.
StartUp Repair from Recovery Options or Vista disk
How to do a Startup Repair
http://www.vistax64.com/tutorials/91467-startup-repair.html
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx
Hope this helps.
Rob - Bicycle - Mark Twain said it right.- Proposed As Answer bySpiritX Wednesday, November 04, 2009 7:06 PM
- Thanks for the fast response! Sorry for the lack of info..
h
My computer can go into safe mode, as i mentioned, after restarting the computer from safe mode, it seems to work. However, choosing the "last known good config" option still leads me to a blue screen. I have not performed a system restore yet.
I'm pretty sure all dell did was reinstall windows and replace my RAM and my HD. But something tells me that probably is not the problem.
---
I downloaded the Bluescreenveiwer that you suggested. And as soon as I ran the app, 4 cases popped up right away..here are some more info on the 4:
November 4th, 2009:
Bug Check String: IRQL_NOT_LESS_OR_EQUAL
BCCode: 0x0000000a
BCP1: 00000000`00000880
BCP2: 00000000`0000000c
BCP3:00000000`00000001
BCP4: fffff800`01e31985
Caused by Driver: mssmbios.sys
Caused by Address: mssmbios.sys+11f4720
October 30th, 2009
- Pretty much the same as the Nov 4th crash, but the "Caused by Address" shows something slightly different
mssmbios.sys+11f5720
October 30th, 2009
- I had two on this day, again "caused by address" is ever so slightly different:
mssmbios.sys+11f5720
October 28th, 2009
Bug Check String: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
BCCode: 0x1000007e
BCP1: ffffffff`c0000005
BCP2: fffff800`01c8a995
BCP3: fffffa60`005e4558
BCP4: fffffa60`005e3f30
Caused by Driver: OA008Vid.sys
Caused by Address: OA008Vid.sys+100a2
---
i ran a sfc /scannow and everything seems to be fine
---
hope the additional information helps!
Thanks - Hi,
Right Dell may not have really fixed the issue at all. Probably best to get them back involved especially if you
have any warranty claim on the system or the work they did.
Did the Event Viewer Utility show any Driver errors?
Look in the Event Viewer to see if anything is reported about those reboots.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm
Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows Updates to
see if any drivers were updated there. Other lessor possibilities include antivirus/antispyware/security programs.
It is quite likely that the BCCode " a " bluescreen was not caused by mssmbios.sys but another driver causing
it to fault.
mssmbios.sys is part of windows
http://www.computerhope.com/cgi-bin/process.pl?p=mssmbios.sys
BCCode 7e was caused by the Creative Camera driver OR another driver causing it to fault.
Both of those errors could be other drivers or BIOS and other hardware.
-----------------------------------------------------------------
BCCode a
Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem
If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS- Restart your computer.
- Press F8 at the character-based menu that displays the operating system choices.
- Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
- Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
- Try disabling memory caching of the BIOS.
- Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
- Make sure the latest Service Pack is installed.
- If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
- For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.
Comments
Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.
===========================================
BCCode 7e
Cause
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.
Common exception codes include the follwoing:
- 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
For a complete list of exception codes, see the Ntstatus.h file that is located in the inc directory of the Microsoft Windows Driver Kit (WDK).
Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
- Make sure you have enough disk space.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Try changing video adapters.
- Check with your hardware vendor for any BIOS updates.
- Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.
If you do not know the specific cause of the exception, consider the following issues:
- Hardware incompatibility. Make sure that any new hardware that is installed is listed in the Microsoft Windows Marketplace Tested Products List.
- Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.
You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.
======================================================
Please see the generic troubleshooter in 1st message above and also use the generic driver update methods to update major drivers, BIOS, and control software (if any).
This is my generic how to for proper driver updates :
This utility makes it easy to see which versions are loaded :
DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For
each driver in the list, additional useful information is displayed: load address of the driver, description,
version, product name, company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html
For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
Control Panel - Device Manager - Display Adapter - write down the make and complete model of your
video adapter - double click - Driver's tab - write down the version info. Now click UPdate Driver (this
may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT
this will refresh the driver stack.
Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party with their
own software and drivers and any other major device drivers you have.
Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site
(Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset and software
updates at System Maker's site while there.)
Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after each installation.
Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This
is because some drivers rollback before the latest is installed (sound drivers particularly do this) so install a
driver - reboot - check to be sure it is installed and repeat as needed.
Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htmHow to Install a Device Driver in Vista Device Manager
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html
If you update drivers manually then it is a good idea to disable Driver Installations in Windows Updates,
this leaves Windows Updates ON however it will not install drivers which will usually be older and cause
issues. If Updates suggests a new driver then HIDE it (Right Click on it) and then go look for new ones
manually if you wish.
How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx
Hope these help.
Rob - Bicycle - Mark Twain said it right. - Hi,
Check the above and if you need to do more troubleshooting :
Can you Access Safe Mode - repeatedly tap F8 as you boot - last known good configuration OR System Restore?
How to Do a System Restore in Vista
http://www.vistax64.com/tutorials/76905-system-restore-how.html
Look in the Event Viewer to see if anything is reported about those reboots.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm
-------------------------------------------------------------------------
This is my generic troubleshooter and can probably give a little more specific help when you give the BCC codes.
Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info that would
help. Such as the BCC and the other 4 entries on the lower left. And any other error information such as STOP
codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.
As examples :
BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002or in this format :
Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000
This is an excellent tool for posting Blue Screen Error Information
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the
information about all crashes in one table - Free
http://www.nirsoft.net/utils/blue_screen_view.html
Many BlueScreens are caused by old or corrupted drivers, especially video drivers however there are other causes.
You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or Recovery Options if your
system has that installed by the maker.
This tells you how to access the System Recovery Options and/or from a Vista DVD
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx
You can try a System Restore back to a point before the problem started if there is one.
How to Do a System Restore in Vista
http://www.vistax64.com/tutorials/76905-system-restore-how.html
-------------------------------------------------------------------------
Start - type this in Search Box -> COMMAND find at top and RIGHT CLICK - RUN AS ADMIN
Enter this at the prompt - sfc /scannow
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log
http://support.microsoft.com/kb/928228
The log might give you the answer if there was a corrupted driver. (Does not tell all the possible driver issues).
Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Vista
http://www.vistax64.com/tutorials/67612-check-disk-chkdsk.html
-------------------------------------------------------------------------
Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party keyboard and
mouse, as well as other major device drivers.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htmHow to Install a Device Driver in Vista Device Manager
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.htmlHow To Disable Automatic Driver Installation In Windows Vista - Drivers
This tells you how to access the System Recovery Options and/or from a Vista DVD
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx
-------------------------------------------------------------------------
How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
http://support.microsoft.com/kb/958233
Troubleshooting Vista Blue Screen, STOP Errors
http://www.chicagotech.net/vista/vistabluescreen.htm
Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692
Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033
-------------------------------------------------------------------------
In some cases this might be required.
StartUp Repair from Recovery Options or Vista disk
How to do a Startup Repair
http://www.vistax64.com/tutorials/91467-startup-repair.html
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx
Hope this helps.
Rob - Bicycle - Mark Twain said it right. - Hey,
my friend suggested that my vista might have installed an update that might not be for 62-bit OS.....and that could be what is causing the issue.
Could that be possible?
The even viewer shows many errors, (total 441) of just random things..mainly applications and system stuff. There are also 2146 warnings of the same category...is there anything specific i should be looking for?
- It is "possible" an update caused the issue though unikely.
Look for driver related and other errors/issues in the event viewer - there may be no useful info there.
Proceed through the troubleshooter.
Rob - Bicycle - Mark Twain said it right. - Things are getting worse now, I am getting blue screens randomly now while using my computer...here are some details on every kind of BSOD that i have encountered (that are new) :
Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x0000001e
BCP1: ffffffff`c0000005
BCP2: fffffa60`0269401e
BCP3: 00000000`00000000
BCP4: ffffffff`ffffffff
Caused by Driver: bcmwl664.sys
caused by address :bcmwl664.sys+8901e
i've encountered two of these BSOD...
bug check string: DRIVER_IRQL_NOT_LESS_OR_EQUAL
bccode: DRIVER_IRQL_NOT_LESS_OR_EQUAL
bcp1: 00000000`0000e6bc
bcp2: 00000000`00000002
bcp3: 00000000`00000000
bcp4: fffffa60`02694c19
caused by driver: bcmwl664.sys
caused by address: bcmwl664.sys+8ac19
I have had..about 5 of these now
bug check string: INTERRUPT_EXCEPTION_NOT_HANDLED
bccode: 0x0000003d
bcp1: 00000000`00000000
bcp2: 00000000`00000000
bcp3: 00000000`00000000
bcp4: fffffa60`0269101e
caused by driver: bcmwl664.sys
caused by address: bcmwl664.sys+8901e
bug check string: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
bccode: 0x1000007e
bcp1: ffffffff`c0000005
bcp2: fffff800`01c8a995
bcp3: fffffa60`005e4558
bcp4: fffffa60`005e3f30
caused by driver: OA008Vid.sys
caused by address: OA008Vid.sys+100a2
i've also had several more IRQL_NOT_LESS_OR_EQUAL BSODs caused by rassstp.sys, mssmbios.sys, and umbus.sys
..it seems like many of the BSODs are caused by bcmwl664.sys....
this is rediculous, i've had problems ever since i got this laptop...maybe i can see if dell is willing to give me at least a replacment.. - Hi,
Yes I would be talking to Dell to get replacement.
Rob - Bicycle - Mark Twain said it right.- Marked As Answer byEdgar - Support EngineerMSFT, ModeratorMonday, November 23, 2009 3:23 AM
