Spontaneous reboots: memory problem?

[Boris Zakharin]

After having purchased 512MB DDR RAM, I'm getting spontaneous reboots in
Windows XP about every 24 hours (not an exact figure). I'm not certain the
memory is the problem. The following are the stop codes I was able to
retrieve from the Eventlog. They're not always the same:

0x0a (IRQL_NOT_LESS_OR_EQUAL)
0xdb (DRVER_CORRUPTED_SYSPTES)
0x1000007e (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M)
0xd1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)

Is this enough information to pinpoint the problem? I've run memtest86 for 2
cycles without problems.

[Will Dormann]

Boris Zakharin wrote:
After having purchased 512MB DDR RAM, I'm getting spontaneous reboots in Windows XP about every 24 hours (not an exact figure). I'm not certain the memory is the problem. The following are the stop codes I was able to retrieve from the Eventlog. They're not always the same:

If the problem only appeared after adding RAM, then the RAM is suspect.
Run the memory tester from www.memtest.org overnight and check the results.



-WD

[RusH]

"Boris Zakharin" <zakharin@alumni.upenn.edu> wrote :
After having purchased 512MB DDR RAM, I'm getting spontaneous reboots in Windows XP about every 24 hours (not an exact figure). I'm not certain the memory is the problem. The following are the stop codes I was able to retrieve from the Eventlog. They're not always the same: 0x0a (IRQL_NOT_LESS_OR_EQUAL)

mmm SBLive ? :)


Pozdrawiam.
--
RusH //
http://kiti.pulse.pdi.net/qv30/
Like ninjas, true hackers are shrouded in secrecy and mystery.
You may never know -- UNTIL IT'S TOO LATE.

[Boris Zakharin]

25 hours 0 errors. What else could it be?

"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:xuOWb.2853$WM6.971@fe2.columbus.rr.com... Boris Zakharin wrote: After having purchased 512MB DDR RAM, I'm getting spontaneous reboots in Windows XP about every 24 hours (not an exact figure). I'm not certain
the memory is the problem. The following are the stop codes I was able to retrieve from the Eventlog. They're not always the same: If the problem only appeared after adding RAM, then the RAM is suspect. Run the memory tester from www.memtest.org overnight and check the
results. -WD

[Will Dormann]

Boris Zakharin wrote:
25 hours 0 errors. What else could it be?


Does restoring the memory configuration to what it was before cause the
problem to disappear?

(Since you mentioned that the problem appeared after upgrading the memory)


-WD

[Boris Zakharin]

I'd have to run with the old configuration for days to be sure. The reboots
aren't frequent and going back to 256 MB would really slow it down.

"Will Dormann" <wdormann@yahoo.com.invalid> wrote in message
news:PyyXb.5098$9H3.2195@fe2.columbus.rr.com... Boris Zakharin wrote: 25 hours 0 errors. What else could it be? Does restoring the memory configuration to what it was before cause the problem to disappear? (Since you mentioned that the problem appeared after upgrading the memory) -WD

[Alexander Grigoriev]

Try http://home.earthlink.net/~alegr/download/memtest.htm

Run with /preheat option. If you choose to run it under Windows, run it with
disk I/O thread.

"Boris Zakharin" <zakharin@alumni.upenn.edu> wrote in message
news:3syXb.23599$M8.4862@nwrdny02.gnilink.net... 25 hours 0 errors. What else could it be? "Will Dormann" <wdormann@yahoo.com.invalid> wrote in message news:xuOWb.2853$WM6.971@fe2.columbus.rr.com... Boris Zakharin wrote: After having purchased 512MB DDR RAM, I'm getting spontaneous reboots
in Windows XP about every 24 hours (not an exact figure). I'm not certain the memory is the problem. The following are the stop codes I was able to retrieve from the Eventlog. They're not always the same: If the problem only appeared after adding RAM, then the RAM is suspect. Run the memory tester from www.memtest.org overnight and check the results. -WD

[Tony Hill]

On Sat, 14 Feb 2004 23:47:11 GMT, "Boris Zakharin"
<zakharin@alumni.upenn.edu> wrote:25 hours 0 errors. What else could it be?

Well, the other normal cause of random reboots is usually the power
supply. My system is sadly suffering from just that problem (err, at
least I really hope it's the power supply since I've got a new one on
order! :> ). Unfortunately, short of replacing the power supply with
a known-good one it's rather tough to test power supply problems.

-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca

[George Macdonald]

On Thu, 12 Feb 2004 17:05:09 GMT, "Boris Zakharin"
<zakharin@alumni.upenn.edu> wrote:
After having purchased 512MB DDR RAM, I'm getting spontaneous reboots inWindows XP about every 24 hours (not an exact figure). I'm not certain thememory is the problem. The following are the stop codes I was able toretrieve from the Eventlog. They're not always the same:0x0a (IRQL_NOT_LESS_OR_EQUAL)0xdb (DRVER_CORRUPTED_SYSPTES)0x1000007e (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M)0xd1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)Is this enough information to pinpoint the problem? I've run memtest86 for 2cycles without problems.

Have you loaded any new drivers since the memory upgrade? Are you running
a (old) virus scanner which might be incompatible with XP?... maybe try
disabling the scanner. The indications are that someting is awry in the
system page table requests/allocation, possibly caused by a rogue driver -
see here: http://www.osr.com/ddk/ddtools/bccodes_6vxj.htm

Here's the M$ KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;818501

You might try checking that all your system files are intact:

SFC /PURGEALL
SFC /SCANNOW

Also look for driver updates.

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??

[Boris Zakharin]

I'm not sure about the driver, but I notice that the last event in the log
prior to the latest crash (almost exactly 50 minutes earlier) is a warning.
Event ID 3019 source MrxSmb "The redirector failed to determine the
connection type." Looking at MS Help, this is normal. In fact, the time
begfore the second to last crash the message appears 7 times in a row before
the crash. However, in two cases this warning is absent. The last messages
from those are: "The SetupNTGLM7X service was successfully sent a start
control" and "The system detected that network adapter MAC Bridge Miniport
was connected to the network, and has initiated normal operation over the
network adapter."

An error that often comes up in the log, but not in any relation to the
crash is 6004: "A driver packet received from the I/O subsystem was invalid.
The data is the packet." Now this souds like a network driver problem.
However, which one? I've got two physical Ethernet cards, one card that
represents a USB DSL modem, a network bridge, and two VMWare adapters.


"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message
news:f0cu20ha4l4hs5vi403vt1ts405ei2fhup@4ax.com... On Thu, 12 Feb 2004 17:05:09 GMT, "Boris Zakharin" <zakharin@alumni.upenn.edu> wrote:After having purchased 512MB DDR RAM, I'm getting spontaneous reboots inWindows XP about every 24 hours (not an exact figure). I'm not certain
thememory is the problem. The following are the stop codes I was able toretrieve from the Eventlog. They're not always the same:0x0a (IRQL_NOT_LESS_OR_EQUAL)0xdb (DRVER_CORRUPTED_SYSPTES)0x1000007e (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M)0xd1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)Is this enough information to pinpoint the problem? I've run memtest86
for 2cycles without problems. Have you loaded any new drivers since the memory upgrade? Are you running a (old) virus scanner which might be incompatible with XP?... maybe try disabling the scanner. The indications are that someting is awry in the system page table requests/allocation, possibly caused by a rogue driver - see here: http://www.osr.com/ddk/ddtools/bccodes_6vxj.htm Here's the M$ KB article http://support.microsoft.com/default.aspx?scid=kb;en-us;818501 You might try checking that all your system files are intact: SFC /PURGEALL SFC /SCANNOW Also look for driver updates. Rgds, George Macdonald "Just because they're paranoid doesn't mean you're not psychotic" - Who,
me??

[Bob]

Try moving the new ram to another slot. If this works then it means the slot
is bad.

"Boris Zakharin" <zakharin@alumni.upenn.edu> wrote in message
news:o5OXb.51147$KV5.15503@nwrdny01.gnilink.net... I'm not sure about the driver, but I notice that the last event in the log prior to the latest crash (almost exactly 50 minutes earlier) is a
warning. Event ID 3019 source MrxSmb "The redirector failed to determine the connection type." Looking at MS Help, this is normal. In fact, the time begfore the second to last crash the message appears 7 times in a row
before the crash. However, in two cases this warning is absent. The last messages from those are: "The SetupNTGLM7X service was successfully sent a start control" and "The system detected that network adapter MAC Bridge Miniport was connected to the network, and has initiated normal operation over the network adapter." An error that often comes up in the log, but not in any relation to the crash is 6004: "A driver packet received from the I/O subsystem was
invalid. The data is the packet." Now this souds like a network driver problem. However, which one? I've got two physical Ethernet cards, one card that represents a USB DSL modem, a network bridge, and two VMWare adapters. "George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message news:f0cu20ha4l4hs5vi403vt1ts405ei2fhup@4ax.com... On Thu, 12 Feb 2004 17:05:09 GMT, "Boris Zakharin" <zakharin@alumni.upenn.edu> wrote:After having purchased 512MB DDR RAM, I'm getting spontaneous reboots
inWindows XP about every 24 hours (not an exact figure). I'm not certain thememory is the problem. The following are the stop codes I was able toretrieve from the Eventlog. They're not always the same:0x0a (IRQL_NOT_LESS_OR_EQUAL)0xdb (DRVER_CORRUPTED_SYSPTES)0x1000007e (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M)0xd1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)Is this enough information to pinpoint the problem? I've run memtest86 for 2cycles without problems. Have you loaded any new drivers since the memory upgrade? Are you
running a (old) virus scanner which might be incompatible with XP?... maybe try disabling the scanner. The indications are that someting is awry in the system page table requests/allocation, possibly caused by a rogue
driver - see here: http://www.osr.com/ddk/ddtools/bccodes_6vxj.htm Here's the M$ KB article http://support.microsoft.com/default.aspx?scid=kb;en-us;818501 You might try checking that all your system files are intact: SFC /PURGEALL SFC /SCANNOW Also look for driver updates. Rgds, George Macdonald "Just because they're paranoid doesn't mean you're not psychotic" - Who, me??

[John]

"Boris Zakharin" <zakharin@alumni.upenn.edu> wrote in message news:<3syXb.23599$M8.4862@nwrdny02.gnilink.net>... 25 hours 0 errors. What else could it be?

IMO given the frequency of crashes, 25 hours and 0 errors doesn't
rule out memory problems.

I recently worked on a new PC with > once/day BSOD (blue screens of
death), yet it passed memtest flawlessly the first run (overnight).
After a few days and several more BSODs, I ran Memtest again and it
found errors.

After replacing memory the system has been reliable.