Windows Rebooting [DUMP Data]

I have recently re-installed XP Pro and SP2.

All worked great for a week or so, but now when I start the PC it reboots about 4 or 5 times at the Welcome Screen or the XP loading Icon. It eventually boots up and I get the message saying Windows recovered from a serious error. I have two files that have been generated with info about this problem. One is an.xml file the other a .dmp file.

Am I allowed to post them here in case anyone can decipher them?

System is virus and spyware free and all hardware has been fine up until now.

 

The dump file may be of some help. I can't decypher them but there's a few here that can. Go here and follow Joe's instructions.

 

I should have also asked, have you installed any new software or hardware that could be the cause? Can you boot to safemode without getting the error?

 

Hi Zander - no new software installed. I had been playing a game and switched off as normal. Next day I get this problem. got the message to choose last configuration that worked - and same problem occured.

 

Here is the rather lengthy dump. If it means anything to anyone I would be grateful for your help.

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Documents and Settings\silvercue\Desktop\Mini032105-02.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
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Mon Mar 21 08:54:15.421 2005 (GMT+0)
System Uptime: 0 days 0:00:43.000
Loading Kernel Symbols
.............................................................................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 7f4e1af9, b729bc9c, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
*** Possible invalid call from 8056fef7 ( nt!NtDelayExecution+0x82 )
*** Expected target 804e1af9 ( nt!KeDelayExecutionThread+0x0 )

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 7f4e1af9, The address that the exception occurred at
Arg3: b729bc9c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
+7f4e1af9
7f4e1af9 ?? ???

TRAP_FRAME: b729bc9c -- (.trap ffffffffb729bc9c)
.trap ffffffffb729bc9c
ErrCode = 00000000
eax=b729bd2c ebx=0079ffac ecx=00000000 edx=0079ffa4 esi=0079ffac edi=b729bd64
eip=7f4e1af9 esp=b729bd10 ebp=b729bd54 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
7f4e1af9 ?? ???
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 8056fefc to 7f4e1af9

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b729bd0c 8056fefc 0079fc01 00000001 b729bd2c 0x7f4e1af9
b729bd54 804ddf0f 00000001 0079ffac 0079ffb4 nt!NtDelayExecution+0x87
b729bd54 7c90eb94 00000001 0079ffac 0079ffb4 nt!KiFastCallEntry+0xfc
0079ff98 7c90d85c 7c9279d4 00000001 0079ffac 0x7c90eb94
0079ffb4 7c80b50b 00000000 7ffdd000 0075fbb4 0x7c90d85c
0079ffec 00000000 7c92798d 00000000 00000000 0x7c80b50b


POSSIBLE_INVALID_CONTROL_TRANSFER: from 8056fef7 to 804e1af9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .trap ffffffffb729bc9c ; kb

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
---------
*** Possible invalid call from 8056fef7 ( nt!NtDelayExecution+0x82 )
*** Expected target 804e1af9 ( nt!KeDelayExecutionThread+0x0 )

eax=b729bd2c ebx=0079ffac ecx=00000000 edx=0079ffa4 esi=0079ffac edi=b729bd64
eip=7f4e1af9 esp=b729bd10 ebp=b729bd54 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
7f4e1af9 ?? ???
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
b729bd0c 8056fefc 0079fc01 00000001 b729bd2c 0x7f4e1af9
b729bd54 804ddf0f 00000001 0079ffac 0079ffb4 nt!NtDelayExecution+0x87 (FPO: [Non-Fpo])
b729bd54 7c90eb94 00000001 0079ffac 0079ffb4 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ b729bd64)
0079ff98 7c90d85c 7c9279d4 00000001 0079ffac 0x7c90eb94
0079ffb4 7c80b50b 00000000 7ffdd000 0075fbb4 0x7c90d85c
0079ffec 00000000 7c92798d 00000000 00000000 0x7c80b50b
start end module name
804d7000 80701000 nt ntkrnlmp.exe Wed Aug 04 07:18:18 2004 (41107FAA)
80701000 80721d00 hal halmacpi.dll Wed Aug 04 06:59:09 2004 (41107B2D)
b6646000 b6698180 srv srv.sys Wed Aug 04 07:14:44 2004 (41107ED4)
b66c1000 b66e8f00 secdrv secdrv.sys Tue Aug 31 14:42:55 2004 (4134805F)
b67d9000 b6805400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
b7274000 b7277280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
b843f000 b8482180 dump_iaStor dump_iaStor.sys Tue Jun 17 19:10:20 2003 (3EEF598C)
b8483000 b84a6000 Fastfat Fastfat.SYS Wed Aug 04 07:14:15 2004 (41107EB7)
b8546000 b85c80e0 avg7core avg7core.sys Mon Feb 21 00:58:26 2005 (42193232)
b85f1000 b865f400 mrxsmb mrxsmb.sys Wed Jan 19 04:26:50 2005 (41EDE18A)
b8660000 b868aa00 rdbss rdbss.sys Thu Oct 28 02:13:57 2004 (418047D5)
b868b000 b86acd00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
b86ad000 b86f0000 vsdatant vsdatant.sys Wed Jan 26 09:14:04 2005 (41F75F5C)
b86f0000 b8717c00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
b8718000 b8738f00 ipnat ipnat.sys Wed Sep 29 23:28:36 2004 (415B3714)
b8739000 b8790a80 tcpip tcpip.sys Wed Aug 04 07:14:39 2004 (41107ECF)
b8791000 b87a3400 ipsec ipsec.sys Wed Aug 04 07:14:27 2004 (41107EC3)
b8850000 b8852f80 mouhid mouhid.sys Fri Aug 17 21:47:57 2001 (3B7D82FD)
b8858000 b885a580 hidusb hidusb.sys Fri Aug 17 22:02:16 2001 (3B7D8658)
ba964000 ba997200 update update.sys Wed Aug 04 06:58:32 2004 (41107B08)
ba998000 ba9c8100 rdpdr rdpdr.sys Wed Aug 04 07:01:10 2004 (41107BA6)
ba9c9000 ba9d9e00 psched psched.sys Wed Aug 04 07:04:16 2004 (41107C60)
baa3a000 baa42d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 07:08:18 2004 (41107D52)
baa7a000 baa90680 ndiswan ndiswan.sys Wed Aug 04 07:14:30 2004 (41107EC6)
baa91000 baab3680 ks ks.sys Wed Aug 04 07:15:20 2004 (41107EF8)
baab4000 baad7980 portcls portcls.sys Wed Aug 04 07:15:47 2004 (41107F13)
baad8000 bab341c0 cmaudio cmaudio.sys Mon Nov 18 07:51:39 2002 (3DD89C0B)
bab35000 bab5a800 el90xnd5 el90xnd5.sys Fri Jun 15 23:01:39 2001 (3B2A85C3)
bab5b000 bab7de80 USBPORT USBPORT.SYS Wed Aug 04 07:08:34 2004 (41107D62)
bab7e000 bab91780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 07:07:04 2004 (41107D08)
bab92000 baedd4c0 nv4_mini nv4_mini.sys Thu Feb 24 16:13:44 2005 (421DFD38)
baee6000 baee8280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
baefe000 baf00980 gameenum gameenum.sys Wed Aug 04 07:08:20 2004 (41107D54)
baf10000 baf19480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
baf20000 baf29f00 termdd termdd.sys Wed Aug 04 06:58:52 2004 (41107B1C)
baf30000 baf38900 msgpc msgpc.sys Wed Aug 04 07:04:11 2004 (41107C5B)
baf40000 baf4bd00 raspptp raspptp.sys Wed Aug 04 07:14:26 2004 (41107EC2)
baf50000 baf5a200 raspppoe raspppoe.sys Wed Aug 04 07:05:06 2004 (41107C92)
baf60000 baf6c880 rasl2tp rasl2tp.sys Wed Aug 04 07:14:21 2004 (41107EBD)
baf70000 baf7e080 redbook redbook.sys Wed Aug 04 06:59:34 2004 (41107B46)
baf80000 baf8c180 cdrom cdrom.sys Wed Aug 04 06:59:52 2004 (41107B58)
baf90000 baf9a380 Imapi Imapi.SYS Wed Aug 04 07:00:12 2004 (41107B6C)
bafa0000 bafafd80 serial serial.sys Wed Aug 04 07:15:51 2004 (41107F17)
bafd4000 bafd7c80 mssmbios mssmbios.sys Wed Aug 04 07:07:47 2004 (41107D33)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 07:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 07:00:51 2004 (41107B93)
bf9d3000 bfd9d300 nv4_disp nv4_disp.dll Thu Feb 24 16:08:56 2005 (421DFC18)
f740e000 f7424780 KSecDD KSecDD.sys Wed Aug 04 06:59:45 2004 (41107B51)
f7425000 f7436f00 sr sr.sys Wed Aug 04 07:06:22 2004 (41107CDE)
f7437000 f7455780 fltmgr fltmgr.sys Wed Aug 04 07:01:17 2004 (41107BAD)
f7456000 f7499180 iaStor iaStor.sys Tue Jun 17 19:10:20 2003 (3EEF598C)
f749a000 f74b1480 atapi atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
f74b2000 f74d7700 dmio dmio.sys Wed Aug 04 07:07:13 2004 (41107D11)
f74d8000 f74f6880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
f74f7000 f7503e00 i8042prt i8042prt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
f7507000 f7515b80 drmk drmk.sys Wed Aug 04 07:07:54 2004 (41107D3A)
f7517000 f751fd00 intelppm intelppm.sys Wed Aug 04 06:59:19 2004 (41107B37)
f7527000 f752f880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
f7537000 f753f700 netbios netbios.sys Wed Aug 04 07:03:19 2004 (41107C27)
f7547000 f754f700 wanarp wanarp.sys Wed Aug 04 07:04:57 2004 (41107C89)
f7597000 f75a7a80 pci pci.sys Wed Aug 04 07:07:45 2004 (41107D31)
f75a8000 f75d5d80 ACPI ACPI.sys Wed Aug 04 07:07:35 2004 (41107D27)
f75f7000 f75ffc00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
f7607000 f7611500 MountMgr MountMgr.sys Wed Aug 04 06:58:29 2004 (41107B05)
f7617000 f7623c80 VolSnap VolSnap.sys Wed Aug 04 07:00:14 2004 (41107B6E)
f7627000 f762fe00 disk disk.sys Wed Aug 04 06:59:53 2004 (41107B59)
f7637000 f7643200 CLASSPNP CLASSPNP.SYS Wed Aug 04 07:14:26 2004 (41107EC2)
f7647000 f7651580 agp440 agp440.sys Wed Aug 04 07:07:40 2004 (41107D2C)
f7677000 f7685100 usbhub usbhub.sys Wed Aug 04 07:08:40 2004 (41107D68)
f7707000 f770d200 PCIIDEX PCIIDEX.SYS Wed Aug 04 06:59:40 2004 (41107B4C)
f770f000 f7713900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
f773f000 f7745180 HIDPARSE HIDPARSE.SYS Wed Aug 04 07:08:15 2004 (41107D4F)
f7767000 f776c280 avg7rsxp avg7rsxp.sys Wed Feb 09 01:00:20 2005 (420960A4)
f777f000 f7783880 TDI TDI.SYS Wed Aug 04 07:07:47 2004 (41107D33)
f778f000 f7794000 flpydisk flpydisk.sys Wed Aug 04 06:59:24 2004 (41107B3C)
f7797000 f779c000 usbuhci usbuhci.sys Wed Aug 04 07:08:34 2004 (41107D62)
f779f000 f77a3500 watchdog watchdog.sys Wed Aug 04 07:07:32 2004 (41107D24)
f77af000 f77b3580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
f77bf000 f77c3080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
f77c7000 f77cd800 usbehci usbehci.sys Wed Aug 04 07:08:34 2004 (41107D62)
f77cf000 f77d4200 vga vga.sys Wed Aug 04 07:07:06 2004 (41107D0A)
f77df000 f77e5000 kbdclass kbdclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
f77e7000 f77eba80 Msfs Msfs.SYS Wed Aug 04 07:00:37 2004 (41107B85)
f77f7000 f77fe880 Npfs Npfs.SYS Wed Aug 04 07:00:38 2004 (41107B86)
f77ff000 f7805b00 fdc fdc.sys Wed Aug 04 06:59:25 2004 (41107B3D)
f781f000 f7824a00 mouclass mouclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
f784f000 f7869580 Mup Mup.sys Wed Aug 04 07:15:20 2004 (41107EF8)
f786a000 f7896a80 NDIS NDIS.sys Wed Aug 04 07:14:27 2004 (41107EC3)
f7897000 f789a000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
f793b000 f793d900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
f793f000 f7942c80 serenum serenum.sys Wed Aug 04 06:59:06 2004 (41107B2A)
f794b000 f794d580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
f7987000 f7988b80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
f7989000 f798a100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f798b000 f798c700 dmload dmload.sys Fri Aug 17 21:58:15 2001 (3B7D8567)
f7991000 f7992100 swenum swenum.sys Wed Aug 04 06:58:41 2004 (41107B11)
f7997000 f7998280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
f799b000 f799cf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
f799f000 f79a0080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
f79a3000 f79a4080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
f79a7000 f79a8080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
f79b5000 f79b60e0 avg7rsw avg7rsw.sys Wed Oct 27 16:46:47 2004 (417FC2E7)
f7a4f000 f7a4fd00 pciide pciide.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
f7a6f000 f7a6fc00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
f7a79000 f7a79be0 mbmiodrvr mbmiodrvr.sys Thu Jul 11 01:57:39 2002 (3D2CD803)
f7a8a000 f7a8ada0 aslm75 aslm75.sys Wed Apr 23 02:15:58 1997 (335D62CE)
f7aac000 f7aacd00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
f7ab2000 f7ab2940 SVKP SVKP.sys Mon Mar 10 15:31:42 2003 (3E6CAFDE)
f7ab7000 f7ab7b80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
f7b52000 f7bde480 Ntfs Ntfs.sys Wed Aug 04 07:15:06 2004 (41107EEA)

Unloaded modules:
b67c5000 b67d9000 Parport.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
b87dc000 b87e4000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f77a7000 f77ac000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
baeee000 baef1000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

> .formats 7f4e1af9 = 01111111 01001110 00011010 11111001
> .formats 804e1af9 = 10000000 01001110 00011010 11111001

Well well well.. How in the world did this happen.. EIP is off by a flipped byte/ or something subtracting a byte from the first byte of the instruction. Thats ... odd. My first thought is that your processor malfunctioned. I dont see how this could be bad data... but maybe.

Have we been overclocking?
Is your bios current?
Have you tried pulling one of your ram sticks?
Do you have another dump? (and does it look the same)

 

JoeHobart - thanks for the help.

I have been overclocking, but not more than 10% bus increase and my computer is very well cooled. However, I have not overclocked for a few days before this started. I currently have 4x512 of Low latency RAM at cas - 2.3.2.6. in dual channel mode.

I will try taking the last two sticks I put in out - I am going to RMA them anyway as they fail memtest86+ with as little as 5% overclcok (they are from a manufacturer that sells on the strength of overclocking ability).

Is it possible that this is memory problem?

BIOS is the latest from ASUS. I don't have another dump just yet.

 

do you know what "overclocking" means. It means driving the hardware at a higher speed than the manufacturer was able to run the chip with consistant operation.

as a shareholder in many hardware vendors, trust me when i say, if the chips could handle more speed, they would sell them rated higher, because they would sell better for more profit.

For instance, do you truely understand how catestrophic a failure has to occur to fail memtest? Thats not a minor event. How are you able to determine what kind of damage you are doing without a logic probe and a scope that can handle that kind of hertz? The answer is you cant, you're putting your faith in folks who tell you its ok, but they arent aware of how it affects things either. These guys out there advocating this dont have 50,000$ logic probes either. For all you know, you've popped a gate on the ondie memory controller, which on today's amds is on the very expensive piece of silicon you bought called the cpu.

But sure, crank up that bus, ill look at your dumps all day.

 

got the message to choose last configuration that worked

I tried that a time or two and it never worked either. I find Restore Points to do better.

The first question that I would be asking. ( at least for myself )

Did the game I was playing SHUTDOWN and do its cleanup properly ? Some of todays gaming can be pretty heavy duty stuff and take awhile to really cleanup and shutdown.

I ask this due to a similiar problem I myself have had/created.

MY Wife and I play Golf via the Internet on Tuesday evening with a Freind in Canada. Sometimes it is quite late when we get done. BTW I lose more than win

On one Wednesday morning ths XP Pro machine gave me all kinds of errors and/or excuses for not starting up properly. Well It finally gave up and came up properly. ( after I did a System Restore )

Now the most volital memory of all had to kick in ( the one behind my eyeballs and between my ears )

Apparrently I had not given XP TIME ENOUGH to clean up after shuting down the game. I have found that getting in a HURRY creates me more problems than Microsoft and Windows put together do.

So a few weeks later I tried to duplicate WHAT I THOUGHT created the problem. I shutdown the game and the PC right behind. PROBLEMS again the next AM But as I was getting ready to ( and did ) shutdown I noticed that the little green lights on the Router were still showing activity. When I waited for them to stop there were no problems.

If nothing more there are a few things I have learned about using Windows.
#1 Make sure you have a BACKUP BEFORE making changes.

In 98 making backups was a bit tougher. But with the XP Restore Points There is NO EXCUSE. It is too easy to check and make sure you do have a RP. And in some cases ( yes I have had them ) it can actaully SAVE time

#2 DO NOT get in a big HURRY to go from one thing to the other.

#3 Apprently just because the little lights do not show any activity does not mean there is not any.

#4 Pay attention to the COMBINATION of things that may be running. Many things run fine by themselves but may create problems when run along with something else.

#5 Sometimes it may even be the ORDER in which things are started. In my case I must start Links Golf 2003 and minimize it before I start ICQ in order for ICQ to work properly. And once we get the game started I MUST shut ICQ down. We use ICQ just to make sure the other is online and decide which course we are going to play. Plus he makes sure I have his IP address.

Speaking of IP addresses. 123,456,78,90 does not work. But 123.456.78.90 will. The difference is easy to spot here, But on the game screen believe me it is not.

BillyBob

 

Joe - if you don't want to look at my dumps - then don't. I really don't expect you to waste your time with patronising replies either.

I understand what overclocking means and have overclocked my bus speed with full dialogue with OCZ via their support forums throughout. The memory I have is extremely expensive for a reason - the manufacturers support it as overclockable. And no, it does not take a catastrophe to fail memtest -a lot of the memory you buy new will fail it because so much bad memory is sold. Also you can fail memtest86+ and just adjust some timings and it runs fine. sticks I have that failed came like that and failed before anything was overclocked. OCZ have agreed to RMA them no problem.

I have overclocked for many years with almost no problems at all. If after years and about 7 pcs I have eventually done a little bit of damage - then I have lost nothing. I saved a fortune running hardware faster so I will still be well in credit thanks.

 

BillyBob - I have taken note of your post. The game I was playing was an online Only game and it is rather system heavy. I am sure that I did log out and shut the PC down as quickly as possible. I will see if I can replicate the problem as the PC booted up fine today.

 

silverwork

As a suggestion and another thing learned from some not so nice happening.

Let the PC run for a bit to make sure it is going to stay put.

Then SHUTDOWN and restart System Restore just to make sure you have a RP of a system that is working properly.

Or at least make a new one MANUALLY and check to be sure it is there. I have had SR FAIL on me a couple of times.

I checked my SR points this AM and I saw that there were SEVERAL that were made a fews days ago BEFORE I changed Video Drivers and added some new software But for some odd reason there were NONE after.

All are now gone and a new one made.

I do not. Never have. And never will trust SR on its own.

BillyBob

 

I have made a habbit of making SR points now - when things are running well.

The one time I really needed a SR though - after a corrupt system file and repair console - I could not use them as the Registry was lost/restored..

 

I like that reply.

I have had too many ( way too many ) friends and Family ignor me on the RP point. Well, I will now say this. At least two of them have changed their minds and now make sure the RPs are up to date before messing around.

BillyBob

 

Most people learn better "the hard way ". Myself included.

 

Joe - if you don't want to look at my dumps - then don't.

I am happy to look at your dumps and provide any known solutions i am aware of. Your processor is malfunctioning. You'll notice my very first question is 'are you overclocking'. Thats because i've looked at tens of thousands of dumps. I know what malfing hardware looks like, just as much as I can see a bug in software.


I understand what overclocking means and have overclocked my bus speed with full dialogue with OCZ via their support forums throughout. The memory I have is extremely expensive for a reason - the manufacturers support it as overclockable.
How's that workin out for ya? See your dump for exhibit A.

And no, it does not take a catastrophe to fail memtest -a lot of the memory you buy new will fail it because so much bad memory is sold. Also you can fail memtest86+ and just adjust some timings and it runs fine.
Any time you want to have a discussion about how ram works, I'd be happy to explain to you the difference between misaligned strobe timing, and over driving the frequency and the stresses induced therein. The price you pay is because of the yield, labor to test pop rate, and returns. Its not a different chip, its just luck that it doesnt pop right away. Ask your vendor the die difference between their "certified overclockable" and normal ram. Same fabs, same wafers, same dies, different box.

I really don't expect you to waste your time with patronising replies either.
.. All part of the service I provide. no extra charge. You argue that overclocking is good and saved you money. Its a personal choice, to be sure, but its bad for the hardware, and bad for the software that depends on that hardware to function properly. You came here for help, and then argue with me when I tell you why your machine blowed up. *shrug* You still dont seem to grasp that theres more at play than just your "supported overclockable" ram stick. We arent talking about a sense amplifier failure, something added a byte, or flipped an entire byte range on the retrieve. That didnt come out of your ram that way. That came from somewhere else.

You still owe posting a second dump to see if its the same phenomenon or not.