Random reboots

[Gh0st]

Hey guys. I'm new to this site, but from what I have read so far, I like it very much. I have been having a problem for a few months now. Every so often my computer will just randomly reboot itself. I am not sure, but I suspect it has something to do with my RAM. When I have just one stick installed it doesnt restart( at least i dont remember it ever restarting). I have read many suggestions. I have upgraded Bios, chipset, all drivers, and even reformatted, but I still have the problem. i also read an article that said to adjust the CAS value for your ram and the fsb.
http://www.pcworld.com/howto/article/0,aid,110320,pg,2,00.asp
I increased the CAS value, and it seemed to allow my computer to run longer without the restarting, but when i decrease my fsb, my computer will not even boot. if any of you guys have suggestions please help me out. thanks.

edit: i have tried testing with multiple sticks of ram. whenever i have two in it reboots or gets an error. the second one i have in now is brand new. I have also run memtest3.2 and no errors came up.i just read another post and turned off the automatic reboot option. i will post the error message once i get it. thanks.

 

[Gh0st]

here is that event 1001 i say other people talking about.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c5 (0x000a0008, 0x00000002, 0x00000001, 0x8053d39a). A dump was saved in: C:\WINDOWS\Minidump\Mini090805-02.dmp.

here is three event 1003s:
Error code 0000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000.

Error code 0000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804e2a1a.

Error code 100000be, parameter1 bf802e51, parameter2 0c0fa021, parameter3 b8859c98, parameter4 0000000c.

ive also attached some minidump files. thanks

 

[atrice]

It's not clear to me from your post whether or not you have (while running the machine with just one stick of RAM) taken note of which stick allows the machine to run without crashing. If RAM is at fault, this test might help pinpoint the problem. Have you done this yet?

 

[Gh0st]

i havent with this new stick. i plan on it as soon as i get time.

 

[cpc2004]

Hi Gh0st,

One of your minidump crashed with memory corruption and corrupt the windows module win32k.sys. This is the symptom of faulty ram. Diagnsotic which memory stick is faulty.

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: bf802e51, Virtual address for the attempted write.
Arg2: 0c0fa021, PTE contents.
Arg3: b8859c98, (reserved)
Arg4: 0000000c, (reserved)

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xBE

MISALIGNED_IP:
win32k+2d67
bf802d67 0053e8 add [ebx-0x18],dl

LAST_CONTROL_TRANSFER: from bf802eb4 to bf802d67

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8859d30 bf802eb4 00000000 00000400 0000babe win32k+0x2d67
b8859d4c 804dad01 001d0224 00000400 0000babe win32k+0x2eb4
b8859d4c 7ffe0304 001d0224 00000400 0000babe nt!KiSystemService+0xc4
002168e0 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
bf802c03 - win32k+2c03
[ 53:7f ]
bf802c13 - win32k+2c13 (+0x10)
[ 08:74 ]
bf802c23 - win32k+2c23 (+0x10)
[ 7f:15 ]
bf802c33 - win32k+2c33 (+0x10)
[ 74:8b ]
bf802c43 - win32k+2c43 (+0x10)
[ 15:44 ]
bf802c53 - win32k+2c53 (+0x10)
[ 8b:74 ]
bf802c63 - win32k+2c63 (+0x10)
[ 44:53 ]
bf802c71 - win32k+2c71 (+0x0e)
[ 85:24 ]
bf802c73 - win32k+2c73 (+0x02)
[ 74:08 ]
bf802c83 - win32k+2c83 (+0x10)
[ ff:7f ]
bf802c93 - win32k+2c93 (+0x10)
[ 04:74 ]
bf802ca3 - win32k+2ca3 (+0x10)
[ e8:15 ]
bf802ca6 - win32k+2ca6 (+0x03)
[ ff:eb ]
bf802cb3 - win32k+2cb3 (+0x0d)
[ 10:8b ]
bf802cb6 - win32k+2cb6 (+0x03)
[ 24:e8 ]
bf802cc3 - win32k+2cc3 (+0x0d)
[ 20:44 ]
bf802cc6 - win32k+2cc6 (+0x03)
[ 50:ff ]
bf802cd3 - win32k+2cd3 (+0x0d)
[ 8b:74 ]
bf802cd6 - win32k+2cd6 (+0x03)
[ c2:24 ]
bf802ce3 - win32k+2ce3 (+0x0d)
[ 01:ff ]
bf802ce6 - win32k+2ce6 (+0x03)
[ 00:50 ]
bf802cf3 - win32k+2cf3 (+0x0d)
[ 85:04 ]
bf802cf6 - win32k+2cf6 (+0x03)
[ 0f:c2 ]
23 errors : !win32k (bf802c03-bf802cf6)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption

 

[Gh0st]

thanks cpc. i will test it out asap.does that necessarily mean that it is the memory stick or could it also be the slot or dirty contacts?

 

[Gh0st]

i havent had time to check the ram, but instead of restarting i got a blank blue screen with all my sound scrambled.

 

[cpc2004]

thanks cpc. i will test it out asap.does that necessarily mean that it is the memory stick or could it also be the slot or dirty contacts?

You can reseat the memory slot and clean the dust within your PC.