Critical Error Or Buffer Overflow Problem ??

Status
Not open for further replies.
Spacescreamer

Spacescreamer

Innovator
Hi Guys ..

My system been acting weird .. Again that is..

Scenario is like,

Started playing a few games on my PC abt a month back. Game Like Counter Strike and other decent but not too heavy games, and my system hasnt got any graphics card.

What i noticed was that after a few hours of play on the system, my system rebooted abruptly all by itself, and this happened quite often while playing games.

So opting for the safest option due to lack of free time to go into it.. i stopped playing games altogether for the time being.

Offlate i noticed another peculiar problem.

Applications like FireFox, IE, VLC Media Player all started crashing midway thru the operations. FFox esp when it was buffering the data to be displayed.

And if that wasnt the case, the system started to reboot if i had 2-3 applications running.

I used to leave my rig on, turning the monitor off and only the utorrent used to be running.. even then the system has been rebooting.

Recently, i tried to burn a DVD and exited from all the applications, even the internet was disconnected but the system rebooted again.. Making me loose one of my freshly acquired TY DVD :@

So is this a case of some critical error which keeps occuring on and off Or Buffer problem ??

Pls do advice and help me on this issue.. :(
 
Tried formatting and reinstalling Windows?sometimes registry errors or stuff like that might cause problems...or ur hardware is dying...time to upgrade!!!!
 
^^ Guide me to that pls..

@Indrajeet.. U sure..? Its been only 2 years old that i got my system.

So not too mch time has passed.
 
it used to happen when one of my older system's hdd developed bad sectors and would restart when windows would try to write to those sectors...try checking that too....im guessing its the hdd causing the problem..

eventlog

start-control panel-administrative tools-event viewer-system..
 
Had Drives automatically remap bad sectors, nowadays :)

I think the OP needs to do an intensive memory test ie leave machine overnight with memtest, sounds like a RAM problem.
 
I too agree this is likely to be a RAM error, but it could be an HDD error too. Or any number of hardware problems for that matter.

Start with the event log and memtest, we'll proceed from there.
 
Okay .. i just opened the log ..

scores of Errors and Warnings.

Errors Sources:

>DCOM

>W32Time

>ialm

>Service Control Mgr

Warning Sources:

>Tcpip

>W32Time

>Dhcp

>disk

>PlugPlayManager

>USER32

The Error And Warning Instances are way too much ..

What Next ?
 
Warnings are not too important... what you do need to do is look at the error logs. Are there any error events at the time your machine rebooted? Also, right click on my computer > system properties > advanced > startup and recovery, make sure that the box titled "Automatically restart" is NOT checked. That way if there is a BSOD, you will see it and any error messages. If there is no BSOD but only random restarts, then I suspect a hardware problem (RAM/HDD).
 
  • Like
Reactions: 1 person
Ok .. so i just UNCHECKED the Automatically Restart option under the Startup & Recovery Option.

Let's See How it goes now ...

EDIT:

So ..

the inevitable happened, and thanks to the likes of KingKrool, i have some leads now.

As i was goin to write that i have 4 partitions done on my main HDD, and have checked each for any error.. plus have defragmented the C: as well, the BSOD paid me a visit.

PAGE_FAULT_IN_NO_PAGED_AREA

Check to make sure any new hardware Or Software is properly installed. ... bla bla bla..n fiddle dee dee ...

Beginning to make dump of the physical memory.

So now what ..?

i guess its a RAM error ? (i cheked the hdd for errors).

is it gonna go away if the page file size is increased??

Steps for the increase in page file (if required i.e) ??
 
No no. Is not a result of the page file. There are two possibilities:

1. A bad driver. Something in the kernel is dereferencing a bad pointer, resulting in a crash.

2. The RAM contents are being corrupted due to hardware issues. Possibly bad RAM, I suppose it could be a bad PSU.

There is also an outside, third possibility which I will discount here. That is a bad hdd, resulting in a corrupt pagefile. You seem to have checked the hdd for errors (I will assume the check would have found the problems, but if it is a bad sector on the hdd, I am not sure it would). If you want to make sure that it is NOT the hdd, you can switch the location of the pagefile. How to move the paging file in Windows XP provides information on how to do so. If a bad HDD is corrupting the pagefile, this should fix it, except if by some unfortunate chance the other partitions are also bad and corrupt the pagefile (very very small probability).

I would suggest using memtest to check for errors. Let us know how it goes.
 
u mean

My Computer>c:>sharing and security>tools>error checking

I have run that test on all the drives.

The C: test req me to restart the comp as u wd know that control has to be given to some critical data, did that too and read the summary. No Bad sectors detected.

next step ?

i mean if the above mentioned indeed was the one to which u were pointing towards..

changing the page file location ?
 
Well, the simplest thing is the pagefile location change, though I am almost sure that is not the issue. But there is no harm in trying. See the link I have sent you, make the pagefile reside on some other partition than it is on now (make sure to disable the pagefile on the current partition, not just enable it on another).
 
Jeez.. U r fast man ..

a minute ago , u r not online.. i make some changes and come back .. Whoa.. u r there again and ready with a fresh post. Apply Some brakes yaar.. :P

Khair, good to observe that i am on the same track as u been thinking (well u r the commander here ;)

I did changed the location of the paging file.. as that seemed to be the most simplest of the logical step towards solving the problem.

I must mention here that wen i had purchased the system, within 2 months of that the psu had gone kaput.

It was under warranty so the vendor got it repaired.. not replaced.

Within abt 5-6 months my hdd developed bad sectors, which i thought was due to the woofer of my MX 5021 being too close to the system.

Maybe now i have to believe that the psu is acting up.

As i wrote all this, ffox crashed once again.

I had changed the location of the paging file, but hadnt disabled it from the C: .

I ll do that rite now and then as u said.. Lets see..
 
Hold a sec, you also have apps crashing without the system rebooting? Then this is not a driver error. Is almost certainly hardware, whether it is the PSU, RAM or HDD remains to be seen.
 
ffox crashed while typing..

then the change that i made was that i absolutely removed paging from the C: drive.

So far so good.

Think i ll have to stretch the legs of my system and do some rigorous usage to chek how the change has been useful.
 
EDIT:



A problem has been detected and Windows has been shut down to prevent any damage to your computer.

IF this is the first time that u have seen this stop error screen, restart ur comp.

if this occurs again, then follow this procedure:

Check to see if u have adquate space. If a driver is identified in the error msg, then disable or check for the update.

Try changing the video adapter.

Chek with ur hardware vendor for any bios update.

Disable any BIOS memory option sch as caching or shadowing. If need to use safe mode then restart and press F8.

Technical Information:

STOP: 0x0000008E (0xC000 ... something something....)



The paging fault occured once again after the above mentioned error had occured and happened while i was writing abt the above mentioned error.

Any more clues now ??
 
Well you can switch your pagefile back. We now have issues with either your RAM, HDD, PSU or Motherboard to worry about.

First off, let us try eliminating the HDD. Try running memtest. I have little experience with that though, some of the other members will be able to guide you better as to how to use it best.

Also, have you tried safe mode (with networking) ever? Has it helped?
 
Well there are two tools. One is memtest86+

Memtest86+ - Advanced Memory Diagnostic Tool

It runs from a boot disk (i.e. boot into it). The other is this tool called memtest

MemTest: RAM reliability tester for Windows

It runs within windows. Once, when I bought some incompatible RAM, memtest86+ was not able to detect any errors even after several errors, but memtest did so immediately. Try both. Try memtest (within windows) first, followed by memtest86+ (you'll need to create some sort of bootdisk with it).

Refer to their websites for details.
 
Status
Not open for further replies.
Top Bottom