Edited by cmislin, 23 January 2014 - 05:19 PM.
BSOD Windows XP
Started by
cmislin
, Sep 30 2013 05:55 PM
#421
Posted 23 January 2014 - 02:23 PM
#422
Posted 23 January 2014 - 07:54 PM
Double checked settings on mb for fsb booted it up BSOD then rebooted drive not showing. Powered down checked connectors and then it booted up. No report could be pulled for BSOD. I ran that program ya asked for about chip and motherboard. I not 100% how to interpret it but there it is.
Attached Files
Edited by cmislin, 23 January 2014 - 07:55 PM.
#423
Posted 24 January 2014 - 12:35 AM
another BSOD nothing can be received from whocrash or bluescreenviewr but wrote this down. Kernal in page error and the error was on atapi.sys
#424
Posted 24 January 2014 - 01:05 AM
after typing that last msg another BSOD this time no error msg or error code like a generic BSOD.
#425
Posted 24 January 2014 - 01:21 AM
Make that 2x BSOD not file error or what not just a address code (the address code was there for the previous one as well)
#426
Posted 24 January 2014 - 07:59 AM
Gday.
Did you put the RAM in the empty slots, or move them around?
Did you change the switches on the MB?
Did you put the RAM in the empty slots, or move them around?
Did you change the switches on the MB?
#427
Posted 24 January 2014 - 02:27 PM
The ram is the same earliest ram we left in there while testing and the fsb switches I double checked are on default. Also sometimes during bootup it wouldn't detect my hard drive in bios.
#428
Posted 24 January 2014 - 05:53 PM
Not good news.
There may be an intermittent hardware fault that does not show up when testing. It may be time to take it into a repair shop, if you think it worth the cost, as we appear to have run out of things to try.
Edit.
Lets see if altering those MB switches stabilize the system.
Turn off the PSU before altering the switches.
Set the switches on the first configuration to the right of defaults and then test. Then the next configuration and test. Keep going to the last one.
There may be an intermittent hardware fault that does not show up when testing. It may be time to take it into a repair shop, if you think it worth the cost, as we appear to have run out of things to try.
Edit.
Lets see if altering those MB switches stabilize the system.
Turn off the PSU before altering the switches.
Set the switches on the first configuration to the right of defaults and then test. Then the next configuration and test. Keep going to the last one.
#429
Posted 24 January 2014 - 06:27 PM
How long should I test it for?
#430
Posted 24 January 2014 - 07:44 PM
Ten minutes should be enough, you just need to stress the system. Open a browser, look for any U tube long video, and play, run windows update, start playing a game.
Or, you could do a proper job by following this tutorial, Please excuse the title.
> http://www.pcworld.c...c-hardware.html
Or, you could do a proper job by following this tutorial, Please excuse the title.
> http://www.pcworld.c...c-hardware.html
#431
Posted 24 January 2014 - 08:03 PM
Yeah funny thing never had any of that stuff show anything at all. Seems to be most of my faults happen just given time.
#432
Posted 25 January 2014 - 12:27 AM
next setting just browser open and windows update going another BSOD but only address code no file name associated. Checking for bluescreen viewer and such. Yep nothing in bluescreenviewer and whocrash.
Edited by cmislin, 25 January 2014 - 12:41 AM.
#433
Posted 25 January 2014 - 01:44 AM
While stressing, monitor your temps/volts, see if they spike before a BSOD.
#434
Posted 25 January 2014 - 01:48 AM
with that cpu type program or install one?
#435
Posted 25 January 2014 - 04:21 AM
Please excuse me for being late on parade folks
Not sure if any of the following have already been tried but here are a couple of checks for you to do cmislin
Try disabling the auto reboot after system failure option, this may allow you to view any messages that could be flashing past that quick that you don`t see them.
Right Click on My Computer and select Properties
Click on the Advanced tab
Under the Startup and Recovery section, click on Settings
Under the System Failure section, remove the check mark in the box next to Automatically Restart
Click OK twice to complete the process
Use the computer as you have been doing and check for error messages if the system crashes.
Next run driver verifier to check out the atapi.sys driver that you mentioned in your reply #423 (wow).
1.Click Start
2.Click Run…
3.Type CMD and press Enter
4.In the new box, type verifier and press Enter
The Driver Verifier Manager utility will open up;
Select the Create standard list option.
In the next screen you can choose to auto select a driver or select from a list, please choose the select from a list option and then place a tick in the atapi.sys box, restart the computer and see if this causes the system to crash.
To disable driver verifier when done go to start, run and type in verifier /reset
Click on OK and you`re done.
Not sure if any of the following have already been tried but here are a couple of checks for you to do cmislin
Try disabling the auto reboot after system failure option, this may allow you to view any messages that could be flashing past that quick that you don`t see them.
Right Click on My Computer and select Properties
Click on the Advanced tab
Under the Startup and Recovery section, click on Settings
Under the System Failure section, remove the check mark in the box next to Automatically Restart
Click OK twice to complete the process
Use the computer as you have been doing and check for error messages if the system crashes.
Next run driver verifier to check out the atapi.sys driver that you mentioned in your reply #423 (wow).
1.Click Start
2.Click Run…
3.Type CMD and press Enter
4.In the new box, type verifier and press Enter
The Driver Verifier Manager utility will open up;
Select the Create standard list option.
In the next screen you can choose to auto select a driver or select from a list, please choose the select from a list option and then place a tick in the atapi.sys box, restart the computer and see if this causes the system to crash.
To disable driver verifier when done go to start, run and type in verifier /reset
Click on OK and you`re done.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users