Unsolved
This post is more than 5 years old
1 Message
0
2703
Dell Studio 1558 really odd BSOD error!
Hey guys
I have this really odd error on my laptop (Dell Studio 1558) and i have recorded it in this video:
Thing is, it only does that during a BSOD, this one in the video was manually triggered by me. The BSOD does not occur because the screen garbles, the BSOD is garbled. This happens even after reinstalling the OS too. Yet all the hardware has passed Dells (very in depth might i add) testing process' that you can boot into.
OS: Windows 7
Does anyone have any idea what is going on with this?
Cheers!
DELL-Terry B
4 Operator
4 Operator
•
3.5K Posts
0
April 12th, 2011 15:00
BIOSNOVA
You mention that the system gets the garbled video after having a BSOD. Have you been able to record the exact BSOD error is? Have you tried running a debugger on the minidump files on the system and see if they can give more detail?
Here is a link for the debugger
http://msdn.microsoft.com/en-us/windows/hardware/gg463012
To find where the minidump error messages are, open computer, then local disk (c:) , windows, then look for and open the minidump, folder. The errors should be located there.
If they are no errors listed then make sure that it is turned on in Windows to save them. Open control panel, system, advanced system settings, click the advanced tab, and click settings under "startup and recovery". There should be field near the bottom of the window named Dump File: It may read something like %SystemRoot%\Memory.DMP which is fine. Make sure that "write an event to the system log is checked and that overwrite any existing file is unchecked. Then you may have to wait for the next BSOD but you should be able to find the new error in the minidump folder under the windows directory.
Then go to the debugger. If you have not already done so please be sure to set the symbol path
Set your symbol path
You have to do this. You will not get helpful information unless it is done correctly. There are a number of ways to get it right, and this is possibly the easiest;
a) Start WinDBG
b) WITHOUT opening any dump files, click File, "Symbol File Path..."
c) Set the path to be the following:
SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
The following link should have more info on setting the symbol path
http://msdn.microsoft.com/en-us/windows/hardware/gg463028
You can simply type file/open crash dump then point to the minidump file of the error. I would use the! Analyze -v commands while in the debugger, it will give you more information on the error. What we are hoping for is that the debugged error will give us a name of a program or driver and that will point out to us where the problem is coming from.
If you simply wish to send the minidump to me, via private message then I can analyze them here. That is up to you. So am looking forward to seeing copies of the errors or hearing from you that you were able to debug them and what you found out.
TB