Blue screen of death on XP!?!
#1
Scooby Regular
Thread Starter
iTrader: (1)
Join Date: Oct 2005
Location: Here and at work...
Posts: 298
Likes: 0
Received 0 Likes
on
0 Posts
Blue screen of death on XP!?!
Hi guys,ive just upgraded my pc to a newer spec:
3.0Gb AMD Athlon 64 XP
Asus A8N-SE SLI motherboard
Geforce 7600 GT sli pci-e graphics card
2 x 256 DDR400 3200 ram (this is original ram used from last pc)
160Gb Maxtor sata 7200 hard drive (running windows xp pro)
120Gb Seagate IDE 7200 hard drive (used for storing music,videos,games)
All latest drivers are installed!
My question is when im downloading from the internet,the computer produces a blue screen and then restarts,then windows reloads and says its just recovered from an serious error . Other than that there's no problem surfing the internet and playing games.
Im on an ethernet connection using 2meg broadband (NTL).
Any ideas welcome
3.0Gb AMD Athlon 64 XP
Asus A8N-SE SLI motherboard
Geforce 7600 GT sli pci-e graphics card
2 x 256 DDR400 3200 ram (this is original ram used from last pc)
160Gb Maxtor sata 7200 hard drive (running windows xp pro)
120Gb Seagate IDE 7200 hard drive (used for storing music,videos,games)
All latest drivers are installed!
My question is when im downloading from the internet,the computer produces a blue screen and then restarts,then windows reloads and says its just recovered from an serious error . Other than that there's no problem surfing the internet and playing games.
Im on an ethernet connection using 2meg broadband (NTL).
Any ideas welcome
#2
Scooby Regular
Join Date: Dec 2005
Location: Hertfordshire
Posts: 280
Likes: 0
Received 0 Likes
on
0 Posts
I had a similar problem with the built in network card on my K8S-MX Asus motherboard (SIS chipset). Used to crash (blue screen) when using torrents and also if attaching large files to emails through hotmail. I upgraded to the latest driver for the network (beta version I think) and the problem went away.
#4
Scooby Regular
Thread Starter
iTrader: (1)
Join Date: Oct 2005
Location: Here and at work...
Posts: 298
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Iain Young
What is the error message you get on the blue screen?
#6
Scooby Regular
Join Date: Sep 1999
Location: Swindon, Wiltshire Xbox Gamertag: Gutgouger
Posts: 6,956
Likes: 0
Received 0 Likes
on
0 Posts
Does sound like it's either a hardware problem, or a driver issue. I've got the same motherboard (with the latest drivers from Asus), and have no problems with it.
To see the error message...
1) Right click on "My computer"
2) Select the advanced tab
3) Press the settings button in the "Startup and recovery" section
4) Remove the tick in the checkbox labelled "Automatically restart" in the system failure section.
To see the error message...
1) Right click on "My computer"
2) Select the advanced tab
3) Press the settings button in the "Startup and recovery" section
4) Remove the tick in the checkbox labelled "Automatically restart" in the system failure section.
Trending Topics
#10
Scooby Regular
Join Date: Jun 2006
Location: Coruscant, Imperial City, block 1138, Apt 12
Posts: 61
Likes: 0
Received 0 Likes
on
0 Posts
One thing you can try if you're getting intermittent crashes is to check the Event viewer.
Control Panel --> Admin Tools --> Event Viewer
And click on the "System" section. *Possibly* you might see some big fat red X's in there which might/hopefully correspond to the times of your crashes or, obviously, just before hand. It's doubtful they will *be* your crash reasons but perhaps something that leads to them..?
Sadly tho, bad error handling in the Windows OS means exceptions are not caught and your get your BSODs.
I had a similar issue some time ago and it turned out there was an IRQ_LESS_THAN_ZERO stop error, which from looking at the event logs, lead me to find it was a vid driver issue -- not that this is necessarily your issue.
Control Panel --> Admin Tools --> Event Viewer
And click on the "System" section. *Possibly* you might see some big fat red X's in there which might/hopefully correspond to the times of your crashes or, obviously, just before hand. It's doubtful they will *be* your crash reasons but perhaps something that leads to them..?
Sadly tho, bad error handling in the Windows OS means exceptions are not caught and your get your BSODs.
I had a similar issue some time ago and it turned out there was an IRQ_LESS_THAN_ZERO stop error, which from looking at the event logs, lead me to find it was a vid driver issue -- not that this is necessarily your issue.
#12
Scooby Regular
Thread Starter
iTrader: (1)
Join Date: Oct 2005
Location: Here and at work...
Posts: 298
Likes: 0
Received 0 Likes
on
0 Posts
Right guys had a look at your reply's which have been very helpful . Stopped the computer restarting from another crash and it says:
DRIVER_IRQL_NOT_LESS_OR_EQUAL and it also shows a file name: NVTCP.SYS
I cleared the event log before the system crash and it lists an error category 102 and event 1003 - user N/A!?!
Microsoft support center shows the error below:
Product:Windows Operating SystemEvent ID:1003Source:System ErrorVersion:5.2Symbolic Name:ER_KRNLCRASH_LOGMessage:Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5.
So can any of you tech heads out there can pin point to whats causing it? Ive asked a few lads at work and some ideas are: Faulty memory or memory not compatiable with new m/board, or m/board bios needs flashing with new drivers.
DRIVER_IRQL_NOT_LESS_OR_EQUAL and it also shows a file name: NVTCP.SYS
I cleared the event log before the system crash and it lists an error category 102 and event 1003 - user N/A!?!
Microsoft support center shows the error below:
Product:Windows Operating SystemEvent ID:1003Source:System ErrorVersion:5.2Symbolic Name:ER_KRNLCRASH_LOGMessage:Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5.
So can any of you tech heads out there can pin point to whats causing it? Ive asked a few lads at work and some ideas are: Faulty memory or memory not compatiable with new m/board, or m/board bios needs flashing with new drivers.
#13
Doing a google search on this shows a lot of other people are having the same problem. Here is something one guy tried to solve the issue:
http://www.planetamd64.com/lofiversi...php/t7473.html
Looks like an issue with the Nvidia Drivers. and Firewall.
http://www.planetamd64.com/lofiversi...php/t7473.html
Looks like an issue with the Nvidia Drivers. and Firewall.
#14
Scooby Regular
iTrader: (1)
DRIVER_IRQL_NOT_LESS_OR_EQUAL is one of the worst BSODs to get, as it can mean many things, and not necessarily what you think it should be from the driver quoted. But having said that I would try reinstalling your nforce drivers, or trying a previous version of the nforce drivers maybe first. If that doesnt help then remove the NAM driver (NAM = Network Access Manager). This is the nforce firewall, as has well known issues, causing BSODs, especially in P2P/Torrent applications.
hehe snap jpor
hehe snap jpor
#15
Scooby Regular
iTrader: (5)
Join Date: Feb 2003
Location: Worcester
Posts: 2,625
Likes: 0
Received 0 Likes
on
0 Posts
looks like a nic problem
edit snap above... we all googled http://forum.abit-usa.com/archive/in...p/t-84419.html
edit snap above... we all googled http://forum.abit-usa.com/archive/in...p/t-84419.html
#18
Scooby Regular
Join Date: Sep 1999
Location: Swindon, Wiltshire Xbox Gamertag: Gutgouger
Posts: 6,956
Likes: 0
Received 0 Likes
on
0 Posts
Ah, I remember hearing about this. In most cases the best solution is to remove the nvidia drivers for the firewall etc, and just use the standard windows xp / intel drivers instead. That's what I'm using on mine and it's rock solid. I did briefly try the nforce drivers (to give the hardware firewall a go), but I never managed to get it working. Didn't get any blue screens, but it crippled my network connections...
#19
Scooby Regular
Join Date: Jun 2006
Location: Coruscant, Imperial City, block 1138, Apt 12
Posts: 61
Likes: 0
Received 0 Likes
on
0 Posts
Ah yes - Nvidia "extras"
basically when I install Nvidia drivers, especially the nforce ones, I try and install *only* the drivers I want by installing via the "Update Driver" way rather than running the "install.exe" file.
After installing the vid drivers, I always hit the registry and remove all "nv*.exe" and "nv*.dll" calls in the ../M$/Windows/CurrentVersion/Run areas so they don't load on startup - they only slow things down and result in a fuct up machine - from my experience anywaze.
But yes - Stop errors - one of the lowest and worst errors as most often they are red herrings for a long time
M$ - why cant you handle your exceptions correctly?? It isn't *that* hard!
basically when I install Nvidia drivers, especially the nforce ones, I try and install *only* the drivers I want by installing via the "Update Driver" way rather than running the "install.exe" file.
After installing the vid drivers, I always hit the registry and remove all "nv*.exe" and "nv*.dll" calls in the ../M$/Windows/CurrentVersion/Run areas so they don't load on startup - they only slow things down and result in a fuct up machine - from my experience anywaze.
But yes - Stop errors - one of the lowest and worst errors as most often they are red herrings for a long time
M$ - why cant you handle your exceptions correctly?? It isn't *that* hard!
#20
Scooby Regular
Thread Starter
iTrader: (1)
Join Date: Oct 2005
Location: Here and at work...
Posts: 298
Likes: 0
Received 0 Likes
on
0 Posts
Well guys,i removed the nvidia NAM drivers and now its spot on .I was running the nvidia firewall and my god it was slower than my old 56k modem! So now im running the windows drivers and firewall!
So i BIG thank you to all who helped in this thread
Top marks!!!!!!
So i BIG thank you to all who helped in this thread
Top marks!!!!!!
Thread
Thread Starter
Forum
Replies
Last Post
Pro-Line Motorsport
Car Parts For Sale
2
29 September 2015 07:36 PM