I need HELP!!!!!!!

pebbly · 14 Mar 2010

LilDomii said:

Oh.

never mind Lil' Dom , it happens to me all the time

Dom · 14 Mar 2010

Lol

JMH · 14 Mar 2010

pebbly said:

LilDomii said:

Oh.

never mind Lil' Dom , it happens to me all the time

And that is the invaluable learning curve.....
[I'm watching this unfold with great interest.]

pebbly · 14 Mar 2010

JMH said:

pebbly said:

LilDomii said:

Oh.

never mind Lil' Dom , it happens to me all the time

And that is the invaluable learning curve.....
[I'm watching this unfold with great interest.]

so am i ,cant wait for the next episode

jcgriff2 · 14 Mar 2010

Those were 11 very interesting kernel dumps you attached a few pages back.

One of the bugchecks - 0x51

0x51 = Registry error

To quote Microsoft -

Cause

Something has gone wrong with the registry.

This error may indicate that the registry encountered an I/O error while trying to read one of its files. This can be caused by hardware problems or file system corruption.

It may also occur due to a failure in a refresh operation, which is used only in by the security system, and then only when resource limits are encountered.

The Windows installer was running at the time.

Remove AVG - you have a version installed that has caused problems in the past.

AVG Removal --> AVG Antivirus and Security Software - Tools download

Reboot upon removal.

Install Microsoft Security Essentials --> http://www.microsoft.com/Security_Essentials/

Update these drivers -

Code:

nvlddmkm.sys Thu May 14 16:48:07 2009 (4A0C8387) - NVIDIA Video
Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D) - Realtek Ethernet

Another dump mentioned ntfs.sys = NTFS file system = hard drive

Run chkdsk /r

Regards. . .

jcgriff2

.

DETAILED BUGCHECK SUMMARY

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 11 19:38:38.162 2010 (GMT-4)
System Uptime: 0 days 0:02:37.019
BugCheck 51, {1, fffff8a000668010, 29000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+9b7a )
BUGCHECK_STR:  0x51
PROCESS_NAME:  msiexec.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 13 00:29:50.572 2010 (GMT-4)
System Uptime: 0 days 0:00:14.476
BugCheck A, {0, 2, 0, fffff800028eec06}
Probably caused by : Pool_Corruption ( nt!ExFreePool+d4d )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 13 00:21:16.338 2010 (GMT-4)
System Uptime: 0 days 0:00:14.242
BugCheck A, {fffff80002c76ea6, 2, 0, fffff800028b7f62}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 23:51:42.074 2010 (GMT-4)
System Uptime: 0 days 2:28:21.588
BugCheck C1, {fffff9801257ac10, fffff9801257a443, f303e8, 23}
Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 21:04:28.850 2010 (GMT-4)
System Uptime: 0 days 0:00:17.364
BugCheck D1, {fffff88001336a6c, 2, 8, fffff88001336a6c}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+5c0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 20:42:20.375 2010 (GMT-4)
System Uptime: 0 days 8:33:28.310
BugCheck 1A, {5003, fffff90000812000, 1657, 163e000043fe}
Probably caused by : win32k.sys ( win32k!memset+b0 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 11:58:51.026 2010 (GMT-4)
System Uptime: 0 days 0:00:13.962
BugCheck A, {fffff80002c6b29a, 2, 0, fffff800028b3f62}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 09:50:17.668 2010 (GMT-4)
System Uptime: 0 days 0:00:14.182
BugCheck BE, {fffff80002bd5230, 3c0000002bd5121, fffff880031b5f10, a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40a84 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 05:46:01.574 2010 (GMT-4)
System Uptime: 0 days 0:30:12.088
BugCheck A, {48, 2, 1, fffff8000293fabf}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 11 21:04:43.312 2010 (GMT-4)
System Uptime: 0 days 0:00:11.826
BugCheck D3, {fffff88000e70824, 2, 0, fffff800028e7f62}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD3
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 11 19:01:19.780 2010 (GMT-4)
System Uptime: 0 days 0:41:31.782
BugCheck A, {fffffa0003d41460, 2, 1, fffff8000289a906}
Probably caused by : memory_corruption ( nt!MiRemoveUnusedSegment+96 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
by jcgriff2   
 
J. C. Griffith, Microsoft MVP 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

pebbly · 14 Mar 2010

thank you jcgriff2 that may be of great help to the OP

win7clutz · 14 Mar 2010

If he's using the stock cooler that comes with the retail cpu ,the thermal compound was already on the cooler and very likely he wouldn't even have noticed it... I haven't seen any temps posted so thermal problems at this point are just SWAG engineering.

Additionally, mini-dumps, loaded applications, OS updates and the majority of the conversation in this thread is totally irrelevant until he can validate the hardware.

Until he can successfully boot to and complete several runs of Memtest, nothing else matters, the box will never be stable…

dmcouch1975 · 15 Mar 2010

I did the Window Diagnostic Test let it run 10 times with only 1 stick of RAM and passed with no hardware errors but when I put in 2 sticks it tells me I have a hardware Error but never tells me what it is. I put the RAM in just like the motherboard manual says too in slots 1 and 3 I don't think there is any other option but the motherboard....

pebbly · 15 Mar 2010

dmcouch , you will have to try the ram sticks seperately, we need to eliminate those from the equation, then we can move on to the next step :)

dmcouch1975 · 15 Mar 2010

I did check all the sticks one at a time and they all passed. I did it with the INTEL BURN TEST program on the maximun stress setting

I need HELP!!!!!!!

Memory Diagnostic test

RAM