The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
URGENT! XP BSOD right after windows logo on start up! Help!
Zombies Tossed My Salad!
Registered User regular
Registered User regular
So I was minding my own business friday night on the forums and then all of a sunnden a virus warning from AVAST pops up, my PC freezes, and then BSODs. This is the error message it gave me
It didn't give me any info about what file had caused the problem or anything else. That is the totallity of the error message other then "If this is the first time you've seen this message etc.". I turn it off and let it sit and then restart it, BSOD. Try "Last Good Config"; BSOD. Go into safemode, which boots just fine btw, and run Spybot and AdAware and neither of them pick up anything but the normal harmless tracking cookies.
So I try several system restore points, even going all the way back to last week on them and they all don't solve the problem. I've ran check disk on one drive and I am running it on the other currently. The last driver I installed was the directX 9.0c that came with the AVP demo that I had downloaded earlier that day.
How the fucking hell do I fix this? I need my computer, I have a lab report for my bio class due tomorrow and I am typing this out on my phone.
:IRQL_NOT_LESS_OR_EQUAL
STOP:0x0000000A
(0x00000000, 0x0000001C, 0x00000001, 0x804E1BF8)
STOP:0x0000000A
(0x00000000, 0x0000001C, 0x00000001, 0x804E1BF8)
It didn't give me any info about what file had caused the problem or anything else. That is the totallity of the error message other then "If this is the first time you've seen this message etc.". I turn it off and let it sit and then restart it, BSOD. Try "Last Good Config"; BSOD. Go into safemode, which boots just fine btw, and run Spybot and AdAware and neither of them pick up anything but the normal harmless tracking cookies.
So I try several system restore points, even going all the way back to last week on them and they all don't solve the problem. I've ran check disk on one drive and I am running it on the other currently. The last driver I installed was the directX 9.0c that came with the AVP demo that I had downloaded earlier that day.
How the fucking hell do I fix this? I need my computer, I have a lab report for my bio class due tomorrow and I am typing this out on my phone.
Zombies Tossed My Salad! on
0
Posts
software. <snip> Technically, this error condition means that a
kernel-mode process or driver tried to access a memory location to
which it did not have permission, or at a kernel Interrupt ReQuest
Level (IRQL) that was too high. (A kernel-mode process can access only
other processes that have an IRQL lower than, or equal to, its own.)"
Your specific error was caused by the Device Driver, Windows
Component, or Application Program that is using memory address
0x80522E06. Here is a procedure that may help you to trace the
error. Note that this procedure requires Microsoft Excel (or a
comparable spreadsheet product) in order to complete. If you do not
have such a spreadsheet then you can email me the PSTAT2.TXT file to
ron.martell@gmail.com and I will finish the check. Please do not
post the file to this newsgroup and also please include the text of
your original email (especially the STOP code and parameters in the
email with the file.
*******
Identifying the cause of STOP errors using PSTAT & Excel
Many times when a STOP error occurs the information provided does not
specifically identify the application, device driver, or other
component file where the error occurred. However the 4 parameters
associated with the STOP (bugcheck) code will very often include one
that is the address where the error occurred. You first need to look
up the detailed information about the specific STOP code in order to
determine if the address is included and if so which of the 4
parameters has the address.
You can identify the meaning of each of the parameters for your
specific STOP code at:
http://msdn2.microsoft.com/en-us/library/ms789516.aspx
The second step in the procedure is to identify the addresses that
each active process is being loaded at. The PSTAT utility will
provide this information. On some systems the PSTAT utility may
already be present. Check this by opening a Command Prompt window
(Start - Run - CMD) and entering the following command:
PSTAT /?
If PSTAT is not on your computer you can download it free from
Microsoft. The download is called "Windows XP Service Pack 2 Support
Tools" and it is available from
http://www.microsoft.com/downloads/d...displaylang=en
With PSTAT installed on your computer the next step is to open a
Command Prompt window again (Start - Run - CMD) and generate a report
with PSTAT. Because you need to copy part of the information from
this report (and only part) it is best to create the report as a text
file. In the Command Prompt window enter the following command:
PSTAT > C:\JUNK\PSTAT.TXT
You may change C:\JUNK\ to whatever drive and folder that you want to
save the report into.
Now open the saved file in Notepad. Start - Run - NOTEPAD
C:\JUNK\PSTAT.TXT
Scroll down the file, about 80% of the way to the end of the file and
you will find a head line:
ModuleName Load Addr Code Data Paged LinkDate
It is the information from this line to the end of the file that we
want to copy from this file and save as a separate file. Select the
block of text and copy it to the clipboard. Open a new notepad window
and paste the clipboard contents into it. Save this file under a
different name. I use PSTAT2.TXT and put it into the same C:\JUNK
folder.
Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT
file into Excel. Excel will automatically parse the file into
columns. Once this is done use DATA - SORT to sort the entire
spreadsheet based on the value in Column B (Load Addr).
It is now a simple task to read down the addresses until you find the
highest value that is less than the address where the error occurred.
That module (name in column A) is the prime suspect for the cause of
your error.
If you don't have excel, I'm sure open-office would be able to do it as well.
Googling suggests that this is a problem associated with possibly a recent Avast update.
If you're in a hurry, I suggest using Safe Mode to uninstall Avast (you can reinstall it after that if it doesn't work, so why not?).
That is exactly it. Thank you
Good luck with your lab report.
The problem was the spdt.sys file for some reason.
all that it took to fix it was bypassing it by pressing escape during the boot into safe mode and then renaming it and what ever copies are in other drives. it's located in the windows/system32 folder