Random Restarts with new install of windows 7

kungfujack · 06 Aug 2010

Hello all,

Thank you in advance for any help you may give.

I have been battling random BSOD, restarts and freezes for the past 2 weeks. I have been able to restore a good bit of stability to my system but I am still experiencing random restarts and shut downs. I have attached the most recent dump file from one of these restarts. Could anyone take a look at this and possibly point me in the right direction? It would be much appreciated.

Thank you

kungfujack · 06 Aug 2010

Update: I just recieved another bsod.

Error: reference_by_pointer

0x00000081

attached is another minidump

Since my problems began I have run memtest for 28 passes and no errors were found. I have changed out PSU and problems were still happening. I removed my vid card and problems persisted. I cleaned all dust around cpu and fans. Speed fan shows the following:

Temp1: 27C
Temp2: 51C
Temp3: 25C
Core: 33C
GPU: 69C

Jonathan_King · 07 Aug 2010

Welcome!

Please enable driver verifier: Driver Verifier - Enable and Disable

Also, update your Conextant Diagnostics software.

...Summary of the Dumps:

Code:


Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Aug  6 21:06:26.763 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:32.464
BugCheck 1000008E, {c0000005, 82c232bb, 96913ae4, 0}
Probably caused by : ntkrpamp.exe ( nt!ObpLookupDirectoryUsingHash+76 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  WUDFHost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Aug  6 21:05:06.847 2010 (UTC - 4:00)
System Uptime: 0 days 2:47:15.688
BUGCHECK_STR:  0x18
PROCESS_NAME:  plugin-contain
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

After Verifier has caused several BSODs, please follow these directions, rather than uploading just the dumps: https://www.sevenforums.com/crashes-d...tructions.html

kungfujack · 08 Aug 2010

Sorry for the confusion, I'm pretty new to all of this.

I have done as instructed...i think. I am do not know what conextant diagnostic software means, i googled it but I'm still a bit confused, sorry again. I have attached the zipped folder as requested. Please let me know if this is correct.

Thank you

ttran · 08 Aug 2010

If you've enabled Driver Verifier follow instruction JK post, please wait for your system to crash and upload the newest DMP.
In the meantime, please Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Code:

BugCheck 19, {20, 87495840, 87495848, 8010009}

GetPointerFromAddress: unable to read from 82b6a718
Unable to read MiSystemVaType memory at 82b4a160
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+1b1 )

Followup: MachineOwner
---------
BugCheck 1A, {41284, 1501c001, 279d, c0802000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

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

Please type in cmd command window :
verifier /query to Displays a summary of Driver Verifier's current activity

kungfujack · 09 Aug 2010

Ok, I have had a couple crashes since then. Here is the newest dump file.

I have ran memtest a couple times without error, the longest run being 26 passes. However, I have been experimenting with my ram. My PC came with the following ram:

3GB total:
1gb DDR2, 667, CL5 x2 Brand= MTSHTF (not sure about this, but its the only resemblence of a brand name I could find on the sticks)
512MB DDR2 Brand=Samsung

I tried my system with different combos of each, 1gb at a time, the two 512's at a time and everything seems ok, BUT when I put them together things seems to get hairy. The first time I put back all four sticks i got a blue screen within seconds of windows loading, the second time i couldnt even get to the login screen. I removed sticks as to make them matching, running the two samsungs together, and then the two 1gb together and no blue screens (again the testing time isn't very long). When i mismatched one 1gb and one 512 I got a blue screen before the loading windows screen came up. Could this be the problem? I have been using this ram together for about 3 years, why would it only now start not liking each other?

ttran · 09 Aug 2010

There is no DMP file in the one you just uploaded. Make sure you run the tool in the posting instruction as administrator right. Othewise, just simply do this to upload the newest DMP:

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

Also, Which memtest did you use? I don't trust the built in memtest at all, please use Memtestx86, do it at least 7 passes and 7 passes should take at least 9 hours to finish

kungfujack · 09 Aug 2010

Sorry about that. Here they are.

ttran · 09 Aug 2010

Thanks

Things look more obvious now, at this point I really suspect the graphic card.

STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

First thing to try is to reinstall the driver, When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using http://www.guru3d.com/category/driversweeper/

When it is removed then download and install the fresh copy.
When you update graphic card, update directx as well:
Download details: DirectX End-User Runtime

Also, see if you can borrow different graphic card to try on your system, at this point, it looks pretty obvious to be the cause. Stop code 50 is usually hardware come into play and your graphic card driver was blamed in there.

BUGCHECK SUMMARY:

Code:

BugCheck 50, {db706145, 1, 8ede928d, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

Could not read faulting driver name
Probably caused by : hardware ( nvlddmkm+3d028d )

Followup: MachineOwner
---------
BugCheck 1000008E, {c0000005, 82ae42a3, 9ac6fc18, 0}

Probably caused by : memory_corruption ( nt!MiGetPreviousNode+32 )

Followup: MachineOwner
---------
BugCheck 1A, {41201, c000ddb8, 3fb51867, 9127b230}

Probably caused by : memory_corruption ( nt!MiGetPageProtection+1a6 )

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

Also, use memtestx86 to test your Ram and tell me the result
If it report error: Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots. If all slots ok and all individual stick are ok, it's probably compatibility issue

Good Luck,

Tuan

kungfujack · 12 Aug 2010

Thanks guys for all the help. I believe I have found the problem. It seems to be a bad ram slot on my mobo. I removed the stick of ram from that slot and my computer has not had any issues since Sunday morning. Hopefully this will continue to be the case.