Help Please

[joker007]

I will check the PSU tomorrow night. I replaced the cmos battery the other day so it is all clear. Will let you know how the PSU check goes. Thanks again for everyones help so far.

 

[ickymay]

adding another stick can change the timings slightly then making your system unstable and the fact the bios doesn't detect and set correct timings suggests to me the ram is not an ideal match to your motherboard

Ideally you need to find the exact spec make model number for your ram and see if you can find it on the tested ram list >> View attachment 83502 provided by msi ?

A great program for accurately identifying ram is CPU-Z

have you been to the msi site to make sure you have the latest bios and chipset drivers ?

 

[joker007]

Hi all. Regarding the RAM, it ran 100% stable with my nvidia 8800GTS 512mb at 800mhz. No probs for 3 years. Its only since I went to the HD 5850 that I've had problems which leads me to suspect either the card just doesn't like my RAM running at 800mhz (which the nvidia was fine with) or my system just can't stand ATI drivers. I use cpu-z and Core temp to monitor hardware and am using the latest bios for the motherboard. Regarding the chipset drivers, the only ones listed are for vista 64 bit not windows 7. Is it worth putting these on? They were released in 2008 and as the mobo is quite old now MSI don't really support it anymore.
I have tested my PSU with a multimeter at POST, Boot, Windows Start up, System Idle, System load and shutting down. The reading on the 12 volt rail was a consistent 12.15volts throughout all tests. The 5 volt rail was a consistent 5.14volts, and finally the 3.3 volt rail consistently raed 3.38 volts which rules a PSU problem out. What else apart from RAM could cause the artifacts and crashing? I have noticed the hard disk clunking a bit more lately. Could this cause the problems? It showed no errors in dskchk. I'm currently running the 4 gb RAM at 667mhz to see if things remain stable. The one positive is that I don't have to RMA any of my new components, just wish I could have a stable system to run them on!

 

[ickymay]

It is very likely the unsupported chipset could be the root of your problems

 

[joker007]

Well it dosn't look like a RAM issue as I have just had another crash. Have attached the minidump file if you would be kind enough to have a look. I am going to email MSI technical support about the chipset drivers. In the mean time I may just install the ones on the website as they are compatible with Vista 64 bit.

 

[ickymay]

Well it dosn't look like a RAM issue as I have just had another crash. Have attached the minidump file if you would be kind enough to have a look. I am going to email MSI technical support about the chipset drivers. In the mean time I may just install the ones on the website as they are compatible with Vista 64 bit.

this crash is REFERENCE_BY_POINTER BugCheck 18 and for this error it's very likely to be a driver ?

MSDN suggests

1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.

personally I think this should be solvable by updating your drivers?

It is significant when looking at the drivers present in the crash .dmp I can see 75% of them are from May and July of 2009 ?

Can you vigorously go through all of your hardware, and using the manufacturers websites make sure you have all of the latest drivers ?

It also wouldn't hurt to run a virus check ?

It would also be a good idea to run a disk check ?

of course this could all lead back to the idea that your graphics card and drivers just will not work with your chipset

for reference heres the output from debugger

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


Loading Dump File [D:\downloads\070710-29531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Wed Jul  7 17:47:27.901 2010 (UTC + 1:00)
System Uptime: 0 days 0:11:50.854
Loading Kernel Symbols
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[B]BugCheck 18, {0, fffffa8005ffaef0[/B], 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46451 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8005ffaef0, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
	The reference count of an object is illegal for the current state of the object.
	Each time a driver uses a pointer to an object the driver calls a kernel routine
	to increment the reference count of the object. When the driver is done with the
	pointer the driver calls another kernel routine to decrement the reference count.
	Drivers must match calls to the increment and decrement routines. This bugcheck
	can occur because an object's reference count goes to zero while there are still
	open handles to the object, in which case the fourth parameter indicates the number
	of opened handles. It may also occur when the object’s reference count drops below zero
	whether or not there are open handles to the object, and in that case the fourth parameter
	contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c67fac to fffff80002cd0600

STACK_TEXT:  
fffff880`02926428 fffff800`02c67fac : 00000000`00000018 00000000`00000000 fffffa80`05ffaef0 00000000`00000002 : nt!KeBugCheckEx
fffff880`02926430 fffff800`02fccf09 : fffff880`02926ca0 fffff880`02926810 00000000`0000001e 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x46451
fffff880`02926490 fffff800`02fcd7d6 : fffff880`02fd3101 00001f80`00d100dc fffffa80`00000001 00000000`00000001 : nt!ObpWaitForMultipleObjects+0x2d3
fffff880`02926960 fffff800`02ccf853 : fffffa80`05ffa060 00000000`00c0fb08 fffff880`02926bc8 fffff880`02926c00 : nt!NtWaitForMultipleObjects+0xe5
fffff880`02926bb0 00000000`7788046a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c0fae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7788046a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46451
fffff800`02c67fac cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46451

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+46451

BUCKET_ID:  X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+46451

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

3: kd> !object 02fccf09
GetUlongFromAddress: unable to read from fffff80002f08010

3: kd> !object fffffa8005ffaef0
GetUlongFromAddress: unable to read from fffff80002f08010
Could not read ObjectType address

as you can see I ran the command kd> !object address where the address was fffffa8005ffaef0 but the returned error was

GetUlongFromAddress: [B]unable to read from fffff80002f08010[/B]
Could not read ObjectType address

 

[joker007]

Thanks a lot for this Ickymay. Strange about the drivers. I know regarding hardware that I am running the latest drivers for my system. I have run several virus scans and disk checks which returned nothing. The thing I find really strange is that when I'm running 3d applications like games the PC is 100% stable. Its just at desktop running 2D that I have problems. Would it be worth formatting and starting again? I have already done this recently but wasn't running the latest chipset drivers. It wouldn't be too much bother as I have all personal data on another hard drive.

 

[ickymay]

Thanks a lot for this Ickymay. Strange about the drivers. I know regarding hardware that I am running the latest drivers for my system. I have run several virus scans and disk checks which returned nothing. The thing I find really strange is that when I'm running 3d applications like games the PC is 100% stable. Its just at desktop running 2D that I have problems. Would it be worth formatting and starting again? I have already done this recently but wasn't running the latest chipset drivers. It wouldn't be too much bother as I have all personal data on another hard drive.

the only reason I can see to format would be so you could try and emulate the crash with nothing but windows installed , which cuts down the variables ?

 

[joker007]

I wanted to format for that reason exactly. Just a fresh Windows install with only what I needed installed. It was stable for a couple of hours and then crashed again. Really struggled to get the PC to post even with clearing the cmos. Eventually managed to get the PC to boot and I have now tried something else. Being as the system is 100% stable when gaming I have tried to replicate the conditions the PC is in when in 3d mode. I haven't disabled powerplay on the GPU but I have disabled intel speedstep as the CPU was constantly throttling and I had a feeling the GPU didn't seem to like this. Anyway the PC has been stable all day so I'm crossing everything that it stays that way! I can only hope! Its very strange as the 8800GTS was fine with speedstep but we'l have to see. I will let you know if this has solved my crashes in a couple of days. If not back to square one. A big thank you to everyone that took the time to help me. Much appreciated.

 

[ickymay]

I wanted to format for that reason exactly. Just a fresh Windows install with only what I needed installed. It was stable for a couple of hours and then crashed again. Really struggled to get the PC to post even with clearing the cmos. Eventually managed to get the PC to boot and I have now tried something else. Being as the system is 100% stable when gaming I have tried to replicate the conditions the PC is in when in 3d mode. I haven't disabled powerplay on the GPU but I have disabled intel speedstep as the CPU was constantly throttling and I had a feeling the GPU didn't seem to like this. Anyway the PC has been stable all day so I'm crossing everything that it stays that way! I can only hope! Its very strange as the 8800GTS was fine with speedstep but we'l have to see. I will let you know if this has solved my crashes in a couple of days. If not back to square one. A big thank you to everyone that took the time to help me. Much appreciated.

good call then , please keep us posted

 

[joker007]

Hi all. Just a quick update on the crashing situation. Unfortunately the PC crashed again even with speedstep disabled and i had visual artifacting even on the post screen which locked up. I decided to remove my audigy sound card as its getting on a bit and is by far the oldest component in my system. I hadn't been experiencing sound problems but thought I would give it a go. Anyway, since the uninstall 2 days ago the system has been completely stable with no problems to report. I am hoping its the sound card and not the PCI slot. I have ordered an Asus Xonar D1 so will try it in the same slot to make sure the slot is ok. Have you ever seen sound card faults causing the kind of visual artifacts I have been experiencing? Like the pictures I posted earlier in the thread?

 

[ickymay]

Hi all. Just a quick update on the crashing situation. Unfortunately the PC crashed again even with speedstep disabled and i had visual artifacting even on the post screen which locked up. I decided to remove my audigy sound card as its getting on a bit and is by far the oldest component in my system. I hadn't been experiencing sound problems but thought I would give it a go. Anyway, since the uninstall 2 days ago the system has been completely stable with no problems to report. I am hoping its the sound card and not the PCI slot. I have ordered an Asus Xonar D1 so will try it in the same slot to make sure the slot is ok. Have you ever seen sound card faults causing the kind of visual artifacts I have been experiencing? Like the pictures I posted earlier in the thread?

yes and it's likely you have found your problem piece of hardware and hopefully solved it

 

[joker007]

I'm crossing everything that it is finally sorted. I will give it a week to be sure then post back with the outcome so the thread can be closed. Once again thanks to everyone that has taken the time to help me.

 

[CarlTR6]

Good to hear of your progress; I hope it is the solution.

 

[joker007]

Thought it was too good to be true. All these days without a crash or lock up and then its started again! Oredered my new sound card aswell! Unfortunately, the lock up didn't create a mini dmp file. I had to reset the PC and leave the power off for 10 mins just to get it to post. I just wish I had a spare motherboard I could try. If it was the chipset drivers not being compatible with the HD 5850 then it wouldn't crash with my old 1900xt which it does. I think I'm going to borrow an nvidia card off someone and see what happens. The thing that is strange is that when my system finally boots it informs me that previous overclocking has failed and settings have been reset to default. My system is not overclocked and is completely at stock settings. Could this be a sign of a failing motherboard? If so why would my system be rock stable when stressing it the most when gaming? It still points to 2d speeds and ATI cards with windows 7 64bit. Is it maybe worth trying xp 32bit just to see if its stable?

 

[ickymay]

with your symptoms i would be checking PSU ?

then checking my CPU was running at the recommended clock speed and voltage ?

then checking in BIOS to make sure my RAM was at correct timings and voltages ?

 

[joker007]

Hi Icky. Everything like that has been checked. I posted the results of my psu voltages earlier in the thread. Cpu is running at stock. All temps are fine. It seems to happen about 10 minutes after Windows has loaded. It just did it again but this time it created a BSOD which I will attach generated dmp.
Fault was REFERENCE BY POINTER

 

[CarlTR6]

Stop error 18, Reference by pointer: Usual causes: Device driver, kernel, hardware

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


Loading Dump File [C:\Users\Owner\Downloads\071610-21156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[url=http://msdl.microsoft.com/download/symbols]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Fri Jul 16 09:07:26.899 2010 (GMT-4)
System Uptime: 0 days 0:04:12.727
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa8005485620, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46451 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8005485620, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002a0cfac to fffff80002a75600

STACK_TEXT:  
fffff880`0674d428 fffff800`02a0cfac : 00000000`00000018 00000000`00000000 fffffa80`05485620 00000000`00000002 : nt!KeBugCheckEx
fffff880`0674d430 fffff800`02d71f09 : fffff880`0674dca0 fffff880`0674d720 00000000`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x46451
fffff880`0674d490 fffff800`02d727d6 : 00000000`00000001 fffff8a0`026441d0 00000000`00000001 00000000`00ecf600 : nt!ObpWaitForMultipleObjects+0x2d3
fffff880`0674d960 fffff800`02a74853 : fffffa80`054b6060 00000000`00ecf418 fffff880`0674dbc8 00000000`00000001 : nt!NtWaitForMultipleObjects+0xe5
fffff880`0674dbb0 00000000`7756030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ecf3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7756030a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46451
fffff800`02a0cfac cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46451

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46451

BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46451

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

2: kd> lmtsmn
start             end                 module name
fffff880`04866000 fffff880`048a4000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00fa4000 fffff880`00ffb000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c5c000 fffff880`02ce6000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03e8f000 fffff880`03ea5000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00dd6000 fffff880`00de1000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`07271000 fffff880`0727c000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00c86000 fffff880`00c8f000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00dac000 fffff880`00dd6000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`048a7000 fffff880`04f83000   atikmdag atikmdag.sys Thu May 27 12:47:58 2010 (4BFEA23E)
fffff880`03ea8000 fffff880`03eee000   atikmpag atikmpag.sys Thu May 27 12:25:36 2010 (4BFE9D00)
fffff880`0192f000 fffff880`01936000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`019db000 fffff880`019ec000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`06948000 fffff880`06966000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`006b0000 fffff960`006d7000   cdd      cdd.dll      unavailable (00000000)
fffff880`058f8000 fffff880`05915000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`018cf000 fffff880`018f9000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e31000 fffff880`00ef1000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01869000 fffff880`01899000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cf1000 fffff880`00d4f000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0114e000 fffff880`011c1000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`03e7f000 fffff880`03e8f000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`05915000 fffff880`05923000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02ddb000 fffff880`02df9000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02dcc000 fffff880`02ddb000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01200000 fffff880`01216000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`058c4000 fffff880`058e6000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`0592f000 fffff880`05938000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05923000 fffff880`0592f000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05938000 fffff880`0594b000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`058ec000 fffff880`058f8000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`03eee000 fffff880`03fe2000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04f83000 fffff880`04fc9000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`04800000 fffff880`04848000   e1e6032e e1e6032e.sys Tue Mar 24 14:17:23 2009 (49C923B3)
fffff880`04fed000 fffff880`04ffa000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`010dc000 fffff880`010f0000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0425a000 fffff880`04265000   flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`01090000 fffff880`010dc000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013f6000 fffff880`01400000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`011c1000 fffff880`011fb000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01587000 fffff880`015d1000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02fe1000 fffff800`0302a000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04fc9000 fffff880`04fed000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05986000 fffff880`0599f000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`0599f000 fffff880`059a7080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05978000 fffff880`05986000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`06880000 fffff880`06948000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`015eb000 fffff880`015f4000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`00e20000 fffff880`00e28000   intelide intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01826000 fffff880`0183c000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`0433d000 fffff880`0434c000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`059a8000 fffff880`059b6000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bae000 fffff800`00bb8000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`0435d000 fffff880`043a0000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013cb000 fffff880`013e5000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0155c000 fffff880`01587000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`058e6000 fffff880`058eb200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`05600000 fffff880`05615000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`059d6000 fffff880`059f9000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c99000 fffff880`00cdd000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`0594b000 fffff880`05959000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`0434c000 fffff880`0435b000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`059b6000 fffff880`059c3000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`018f9000 fffff880`01926000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`0738b000 fffff880`0739b000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`06966000 fffff880`0697e000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0697e000 fffff880`069ab000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`069ab000 fffff880`069f9000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`06800000 fffff880`06823000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01994000 fffff880`0199f000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e09000 fffff880`00e13000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010f0000 fffff880`0114e000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02dc1000 fffff880`02dcc000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015d9000 fffff880`015eb000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0140a000 fffff880`014fc000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03fe2000 fffff880`03fee000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`042b8000 fffff880`042e7000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04265000 fffff880`0427a000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d5a000 fffff880`02d69000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02ce6000 fffff880`02d2b000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`014fc000 fffff880`0155c000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0199f000 fffff880`019b0000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02db5000 fffff880`02dc1000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a05000 fffff800`02fe1000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`01228000 fffff880`013cb000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01926000 fffff880`0192f000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02d34000 fffff880`02d5a000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`03e62000 fffff880`03e7f000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00d82000 fffff880`00d97000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d4f000 fffff880`00d82000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e28000 fffff880`00e2f000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013e5000 fffff880`013f6000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06c7c000 fffff880`06d22000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05887000 fffff880`058c4000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00cdd000 fffff880`00cf1000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0183c000 fffff880`01860000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`042e7000 fffff880`04302000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04302000 fffff880`04323000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04323000 fffff880`0433d000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`01979000 fffff880`01982000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01982000 fffff880`0198b000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0198b000 fffff880`01994000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0104c000 fffff880`01086000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`05615000 fffff880`0562d000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05657000 fffff880`05886800   RTKVHD64 RTKVHD64.sys Wed Mar 17 04:49:15 2010 (4BA0978B)
fffff880`06d22000 fffff880`06d2d000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`03e56000 fffff880`03e62000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02d69000 fffff880`02d86000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015d1000 fffff880`015d9000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`07200000 fffff880`07271000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`072f3000 fffff880`0738b000   srv      srv.sys      Tue Dec 08 03:32:55 2009 (4B1E0F37)
fffff880`06d6c000 fffff880`06dd5000   srv2     srv2.sys     Mon Jul 13 19:25:02 2009 (4A5BC24E)
fffff880`06d2d000 fffff880`06d5a000   srvnet   srvnet.sys   Tue Dec 08 03:32:26 2009 (4B1E0F1A)
fffff880`0435b000 fffff880`0435c480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`06d5a000 fffff880`06d6c000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`019ce000 fffff880`019db000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`019b0000 fffff880`019ce000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02da1000 fffff880`02db5000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00500000 fffff960`0050a000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01800000 fffff880`01826000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`043a0000 fffff880`043b2000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05959000 fffff880`05976000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`05976000 fffff880`05977f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04855000 fffff880`04866000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04200000 fffff880`0425a000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`03e00000 fffff880`03e56000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04848000 fffff880`04855000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00e13000 fffff880`00e20000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01936000 fffff880`01944000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01944000 fffff880`01969000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00d97000 fffff880`00dac000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d86000 fffff880`02da1000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01969000 fffff880`01979000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ef1000 fffff880`00f95000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f95000 fffff880`00fa4000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d2b000 fffff880`02d34000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000c0000 fffff960`003cf000   win32k   win32k.sys   Sat May 01 11:06:30 2010 (4BDC4376)
fffff880`00e00000 fffff880`00e09000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`059c3000 fffff880`059d5100   xusb21   xusb21.sys   Thu Aug 13 18:10:17 2009 (4A848F49)

Unloaded modules:
fffff880`01899000 fffff880`018a7000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018a7000 fffff880`018b3000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018b3000 fffff880`018bc000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018bc000 fffff880`018cf000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Unfortunately, the dump does not point to a particular driver or hardware item. Since you have tested your hardware, let's try enabling Driver Verifier again and running it for 36 hours.

 

[joker007]

Hi Carl. I'm pretty sure its hardware as it locked up in safe mode and bios earlier. I've gone back to one stick of RAM and it seemed stable so I've put the other stick in but i've got them in the other two sockets to see if that makes a difference. So far so good, been ok for a couple of hours but early days yet. Will post back tomorrow with progress report.

 

[CarlTR6]

If it is locking up in BIOS, that is a sure sign it is hardware. Thanks and let us know.