Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows Blue Screen of death

Status
Not open for further replies.
kjv1611

kjv1611

New member
Jul 9, 2003
10,758
US
I recently built a machine with these specs:
Case/Power Supply: Antec Sonata w/built-in 380 Watt PS
Mobo: Asus A8V Deluxe
Memory: 2 x 256MB DDR400 - Kingston
Processor: Amd Athlon 64 3000
Video Card: Asus V9520-X/TD-128 DDR 8X (GForce FX 5200)
Sound: built in
Wireless network: Linksys wireless PCI card on this on this computer.
Western Digital 80 GB Parallel 7200 8mb cache drive.
Liteon 16X DVD-Rom
OS: Windows XP Pro

Now, these errors did not happen once at my house, nor at the house where I took the machine until after a good while after Quickbooks 2004 Pro and the Microsoft Intellimouse drivers were installed. At that point, it happened a couple of times, seemed somewhat random. I later looked at the machine, and it SEEMED like it happened more when there was network activity between this and the other computer. Though, yesterday it did not happen at all, and today, the friend called me, and it happened twice right off.

The blue screen basically says:
Microsoft has shut down your machine to protect it from damage b/c of serious errors.

Technical details:
Stop At:
0X0000009C (0X00000004, 0X80545FF0, 0XB2000000, 0X00070F0F)
Click to expand...

Just a couple of other notes I've thought to mention, just to see if anyone can guess it's a bad board:
1.) I noticed that I could not get the wireless network card to work on the last pci slot, but a couple of slots up, it worked fine.
2.) I also noticed that the computer did not read a printer on the LPT1 port, though it was hooked up through a parallel cable directly to the motherboard, but worked fine when hooked through USB.
3.) I was getting keyboard errors with one keyboard, but not with any others, so I assumed it was the keyboard.
4.) One monitor did not work appropriately with the board, but 2 other monitors have worked fine. (the one was too dark, and the screen fuzzy.

Anyway, if anyone has any idea(s) on this, please let me know, b/c I'd like to get this fixed for my friend ASAP.

I've not encountered this before with new equipment, only old equipment.

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Sort by date Sort by votes
Also, this may look a little better if I post it this way, instead of in a "quote" frame:
Code: 
Microsoft has shut down your machine to protect it from damage b/c of serious errors.

Technical details:
Stop At:
0X0000009C (0X00000004, 0X80545FF0, 0XB2000000, 0X00070F0F)

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Or, if anyone knows of any freeware software that detects problems, such as hardware problems, and then prints a report (out to a text or html doc, or something). I was thinking I'd seen something like that, but was unsure.

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Thanks for that link. It references the problem, but basically just tells that the processor tells Windows to do that, but then just says that basically any problem with your machine can cause this error. So, I'll keep searching. In the mean time, I'm attempting to fill out a form for Asus tek support, to see if they have any further specifics. Thanks for the link, though.

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Got another question at ya: Perhaps you are using XP PRO with SP2???? if so, go to the BOOT.INI file (the startup file on drive C:) there is a entry "/NoExecute=xxxx" delete this and only this...



Ben

If it works don't fix it! If it doesn't use a sledgehammer...
 
Upvote 0 Downvote
Can you un-install the Intellimouse and try a normal mouse? This can start narrowing it down.
 
Upvote 0 Downvote
Hmm, Ben, that may very well be it, b/c it is XP Pro, and SP2 is installed. So, are you talking about going to Run, then msconfig, and uncheck it in startup, or in the services, or in registry? I can try whichever it is, if that's the case, that will be an easy fix!
If not, I can go ahead and uninstall the mouse drivers, and will be doing so anyway within a week most likely, b/c have a logitech MX700 duo in transit now which will replace it.

By the way, a note here, if anyone is looking for a Logitec MX Duo cheap, then go to - they have it for $50, and free shipping right now. I can vouch for their products, based on my experience - I've never gotten a bad product there, and that's saying a lot, since most of their stuff is refurbished.

Anyway, thanks for both posts, and I'll post back when get it finished to let all know what finally fixed the issue. I'm guessing that the startup deal very well could be it, b/c now that I think about it, I had not installed SP2 on that machine until not long before those errors began occuring. I know that it isn't the temps for the CPU and/or case, so long as the BIOS is correct, b/c frankly, I wish my computer at home had the same kind of temps it's showing there. There is only one 120mm fan in the rear of the case, the fan(s) in the power supply, and the standard heatsink/fan for the AMD Athlon 64.

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Yeah, you're on the right track. Just remember that before you assume it's a hardware issue, rule out all software possibilities first. In other words, throw another spare drive in, format it, and add a clean installation of XP to it using it as the primary drive.

If the problem is not easy to duplicate, that may not be the best method to use for troubleshooting. But you get the idea - work your way back to the starting point when things were calm. It may take some time, but is cheaper than wasting money on a new board...


~cdogg
[tab]"All paid jobs absorb and degrade the mind";
[tab][tab]- Aristotle
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884
 
Upvote 0 Downvote
No discrepencies there - cheaper than new board. I'm really hoping at this point that simply stopping the service mentioned from running will be the fix, as that would be the quickest/easiest fix. Only thing I wonder, is why it would cause problems on some machines and not others. I guess that's just the way it is. [smile]

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Hi there,

you can take a look at the Boot.INI with MSCONFIG (at least on my PC you can't change it there), to change it you have to Right Click on 'My Computer' (or in the Control Panel double click on System) then go to Extended, then look at the SystemStart, there you can edit the BOOT.INI file using Notepad/Editor....

the 'NoExecute=OptIn/OptOut' and "Execute" in SP2, is to enable the Software Emulation of the Buffer Overflow Protection for 32-Bit CPU's and/or to enable WinXP to use the Hardware version of the Buffer Overflow that is inherit in the 64-Bit AMD's... On some systems this can cause Software problems with Drivers and Applications...



Ben

If it works don't fix it! If it doesn't use a sledgehammer...
 
Upvote 0 Downvote
Thanks for the detail there, that helps to understand the problem a little better. In that case, it could very well be b/c of Quickbooks having problems with that setting, b/c that is the only difference in the two machines (other than microsoft vs. logitech mouse). I'll be getting over there sometime in the next couple days, and I'll look at that file then. Of course, I'll make a backup of the file first! [wink]

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Once I've attempted to resolve the issue, I will post back, but understand, it might not be until early next week.

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Um, I thought I already put this, but basically, I tried the fix by BigBadBen, but problem still persists.

Here is what I now have in the boot.ini file:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect



and another note since I previously had posted this... weird..

It seems that this occurs when there is any activity on the network. Can't verify for sure yet, but that is what it seems like. Could that mean that it is the wireless network card, or the Norton Firewall causing the issue?

Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
Basically, I had already posted once, but it did not go through correctly, apparently, but it all boils down to this: I made the change as suggested, but it did not fix the problem. Also, I installed Quickbooks (was the only software difference) on the other computer, but no problems were found on that machine after the install.

Also, when I tried to conact Asus tech support, the support person just closed the case, and said it was a windows problem, and not the motherboard. Is it possible that something just did not get installed correctly with Windows, and that caused the problem? If so, it would probably be less time consuming to just reinstall Windows and other software as apposed to sending the Mobo back for replacement (if it is the Mobo). Or, could it be caused by some other hardware malfunction?

The reason I keep going back to the possibility that it is the motherboard is that I've ended up noticing a few other issues: the connection type issues I posted earlier, and just yesterday, the friend who owns the machine could not get files to save to the floppy drive correctly, though it worked fine before when I used it. I really can't quite figure it out. I do know for sure that when there is network activity, such as the other computer trying to access the shared drive, the thing crashes, and gives the blue screen. The only problem is that is not the only time that happens, just that it does happen 100% of the time that someone attempts to use the network to browse files.

Anyway, if anyone has any other advice and/or words of wisdom, I'm all ears. Though I hate the possibility, it is looking to me to be a bad board, but again, if anyone else has a valid reason to point to that it may not be, I'd be glad to try whatever tests you offer.



Stephen [infinity]
"Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me." John 14:6 KJV
 
Upvote 0 Downvote
That link bcastner posted has some excellent suggestions to check and double-check, even if they were already suggested.

In addition, another thought would be to swap out the NIC for another brand/model. It's cheap and probably the least time consuming.


~cdogg
[tab]"All paid jobs absorb and degrade the mind";
[tab][tab]- Aristotle
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884
 
Upvote 0 Downvote
Most likley its the motherboard,cpu,or power supply.Blue screens are a hardware problem.Check the voltage on your power supply your motherboard or cpu maynot be getting the correct voltage,too much voltage will damage the motherboard and cpu.This is what the blue screen trys to stop.
 
Upvote 0 Downvote
rakermc,

My life would be easier if, as you stated, "Blue screens are a hardware problem."

This is unfortunately not true.

Bill Castner
 
Upvote 0 Downvote
kjv1611,

I just realized that you said the blue screen appears "[blue]100% of the time that someone attempts to use the network to browse files[/blue]"

Since you are not sure at this point whether the problem is hardware or software, I think you should try my first suggestion:

--> Throw in another drive with a fresh install of Windows XP SP2. Make it the primary boot drive and don't worry about installing all the individual apps (to save time). Just try to reproduce the blue screen while accessing the network. If it still occurs, it is likely a hardware issue.

We can go from there![tab][wink]


~cdogg
[tab]"All paid jobs absorb and degrade the mind";
[tab][tab]- Aristotle
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

T3kk
  • Locked
  • Question
Logitech camera C920 used with Windows 10 Pro 22H2
Replies
0
Views
925
T3kk
T3kk
T3kk
  • Locked
  • Question
UX Volume visual no longer showing on screen when the Volume button is pressed on headset 2
Replies
4
Views
1K
Scott24x7
Scott24x7
DrB0b
  • Locked
  • Question
Looking for a LAN Messenger-eque program that runs on Windows CE
Replies
0
Views
302
DrB0b
DrB0b
Sebastian42
  • Locked
  • Question
Preventing Windows Explorer from going 'not responding'
Replies
2
Views
307
Sebastian42
Sebastian42
Brian_85
  • Locked
  • Question
Why number "10" character appear on the top,left corner of my printout of Panasonic KX-P11
Replies
3
Views
425
misseditbythatmuch
misseditbythatmuch

Part and Inventory Search

Sponsor

Back
Top