Windows reboots repeatedly. Even after new install

For quite some time my computer has been rebooting whenever I turn it on, when it has been off for a longer period of time. With longer I mean, for aprox. 5 hours or longer.

At first it was maybe a single reboot due to a BSOD, but recently it gotten worse to a stage where it reboots 50 times (and yes I counted em).

I did install windows but it wasn't worthwhile the effort because it's still the same problem. I tried accessing it in safe mode, but to no avail.

I check upon the BSOD errors (with that windows startup option to halt on errors) and it's something different all of the time.

My guess is that I'm having some kind of virus and are going to format all my partitions, repartition it and see if that works. Perhaps there was a virus of some sorts on another unformatted partition.

If anyone should have another idea what this might be... I'm more that curious to hear.

System specs:
Mainbord: MSI K8480M2 (w/ Radeon x200, Realtek AC97 & Realtek RTL8139/810x Lan. All onboard)
CPU: AMD Athlon 64 3000+
Mem: 1 gb (of an unknown brand)
Power supply: Unknown (but sufficient)
HD: Maxtor 6L120M0

 

Hello Chaoschrist and welcome to the Board,

With symptoms like that, first suspect is hardware.

Start running diagnostics: http://oca.microsoft.com/en/windiag.asp for RAM.

Have you run chkdsk http://www.microsoft.com/resources/d...us/chkdsk.mspx or defrag yet? Both disk read intensive, if a problem, may show up.

Not likely, you should eliminate hardware problems first.

Regards - Charles

 

Safe Mode

Start of by booting into Safe Mode.
See if the problem occurs there to run out standard hardware issues - power supply etc.
If windows is stable then it is an problem within the windows software - hardware conflicts etc.

 

Hi...

Well, I did run through chkdsk. No problems there whatsoever. Didn't check the memory though... I don't have any cd-r's around and no floppy drive. But I will check that.

Right now, the system is somewhat stable. Seems that the onboard GPU and soundcard (also onboard) are on the same IRQ. I had a problem like that once before with a different computer.

So perhaps any of the more experienced users here could verify that this could result in a BSOD?

Safe mode does/did the same. But I disabled the onboard soundcard in the bios, and nothing strange happens now.

 

Ran chkdsk/defrag but nothing strange happened. Also... I did run a memorytest like you told me, but it seems the memory is OK.

I did post about the shared IRQ problems, and that I disabled on of 2 devices on that adress. The problem was gone for a while, but now it also reboots once windows is up and running.

 

You write that the error is different each time, but we need some indication of what these errors are - whether they are hardware errors or not.

Follow the instructions in the thread on posting a dump:
Dump Data collection tool and instructions
http://www.windowsbbs.com/showthread.php?t=33471

Regards - Charles

 

Smart money goes to one or the other, perhaps both
Mem: 1 gb (of an unknown brand)
Power supply: Unknown (but sufficient)

I personally don't think you have to look beyond these.

 

Sorry, I can't understand what u mean.

1: If u shut down it, after a while, it'll turn on itself??
2: Or, when u using it, it'll rebooting?

1, Check ur BIOS setting, check the PowerOn setting. some PC can PowerOn itself by the LAN or Mouse event.
2, Check the RAM. Maybe the RAM has the Problem. Change a new one, and try it again.

Good Luck!

 

Yeah, I know what you mean. But I meant... I don't really know which brand, therefor... it's unknown to me But then again, you could be right.

As for the Ram like Flewsky said. I checked that already, no problem there.

I'm still thinking it could be a bootsector virus, since reformatting didn't do the trick either. Although, I downloaded a cd from http://www.ultimatebootcd.com/ and I'm going to run that. And of course I'll try for the dump charlesvar asked.

Edit: I've added the debuglog. Hopefully this helps. Also I ran a couple of memory tests with that ultimate boot cd. One of the tests gave a load of memory errors, yet the others didn't. I find this kinda strange. Does this happen more often? (a diagnostics program giving errors and another giving no errors?)

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini022207-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Thu Feb 22 13:58:34.062 2007 (GMT-8)
System Uptime: 0 days 0:01:21.562
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
............................................................................................
Loading User Symbols
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {859d2910, 1, 8054b907, 0}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Probably caused by : win32k.sys ( win32k+29ef )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 859d2910, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8054b907, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


MODULE_NAME: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
859d2910

FAULTING_IP:
nt+74907
8054b907 8913 mov dword ptr [ebx],edx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 8054ba1e to 8054b907

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f69b2bbc 8054ba1e e19cb6a0 e19a3ad0 e19a3ad0 nt+0x74907
f69b2bfc bf8029ef e19c7d48 00000000 f69b2c28 nt+0x74a1e
f69b2c0c bf8e3695 e19c7d48 e19a3a60 00000000 win32k+0x29ef
f69b2c28 bf8465af e19a3a60 00000001 85273020 win32k!PATHOBJ_bCloseFigure+0x13052
f69b2c44 8058affb 85268020 00000000 8527a7f0 win32k!EngMulDiv+0x1fb5
f69b2cf0 8058b342 00000000 f69b2d4c 804e6851 nt+0xb3ffb
f69b2cfc 804e6851 8527a7f0 f69b2d48 f69b2d3c nt+0xb4342
f69b2d4c 804df0d4 00000001 00000000 f69b2d64 nt+0xf851
f69b2d64 7c90eb94 badb0d00 00aaed70 00000000 nt+0x80d4
f69b2d68 badb0d00 00aaed70 00000000 00000000 0x7c90eb94
f69b2d6c 00aaed70 00000000 00000000 00000000 0xbadb0d00
f69b2d70 00000000 00000000 00000000 00000000 0xaaed70


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+29ef
bf8029ef 5d pop ebp

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

SYMBOL_NAME: win32k+29ef

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

eax=e19a8508 ebx=859d2910 ecx=e19a8390 edx=857ee1e8 esi=857ee050 edi=000001ff
eip=8054b907 esp=f69b2b7c ebp=f69b2bbc iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt+0x74907:
8054b907 8913 mov dword ptr [ebx],edx ds:0023:859d2910=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
f69b2bbc 8054ba1e e19cb6a0 e19a3ad0 e19a3ad0 nt+0x74907
f69b2bfc bf8029ef e19c7d48 00000000 f69b2c28 nt+0x74a1e
f69b2c0c bf8e3695 e19c7d48 e19a3a60 00000000 win32k+0x29ef
f69b2c28 bf8465af e19a3a60 00000001 85273020 win32k!PATHOBJ_bCloseFigure+0x13052
f69b2c44 8058affb 85268020 00000000 8527a7f0 win32k!EngMulDiv+0x1fb5
f69b2cf0 8058b342 00000000 f69b2d4c 804e6851 nt+0xb3ffb
f69b2cfc 804e6851 8527a7f0 f69b2d48 f69b2d3c nt+0xb4342
f69b2d4c 804df0d4 00000001 00000000 f69b2d64 nt+0xf851
f69b2d64 7c90eb94 badb0d00 00aaed70 00000000 nt+0x80d4
f69b2d68 badb0d00 00aaed70 00000000 00000000 0x7c90eb94
f69b2d6c 00aaed70 00000000 00000000 00000000 0xbadb0d00
f69b2d70 00000000 00000000 00000000 00000000 0xaaed70
start end module name
804d7000 806eb600 nt ntoskrnl.exe Tue Aug 03 23:19:48 2004 (41108004)
806ec000 8070c380 hal halaacpi.dll Tue Aug 03 22:59:05 2004 (41107B29)
bf800000 bf9c0380 win32k win32k.sys Tue Aug 03 23:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
bff50000 bff52480 framebuf framebuf.dll Wed Aug 04 00:56:31 2004 (411096AF)
f66cd000 f671f180 srv srv.sys Tue Aug 03 23:14:44 2004 (41107ED4)
f6810000 f682a580 Mup Mup.SYS Tue Aug 03 23:15:20 2004 (41107EF8)
f690b000 f690e280 ndisuio ndisuio.sys Tue Aug 03 23:03:10 2004 (41107C1E)
f6e0b000 f6e22480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
f6e4b000 f6eb9380 mrxsmb mrxsmb.sys Tue Aug 03 23:15:14 2004 (41107EF2)
f6eba000 f6ee5180 rdbss rdbss.sys Tue Aug 03 23:20:05 2004 (41108015)
f6ee6000 f6f07d00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
f6fa8000 f7006cc0 vsdatant vsdatant.sys Mon Jan 08 12:40:47 2007 (45A2AC4F)
f7007000 f7027f00 ipnat ipnat.sys Tue Aug 03 23:04:48 2004 (41107C80)
f7028000 f704fc00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
f7078000 f70cfa80 tcpip tcpip.sys Tue Aug 03 23:14:39 2004 (41107ECF)
f70d0000 f70e2400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f7103000 f7116780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
f7133000 f7135f80 mouhid mouhid.sys Fri Aug 17 13:47:57 2001 (3B7D82FD)
f713f000 f7172200 update update.sys Tue Aug 03 22:58:32 2004 (41107B08)
f7173000 f71a3100 rdpdr rdpdr.sys Tue Aug 03 23:01:10 2004 (41107BA6)
f71a4000 f71b4e00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
f71b5000 f71cb680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
f71cc000 f7216000 akvlzrhl akvlzrhl.SYS Sun Nov 12 02:40:09 2006 (4556FA09)
f7216000 f7227200 Rtlnicxp Rtlnicxp.sys Tue Apr 13 05:14:12 2004 (407BD994)
f7228000 f724a680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f724b000 f726de80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
f7272000 f7274280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
f7296000 f7298900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
f72aa000 f72adc80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
f72f2000 f731ea80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f731f000 f73ab480 Ntfs Ntfs.sys Tue Aug 03 23:15:06 2004 (41107EEA)
f73ac000 f73c2780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
f73c3000 f73d4f00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
f73d5000 f73f3780 fltMgr fltMgr.sys Tue Aug 03 23:01:17 2004 (41107BAD)
f73f4000 f740b480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
f740c000 f7431700 dmio dmio.sys Tue Aug 03 23:07:13 2004 (41107D11)
f7432000 f7450880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
f7451000 f7461a80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
f7462000 f748fd80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
f7490000 f74a7800 SCSIPORT SCSIPORT.SYS Tue Aug 03 22:59:39 2004 (41107B4B)
f74a8000 f7582000 sptd sptd.sys Thu Dec 21 06:01:52 2006 (458A93D0)
f75a3000 f75abc00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
f75b3000 f75bd500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
f75c3000 f75cfc80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
f75d3000 f75dbe00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
f75e3000 f75ef200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
f75f3000 f7601e80 ohci1394 ohci1394.sys Tue Aug 03 23:10:05 2004 (41107DBD)
f7603000 f7610000 1394BUS 1394BUS.SYS Tue Aug 03 23:10:03 2004 (41107DBB)
f7633000 f763d380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
f7643000 f764f180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
f7653000 f7661080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
f7663000 f766fe00 i8042prt i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
f7673000 f767f880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
f7683000 f768d200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
f7693000 f769ed00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
f76a3000 f76ab900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
f76b3000 f76bcf00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
f76c3000 f76d1100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
f76d3000 f76dc480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
f76f3000 f76fb700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
f7713000 f771bd80 HIDCLASS HIDCLASS.SYS Tue Aug 03 23:08:18 2004 (41107D52)
f7723000 f7732900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
f7823000 f7829200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
f782b000 f782f900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
f786b000 f786f280 usbohci usbohci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f7873000 f7879800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f787b000 f787f500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
f78d3000 f78d9000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f78f3000 f78f7880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
f7903000 f7907580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
f7913000 f7917080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
f791b000 f7920a00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f794b000 f7950200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
f795b000 f795fa80 Msfs Msfs.SYS Tue Aug 03 23:00:37 2004 (41107B85)
f796b000 f7972880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
f799b000 f79a1180 HIDPARSE HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
f79b3000 f79b6000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
f7a8f000 f7a91580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
f7a97000 f7a99580 hidusb hidusb.sys Fri Aug 17 14:02:16 2001 (3B7D8658)
f7aa3000 f7aa4b80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
f7aa5000 f7aa6100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f7aa7000 f7aa8700 dmload dmload.sys Fri Aug 17 13:58:15 2001 (3B7D8567)
f7ab3000 f7ab4100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
f7ab7000 f7ab8280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
f7abd000 f7abef00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
f7ac1000 f7ac2080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
f7ac5000 f7ac6080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
f7ad3000 f7ad4100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f7b6b000 f7b6bd00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
f7bfb000 f7bfbd00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)
f7c9d000 f7c9db80 Null Null.SYS Fri Aug 17 13:47:39 2001 (3B7D82EB)
f7ca0000 f7ca0f80 avgclean avgclean.sys Mon Aug 21 15:55:15 2006 (44EA39D3)
Closing open log file c:\debuglog.txt

 

Hi Chaoschrist,

If you have more than one RAM stick, take out one, the one in the 2nd slot, or switch them and run. Then try what was in the 2nd slot and run with it.

For future reference, don't add to a previous post, because that doesn't trigger a notification to anyone that posted that there is new info.

Regards - Charles

 

See if you can get the symbols updated.
The debug will tell you where and how the restart happened, there could be many reasons why it happened.

I like the power supply suggestion. If you can find a "bigger ", "better" power supply try borrowing it (or reduce the load on your current PSU by disconnecting all unneeded hardware, although the PSU may be failing).

Matt

 

re

Hi there i am Gareth. Have you ever been hacked?
If you have then the virus will be in a partition that you use all the time. Maybe you have C: D: and an E: Drive if so you maybe have music in the D: drive and the virus is there and wont go away. You might have to format all partitions to get rid of the virus.

- Gareth

 

If you are still stuck.

Go into the BIOS settings at startup, disable the onboard audio and LAN, at least until you get it stable. Remove any added hardware like PCI cards, etc.
(This relates to a problem I have experienced with my MSI motherboard, if you find disabling the onboard hardware solves the problem, look for BIOS upgrade at MSI.)

In the BIOS, if there is a setting/menu Load Setup Defaults, use that. If that works you will need to find why an "optimum" setting causes the problem.

Check in the section "PC Health" or "monitors ". Voltages are OK (close)? Temperatures not near critical?

Matt

 

Well, it seems the memory was the problem after all

I managed to get a hold of a replacement for now, and I'll be returning to the store as I still have warranty on it.

Thanks for all help

 

Thanks for letting us know what the problem was.

Regards - Charles

 

Glad to hear your frustration may be over. As a general rule "store-bought" memory, while adequate, isn't going to be exceptional. You're also going to wind up paying a premium for something somewhat marginal. On the other hand, with a little research and some time invested in customer reviews and motherboard manufacturer's recommendations, one can get top quality memory from several on-line retailers without paying an arm and two legs.

Regards,