Jump to content

Welcome Guest to Geeks to Go - Register now for FREE
Geeks To Go is a helpful hub, where thousands of friendly volunteers serve up answers and support. Get free advice from the experts. Feel free to browse the site as a guest. However, you must log in to reply to existing topics or start a new topic of your own, and enjoy all this forum has to offer. Additionally, if you can assist another member by sharing your knowledge, please post a reply! Best of all - Registration and all assistance, is FREE! Learn more about How it Works. Infected? Malware Cleaning Guide. What are you waiting for?
Create an Account Login to Account

BSOD+Event Viewer Error in both XP and Win7


  • Please log in to reply

#1
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
Hi all. I have been having random reboots on my windows xp box. I looked in the event logs, and saw the following error consistently
Error code 1000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804e662f.

I reformatted to win7, and almost immediately crashed again, then back to xp (full format rather than quick) and get it this morning.

Any ideas? I am about to run memtest. Box is pretty old, I just use it to serve media out within my house.

Thanks!

also get this error but not every time
Error code 0000004e, parameter1 0000008f, parameter2 0003a203, parameter3 0003a1fb, parameter4 00000000.

Edited by eb50, 07 June 2011 - 05:04 AM.

  • 0

Advertisement


#2
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
Error code 1000000a, parameter1 f740002b, parameter2 00000002, parameter3 00000001, parameter4 804e66a5.
  • 0

#3
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Run this please.
http://www.resplendence.com/whocrashed
Click the Analyse button, scroll down for the results and copy and paste them to your reply please, as they appear please on the report. Not as an attachment.

Edited by Macboatmaster, 07 June 2011 - 05:27 PM.

  • 0

#4
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
installed a replacement vid card and still getting freezes... thanks in advance...

System Information (local)
--------------------------------------------------------------------------------

computer name: SERVU
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINXP
CPU: AuthenticAMD AMD Athlon™ XP 2800+ AMD586, level: 6
1 logical processors, active mask: 1
RAM: 1610063872 total
VM: 2147352576, free: 2049409024



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINXP\Minidump

Crash dumps are enabled on your computer.


On Mon 6/13/2011 9:43:11 PM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini061311-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846)
Bugcheck code: 0x4E (0x8F, 0x530B3, 0x53153, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 6/13/2011 9:37:20 PM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini061311-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF6A5)
Bugcheck code: 0x1000000A (0xFFFFFFFFF740002B, 0x2, 0x1, 0xFFFFFFFF804E66A5)
Error: CUSTOM_ERROR
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 6/7/2011 10:24:13 PM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini061311-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFF76D665C, 0xFFFFFFFFF76D6358, 0xFFFFFFFF80502C1F)
Error: NTFS_FILE_SYSTEM
file path: C:\WINXP\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 6/7/2011 10:22:17 PM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini060711-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 6/7/2011 11:05:09 AM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini060711-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF6A5)
Bugcheck code: 0x1000000A (0xFFFFFFFFF740002B, 0x2, 0x1, 0xFFFFFFFF804E66A5)
Error: CUSTOM_ERROR
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 6/7/2011 10:57:15 AM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini060711-03.dmp
This was probably caused by the following module: parport.sys (parport+0xBD00)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINXP\system32\drivers\parport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Parallel Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 6/7/2011 10:51:54 AM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini060711-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 6/7/2011 10:22:44 AM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini060711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846)
Bugcheck code: 0x4E (0x8F, 0x3A203, 0x3A1FB, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 6/7/2011 2:11:21 AM GMT your computer crashed
crash dump file: C:\WINXP\Minidump\Mini060611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF62F)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804E662F)
Error: CUSTOM_ERROR
file path: C:\WINXP\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed
  • 0

#5
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
1. Did you run memtest
if not do so please
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS
  • Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
    This will enter you into the Bios\Cmos area.
    Find the Advanced area and click Enter
    Look for Boot Sequence or Boot Options and highlight that click Enter
    Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
    Change the second drive to the C or Main Drive
    Once that is done then click F10 to Save and Exit
    You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the "errors" line. If you see ANY errors, even one, most likely, you have bad RAM.


Also run a chkdsk /r.

That is go start, run and type
cmd
at the prompt in the window that opens type
chkdsk C: /r note space between chkdsk and C: and the C: and /r
agree to run on restart and do so.
When complete go start control panel administrative tools
Event Viewer, click application in left pane, in main window find winlogon entry, the first from the top
double click that entry, on the window that opens left click once on the double page symbol below the up and down arrow.
Then on the reply panel for your post, right click and paste.
Your chkdsk results will appear.

Also go start right click the my computer entry, click properties, click the hardware tab, click the device manager button and ensure you have no warnings against any entries in device manager.
click the view tab, click show hidden devices and then check again for any warnings.


After you have done that do this please
Here's how to use it to troubleshoot a driver problem:

  • Access the Run dialog box by pressing the [Windows]-R keyboard shortcut. or start and then run
  • In the Open text box, type the command Verifier.
  • On the Select A Task page, leave the default Create Standard Settings as-is.
  • On the next page, choose the Select Driver Name From A List.
In your case select this one first -parport.sys
5.Click Finish and then reboot the system.If the driver(s) that you selected are causing a problem,the system will halt and display a BSOD (Blue Screen OfDeath) along with an error message. If the selected drivers aren't the cause ofthe problem, the system will start up normally.

Then run again selecting firstly the none Microsoft drivers.

Keep in mind that once you enable the Driver VerifierManager it stays active until you disable it. To do so, follow these steps:

  • Access the Run dialog box by pressing the [Windows]-R keyboard shortcut.
  • In the Open text box, type the command Verifier /reset.

Edited by Macboatmaster, 13 June 2011 - 04:58 PM.

  • 0

#6
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
Running memtest now. I ran it earlier for8 hours and had no errors. Ill try again for 24 hours. Will post back. Thanks
  • 0

#7
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
If you have already done that and it found the ram you have installed and it passed after four or five complete passes. I would personally not bother again at this stage.
I would proceed as my post

I have just had another look at this and as you have completely reformatted installed 7 and still had the crash, presuming that the computer hardware etc can run 7 and then you go back to XP and still have the same errors, I tend to think we are looking at, despite what WHO CRASHED says, either a failing hard disk, or other faulty hardware.. As you have replaced the graphics, I would tend to be looking at the network and sound cards if not integrated on the motherboard.
I would if these are actual cards, (not integrated) take them out, I would also disconnect all, except monitor, keyboard and mouse.
I would then test.

Other aspects to try are a clean boot.
http://support.micro....com/kb/310353/
proceed with manual method and only as far as and including step 3 . Do not proceed step 4.


I am signing off now and will pick this up again about 1800 UK time it is now 0040.

Edited by Macboatmaster, 13 June 2011 - 05:40 PM.

  • 0

#8
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
I ran check disk against C: and the results came up clean (I couldnt paste before the machine would crash again).

I find it interesting that I can run memtest for hours, but windows no longer than probably 5 minutes.

I have several drives so I am running chkdsk on each of them. With my luck, the bad drive will be the 1.5tb with the most data on it.

I really appreciate your responses. I will keep plugging away.
  • 0

#9
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
I have a C, D, E, J, H, and I drives (none are optical). The H I J drives are mounted on an addon SATA card. I might try unplugging this next. Of course, while I type this, I have been up for probably 20 minutes. I did disable the parport.sys but I havent rebooted to disable it yet.



Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 69 unused index entries from index $SII of file 0x9.
Cleaning up 69 unused index entries from index $SDH of file 0x9.
Cleaning up 69 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

30724280 KB total disk space.
6760588 KB in 16188 files.
4904 KB in 1374 indexes.
0 KB in bad sectors.
93264 KB in use by the system.
65536 KB occupied by the log file.
23865524 KB available on disk.

4096 bytes in each allocation unit.
7681070 total allocation units on disk.
5966381 allocation units available on disk.

Internal Info:
c0 44 00 00 a6 44 00 00 0e 57 00 00 00 00 00 00 .D...D...W......
3e 07 00 00 00 00 00 00 f5 00 00 00 00 00 00 00 >...............
be aa 8c 00 00 00 00 00 62 a6 ec 0a 00 00 00 00 ........b.......
7a 1e c1 00 00 00 00 00 06 39 3e 78 00 00 00 00 z........9>x....
f6 9e 01 dc 00 00 00 00 92 14 22 68 01 00 00 00 .........."h....
99 9e 36 00 00 00 00 00 78 3d 07 00 3c 3f 00 00 ..6.....x=..<?..
00 00 00 00 00 30 a2 9c 01 00 00 00 5e 05 00 00 .....0......^...

Checking file system on H:
The type of the file system is NTFS.
Volume label is Movie Backup.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Windows has checked the file system and found no problems.

488384000 KB total disk space.
121484028 KB in 12795 files.
7608 KB in 914 indexes.
0 KB in bad sectors.
95104 KB in use by the system.
65536 KB occupied by the log file.
366797260 KB available on disk.

4096 bytes in each allocation unit.
122096000 total allocation units on disk.
91699315 allocation units available on disk.

Internal Info:
a0 35 00 00 99 35 00 00 c7 69 00 00 00 00 00 00 .5...5...i......
8c 03 00 00 00 00 00 00 0f 00 00 00 00 00 00 00 ................
0a e6 87 00 00 00 00 00 f0 06 6e 1d 00 00 00 00 ..........n.....
6a c0 61 00 00 00 00 00 8e 73 22 f1 03 00 00 00 j.a......s".....
64 ad 73 6c 0e 00 00 00 4e 5a 16 84 12 00 00 00 d.sl....NZ......
99 9e 36 00 00 00 00 00 80 3f 07 00 fb 31 00 00 ..6......?...1..
00 00 00 00 00 f0 cb f6 1c 00 00 00 92 03 00 00 ................


I did look through the previous winlogons and found the following (i blue screen every 5 minutes so there are lots of reboots)

Checking file system on H:
The type of the file system is NTFS.
Volume label is Movie Backup.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The record length 0x288 is too large for attribute of type 0x400
and instance tag 0x0 in file 0x323b. The maximum value is 0x324ed000.
Truncating badly linked attribute records
from file record segment 1500.
The record length of attribute of type 0x4000 and instance tag 0x0
in file 0x6a6 should not be zero.
Truncating badly linked attribute records
from file record segment 1702.
The record length 0x1cc2491 of attribute of type 0xeb1f7c0e and
instance tag 0x3 in file 0xf85 is not aligned.
Truncating badly linked attribute records
from file record segment 3973.
The VCN 0x30020c00000000 of index $I30 in file 0x3e6 is already in use.
Correcting error in index $I30 for file 998.
The index bitmap $I30 in file 0x3e6 is incorrect.
Correcting error in index $I30 for file 998.
The down pointer of current index entry with length 0x78 is invalid.
f0 03 00 00 00 00 04 00 78 00 5a 00 01 00 00 00 ........x.Z.....
e6 03 00 00 00 00 04 00 6a 4c 64 43 91 24 cc 01 ........jLdC.$..
00 99 ec bb 4b 0f cb 01 06 40 bc 56 31 d0 cb 01 ....K....@.V1...
80 22 9b 43 91 24 cc 01 00 60 4b 00 00 00 00 00 .".C.$...`K.....
8e 53 4b 00 00 00 00 00 20 00 00 00 00 00 00 00 .SK..... .......
0c 02 30 00 35 00 2d 00 50 00 4c 00 49 00 7e 00 ..0.5.-.P.L.I.~.
31 00 2e 00 00 00 00 00 00 00 00 00 01 00 00 00 1...............
ff ff ff ff ff ff ff ff 35 00 2d 00 50 00 4c 00 ........5.-.P.L.
18 00 00 00 03 00 00 00 01 00 00 00 00 00 00 00 ................
Sorting index $I30 in file 998.
The index bitmap for index $I30 in file 0x5dc is invalid or missing.
The index bitmap for index $I30 in file 0x5dc is invalid or missing.
Correcting error in index $I30 for file 1500.
The down pointer of current index entry with length 0x78 is invalid.
f1 05 00 00 00 00 07 00 78 00 5a 00 01 00 00 00 ........x.Z.....
dc 05 00 00 00 00 03 00 d0 c8 8a 58 91 24 cc 01 ...........X.$..
00 ab d0 44 2c aa cb 01 2e 17 75 e0 30 d0 cb 01 ...D,.....u.0...
fa 3d a0 58 91 24 cc 01 00 90 63 00 00 00 00 00 .=.X.$....c.....
ef 84 63 00 00 00 00 00 20 00 00 00 00 00 00 00 ..c..... .......
0c 02 30 00 33 00 2d 00 4a 00 41 00 4d 00 7e 00 ..0.3.-.J.A.M.~.
31 00 2e 00 4d 00 50 00 33 00 00 00 00 00 00 00 1...M.P.3.......
ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00 ................
18 00 00 00 03 00 00 00 ff ff ff ff ff ff ff ff ................
Sorting index $I30 in file 1500.
The index bitmap for index $I30 in file 0x6a6 is invalid or missing.
Correcting error in index $I30 for file 1702.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff da 9d 2f 66 91 24 cc 01 ........../f.$..
00 7a cd 46 33 f9 ca 01 0c db 38 32 33 d0 cb 01 .z.F3.....823...
Sorting index $I30 in file 1702.
Unable to locate the file name attribute of index entry 05-PLI~1.
of index $I30 with parent 0x3e6 in file 0x3f0.
Deleting index entry 05-PLI~1. in index $I30 of file 998.
Unable to locate the file name attribute of index entry 16-obie_trice-never_forget_ya-esc.mp3
of index $I30 with parent 0xf6f in file 0xf85.
Deleting index entry 16-obie_trice-never_forget_ya-esc.mp3 in index $I30 of file 3951.
Unable to locate the file name attribute of index entry 16-OBI~1.MP3
of index $I30 with parent 0xf6f in file 0xf85.
Deleting index entry 16-OBI~1.MP3 in index $I30 of file 3951.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file ... WHOLE bunch of these... directory file 1702.
Cleaning up 9 unused index entries from index $SII of file 0x9.
Cleaning up 9 unused index entries from index $SDH of file 0x9.
Cleaning up 9 unused security descriptors.
Inserting data attribute into file 3973.
CHKDSK is verifying Usn Journal...
The USN Journal length 0xe20 in file 0x3596 is less the
largest USN encountered, 0x1cc2491eb1f7c0e, plus eight in file 0xf85.
Repairing Usn Journal $J data stream.
CHKDSK is resetting Usn information...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

Checking file system on I:
The type of the file system is NTFS.
Volume label is Video.

***********

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The first index entry offset, 0x40000, for index $I30 in file 0x4fd
points beyond the length, 0x28, of the index. VCN is unknown.
Removing corrupt index $I30 in file 1277.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Inserting data attribute into file 1277.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

488384000 KB total disk space.
458653788 KB in 9370 files.
3652 KB in 904 indexes.
0 KB in bad sectors.
97104 KB in use by the system.
65536 KB occupied by the log file.
29629456 KB available on disk.

4096 bytes in each allocation unit.
122096000 total allocation units on disk.
7407364 allocation units available on disk.

Internal Info:
70 3d 00 00 2d 28 00 00 85 42 00 00 00 00 00 00 p=..-(...B......
15 00 00 00 00 00 00 00 13 00 00 00 00 00 00 00 ................
68 b6 3a 01 00 00 00 00 f2 f4 46 0e 00 00 00 00 h.:.......F.....
48 fa 7b 00 00 00 00 00 00 00 00 00 00 00 00 00 H.{.............
00 00 00 00 00 00 00 00 ac c6 dd 18 00 00 00 00 ................
99 9e 36 00 00 00 00 00 70 41 07 00 9a 24 00 00 ..6.....pA...$..
00 00 00 00 00 70 01 5a 6d 00 00 00 88 03 00 00 .....p.Zm.......
  • 0

#10
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Well clearly the file system on drive H was not good.

However of course you will have seen that drive C is OK

I would continue with the driver verifier

I would also try the clean boot

I also opine that you should run system file checker on windows.
That is sfc /scannow

It may well ask for the XP CD.
In view of the fact that it is a new installation I do not expect many errors on the system files.
Memtest will not of course access the data on the other drives but windows, will of course.
I think you may be on the correct lines with disconnecting those other drives. and running simply on C drive.
  • 0
<

Advertisement


#11
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
in addition to what Macboatmaster advised you to do

how old and how big is your power supply...with that many drives you may well be at the max it can supply power to...

I suggest you try this...

The H I J drives are mounted on an addon SATA card. I might try unplugging this next.


unplug from the wall and remove the PCI card...
clean out the CPU heatsink fins and dust bunnies/rhinos real good...plug into wall again
work the system for awhile and let us know how it goes
  • 0

#12
eb50

eb50

    Member

  • Member
  • PipPip
  • 12 posts
disabled parport.sys and still got BSOD.

interestingly, i left my machine at home on all day and it was fine. started using it, and within minutes died.

i unplugged my pci card connecting all my sata drives.

ill have to pull out the psu to see how old it is. not more than 3 years. i bought a few of those antec green earth PSUs a while back.

see what happens.
  • 0

#13
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts

left my machine at home on all day and it was fine. started using it, and within minutes died.

On all day, but no demand on the PSU or no request to write to ram etc.

Have you tried that clean boot.
Also if it still crashes then, go back normal statrtup, as per the link - I sent you, for the clean boot.
Restart the computer for that to take effect.

Then reboot again and on F8 select Safe Mode.
See if it still crashes.

Edited by Macboatmaster, 14 June 2011 - 04:12 PM.

  • 0

#14
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
Do not attempt to boot into Safe Mode using MSCONFIG

Using MSConfig to access (force) safe mode with the /Safe boot option could
render your computer unbootable. The Safeboot option modifies the Boot.ini
file by adding the /safeboot:minimal argument to your operating systems
startup line. Some types of malware can delete or alter the safeboot key in
the registry resulting in the inability to reboot fully into safe mode or
back to normal mode. When this occurs, you may be locked in a continuous
reboot loop afterwards where you cannot get back to MSConfig and undo your
selection until the /safeboot argument is removed from the boot.ini....


this is the fix if you have already done it and stuck in the loop...

. What you will need to do is boot with an XP disk and go into recovery console. This will put you into a Command Prompt window. From here you will be able to edit the boot.ini to remove the Safe Mode switch.

Here is a link with instructions about booting to recovery console: http://support.microsoft.com/kb/314058

From the command prompt type "edit boot.ini" and press enter. This will take you into the editor for the boot.ini. Below is a print out of boot.ini with Safe Mode and without Safe Mode switch.

Boot.ini with Safe Mode switch
[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" /noexecute=optin /fastdetect /safeboot:minimal

Boot.ini without Safe Mode switch
[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" /noexecute=optin /fastdetect
  • 0

#15
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
eb50

Happyrock`s post 14 is because I badly worded my post 13. It would have been read as effecting a Safe Mode boot via msconfig.
Entirely my fault.

Happrock
Thanks. Sorry.
  • 0

Advertisement




Similar Topics: BSOD+Event Viewer Error in both XP and Win7     x


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

featured