BleepingComputer.com: Blue Screen on Startup

I recently dusted out my computer as it was overheating like hell. It made the fan stop working for a few minutes (not unusual, this computer is terrible) and when I finally got it to start working it blue screens on startup. error starts with STOP: 0x00000024 and some stuff in parentheses that I'll write down later if you need it. It's a blue screen that i've never seen before as it's shorter than normal, only half the screen actually has text.

Even weirder, and to help prove that it's not a hardware problem, I can boot into linux without any issues on the same computer, same hard drive.

EDIT: okay, so apparently it's a common dirty NTFS issue. Still, any ideas what to do?

EDIT 2: I have done some linux ntfs crap and all I get is: partition is already mounted or refusing to work with partition, so no luck there.

This post has been edited by sausage: 20 March 2011 - 10:22 PM

Hi -
Please do the following as it will provide us with more information.

Please download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thank You -

One issue with that: I can't get into Windows.

EDIT: Ok, pulled some strings in Linux and found it. not sure if it has what you want, but here you go

I don't see my dump in there...


==================================================
Dump File : Mini021911-01.dmp
Crash Time : 2/19/2011 10:48:56 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x80545232
Parameter 3 : 0xf7a58b38
Parameter 4 : 0xf7a58834
Caused By Driver : SynTP.sys
Caused By Address : SynTP.sys+1616c
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : /mnt/usbstick/WINDOWS/minidump\Mini021911-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 110,592
==================================================

==================================================
Dump File : Mini121510-01.dmp
Crash Time : 12/15/2010 7:12:00 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe56f5c94
Parameter 2 : 0x00000000
Parameter 3 : 0xbf08e3e6
Parameter 4 : 0x00000001
Caused By Driver : ati2cqag.dll
Caused By Address : ati2cqag.dll+293e6
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : /mnt/usbstick/WINDOWS/minidump\Mini121510-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 110,592
==================================================

This post has been edited by sausage: 21 March 2011 - 11:37 AM

If...it's a fixable file error...then try to run the chkdsk /r command.

STOP 24 errors can be several types of situations. Could be simple file damage...could be NTFS file system for partition...could be something else with partitition structure...could be caused by hard drive problems.

IMO, the smart thing is to treat it as if it's the worst possible scenario...and then (after moving any valued data files) start with attempting to try the least harmful scenario...run chkdsk /r and see if that accomplishes anything.

Generic info on STOP 24 errors, Aumha STOP Errors - http://www.aumha.org/a/stop.htm .

Louis

Open your computer again and make sure everything is firmly seated and you didn't dislodge anything when you dusted (I hope you used compressed air and didn't actually "dust"). Especially check ram modules and all cables. Be sure to discharge any residual static before touching anything inside the case.

@ham: I can't get into windows.

@Allan: already did that

Well, you might just want to do a repair install. Boot to the XP CD and choose the SECOND repair option, allowing XP to install on top of itself. After completion you'll need to go to Windows Update and download & install all updates (except for hardware & driver related updates, which should never be downloaded from Windows Update - only from the OEM websites). Here is a clear tutorial on how to perform a repair install:http://www.geekstogo.com/forum/topic/138-how-to-repair-windows-xp/

OK, something's wrong. Linux is messing up now. possible hard drive failure? or other hardware?

This post has been edited by sausage: 22 March 2011 - 02:30 PM

"STOP 24 errors can be several types of situations. Could be simple file damage...could be NTFS file system for partition...could be something else with partitition structure...could be caused by hard drive problems."

I think I mentioned the possibility of hard drive problems causing havoc.

If...I wanted to find out if I had such...I would run the appropriate hard drive diagnostic...before attempting a repair of any sort.

Louis

ok, just a thought here.

I ran CHKDSK in a recovery console and got back into windows, but my internet adapters are missing and who knows what else isn't working.

I saved dxdiag info and here's what really throws me off:

System Manufacturer: n/a
System Model: n/a
BIOS: n/a

Name: Intel® PRO/Wireless 3945ABG Network Connection
Device ID: PCI\VEN_8086&DEV_4227&SUBSYS_10108086&REV_02\4&20975680&0&00E1
Driver: n/a

Name: SM Bus Controller
Device ID: PCI\VEN_8086&DEV_27DA&SUBSYS_200F17AA&REV_02\3&B1BFB68&0&FB
Driver: n/a

Name: Intel® PRO/1000 PL Network Connection
Device ID: PCI\VEN_8086&DEV_109A&SUBSYS_200117AA&REV_00\4&192AC53F&0&00E0
Driver: n/a

I'm going to try and get drivers for the adapters, but I'm baffled as to why it says I have no BIOS

EDIT:

Ok, list of issues as of yet:

Windows Installer cannot Start.
InstallShield cannot start, RPC Server cannot be found.
Skype will not start, same error as above.
Taskbar is all the way down and can't be dragged up.
Files on desktop cannot be dragged.
DxDiag shows no BIOS/Motherboard.
Task Manager show no user names on any processes besides the System process of which the user name is SYSTEM.
No Internet.

Gonna make a new thread.

This post has been edited by sausage: 22 March 2011 - 05:52 PM

A clean install...will provide a much easier place...from which to see exactly where the system problems lie.

Louis