Tech Support Forum banner
Status
Not open for further replies.
1 - 12 of 12 Posts

· Registered
Joined
·
1,184 Posts
Discussion Starter · #1 ·
Just randomly a few days ago I got this BSOD. I did a little research but couldn't find much helpful information. I have been getting this error in XP. I have both XP and Vista on the same HD and have been able to run Vista just fine so I feel that it is not hardware related.

I have run various chkdsk and sfc /scannow. The chkdsk has never shown any errors, but I believe the sfc may have fixed a few things. Though I have still gotten the error. I have scanned for virus' and spyware. Really not sure. Any help or suggestions would be great.
 

· Networking Team |Tech
Joined
·
4,122 Posts
Hi ukbsktbll,

Another thing you can do is to perform a "Windows Repair" on the Windows XP side. You will definitely need your Windows XP CD to perform a windows repair. Hopefully everything will work out for you.
 

· Global Moderator
Using Google to solve problems
Joined
·
45,006 Posts
Your last Dump files for 4-1-11 were corrupted an unreadable. The other dump files were from 2010
Kernel stack inpage error Stop 0x77 is caused by a bad block in a paging file, or a disk controller error. You could have bad sectors in your Paging File, (Which Check Disk should have fixed) or you have bad RAM.
Download the ISO image for memtest and burn the image to a CD using IMGBurn and boot off of the newly created CD and run the tests with one stick of RAM in at a time.
 

· Registered
Joined
·
1,931 Posts
Hi

As Spunk.Funk says this is almost certainly a bad sector on your hard drive.
From your event viewer logs (You have many of these errors):
Code:
Event Type:	Error
Event Source:	Disk
Event Category:	None
Event ID:	11
Date:		04/04/2011
Time:		06:12:03 AM
User:		N/A
Computer:	THEBEAST
Description:
The driver detected a controller error on \Device\Harddisk2\D.

[B]AND[/B]

Event Type:	Warning
Event Source:	Disk
Event Category:	None
Event ID:	51
Date:		01/04/2011
Time:		07:28:07 AM
User:		N/A
Computer:	THEBEAST
Description:
An error was detected on device \Device\Harddisk2\D during a paging operation.
From your 1 recent minidump that wasn't corrupted:
Code:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
...............................................................................................................
Debug session time: Fri Apr  1 07:38:43.718 2011 (UTC + 2:00)
System Uptime: 0 days 2:01:47.432

BugCheck 77, {1, adacb808, 0, b4714c4c}
Probably caused by : memory_corruption ( nt!MmInPageKernelStack+176 )

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in.  Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found.  Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED)  normally indicates
the data could not be read from the disk due to a bad
block.  Upon reboot autocheck will run and attempt to map out the bad
sector.  If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked.  See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: adacb808, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: b4714c4c, address of signature on kernel stack

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0x77_1_nt!MmInPageKernelStack+176
1. You can check your hard drive for any errors.
To do this go to Start -> Run -> type chkdsk c: /r -> click Ok. When asked if you want to force a dismount say No. When asked to schedule the check at the next startup say Yes. Restart your PC to allow chkdsk to run.
Note you want to especially run chkdsk on the D:\ drive. However it would be a good idea to run chkdsk on all three of your drives (on all 5 of your volumes c:\, d:\, e:\, v:\ and w:\)

2. Run the hard drive diagnostic tool for your make of hard drive. A list of Hard Drive manufacturers and the links to their Diagnostics tools can be found here. Download the ZIP file, extract the ISO and write it to CD using a program like ImgBurn.
Once written to CD, boot your PC with the CD and run the Advanced or Extended test.
Note you have a combination of 1 Seagate and 2 Western Digital drives. Download the Seagate tool and run that on all of the drives - one by one. If there is a problem with one of the Western Digital drives that Seatools cannot fix you will have to download the Western Digital LifeGuard tool.
 

· Registered
Joined
·
1,184 Posts
Discussion Starter · #10 · (Edited)
i can but i have new ram. Whenever I have had CPU issues people suggest that and it always comes by fine but I will. May not have the results for some time bc I know it needs to be run for a good amount of time.

On average how long per stick does it need to be run to be effective?

Also I have memtest 4.00 already, will that work or should I get the latest?
 
1 - 12 of 12 Posts
Status
Not open for further replies.
Top