Windows 7 BSOD and windbg :<

ok so I will start with what I am running:

I built a Windows 7 PC
Intel DP55WB Mother Board
Core i5 cpu (With large cooler Master CPU cooler)
4G DDRIII OCZ RAM
NVIDIA 9800 Vid Card
and added a D-Link gigabit NIC (I disabled the onboard NIC trying to fix this Issue)
LG DVD-R/RW
300g western digital V Raptor HD
1TB Western digital storage drive

I built this machine back in Nov. and have been very busy working on lots of other projects so I have only worked off and on with this to try and fix it.

I am running Win7 pro 64bit

its installed and works great after disabling the on-board NIC, altho I don't shut my comp down. every night or 2 it crashes, the crashes are almost always while its idle. I have tried to check the minidump file but can't seem to get windbg to work right eather.

So I have a comp that wont stay running for more than 24hrs at a time and minidumps I cant read.

heres a copy/paste of the windbg error:
(This includes me trying to run the symfix command)

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


Loading Dump File [C:\Users\Jon\Desktop\050710-15693-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\Symbols;srv*
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Fri May 7 22:00:45.530 2010 (GMT-5)
System Uptime: 2 days 4:43:01.982
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffff00000000, 2, 1, fffff80002ad39e5}

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+809e5 )

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

0: kd> symfix
*** WARNING: Unable to verify timestamp for kdcom.dll
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for mcupdate_GenuineIntel.dll
*** WARNING: Unable to verify timestamp for PSHED.dll
*** WARNING: Unable to verify timestamp for CLFS.SYS
*** WARNING: Unable to verify timestamp for CI.dll
*** WARNING: Unable to verify timestamp for PCIIDEX.SYS
*** WARNING: Unable to verify timestamp for mountmgr.sys
*** WARNING: Unable to verify timestamp for ataport.SYS
*** WARNING: Unable to verify timestamp for amdxata.sys
*** WARNING: Unable to verify timestamp for volmgrx.sys
*** WARNING: Unable to verify timestamp for pciide.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** WARNING: Unable to verify timestamp for WDFLDR.SYS
*** WARNING: Unable to verify timestamp for ACPI.sys
*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** WARNING: Unable to verify timestamp for msisadrv.sys
*** WARNING: Unable to verify timestamp for pci.sys
*** WARNING: Unable to verify timestamp for vdrvroot.sys
*** WARNING: Unable to verify timestamp for partmgr.sys
*** WARNING: Unable to verify timestamp for volmgr.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** WARNING: Unable to verify timestamp for fileinfo.sys
*** WARNING: Unable to verify timestamp for msrpc.sys
*** WARNING: Unable to verify timestamp for cng.sys
*** WARNING: Unable to verify timestamp for volsnap.sys
*** WARNING: Unable to verify timestamp for rdyboost.sys
*** WARNING: Unable to verify timestamp for ksecdd.sys
*** WARNING: Unable to verify timestamp for pcw.sys
*** WARNING: Unable to verify timestamp for Fs_Rec.sys
*** WARNING: Unable to verify timestamp for disk.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** WARNING: Unable to verify timestamp for fwpkclnt.sys
*** WARNING: Unable to verify timestamp for ndis.sys
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** WARNING: Unable to verify timestamp for vmstorfl.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for mup.sys
*** WARNING: Unable to verify timestamp for hwpolicy.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** WARNING: Unable to verify timestamp for tdx.sys
*** WARNING: Unable to verify timestamp for TDI.SYS
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
*** WARNING: Unable to verify timestamp for netbt.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for fastfat.SYS
*** WARNING: Unable to verify timestamp for cdrom.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** WARNING: Unable to verify timestamp for Beep.SYS
*** WARNING: Unable to verify timestamp for vga.sys
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
*** WARNING: Unable to verify timestamp for watchdog.sys
*** WARNING: Unable to verify timestamp for RDPCDD.sys
*** WARNING: Unable to verify timestamp for rdpencdd.sys
*** WARNING: Unable to verify timestamp for rdprefmp.sys
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** WARNING: Unable to verify timestamp for afd.sys
*** WARNING: Unable to verify timestamp for wfplwf.sys
*** WARNING: Unable to verify timestamp for pacer.sys
*** WARNING: Unable to verify timestamp for netbios.sys
*** WARNING: Unable to verify timestamp for wanarp.sys
*** WARNING: Unable to verify timestamp for termdd.sys
*** WARNING: Unable to verify timestamp for rdbss.sys
*** WARNING: Unable to verify timestamp for nsiproxy.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** WARNING: Unable to verify timestamp for discache.sys
*** WARNING: Unable to verify timestamp for ks.sys
*** WARNING: Unable to verify timestamp for rspndr.sys
*** WARNING: Unable to verify timestamp for kbdclass.sys
*** WARNING: Unable to verify timestamp for mouclass.sys
*** WARNING: Unable to verify timestamp for umbus.sys
*** WARNING: Unable to verify timestamp for csc.sys
*** WARNING: Unable to verify timestamp for dfsc.sys
*** WARNING: Unable to verify timestamp for blbdrive.sys
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*** WARNING: Unable to verify timestamp for tunnel.sys
*** WARNING: Unable to verify timestamp for intelppm.sys
*** WARNING: Unable to verify timestamp for ndiswan.sys
*** WARNING: Unable to verify timestamp for raspppoe.sys
*** WARNING: Unable to verify timestamp for raspptp.sys
*** WARNING: Unable to verify timestamp for rassstp.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** WARNING: Unable to verify timestamp for usbehci.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** WARNING: Unable to verify timestamp for HDAudBus.sys
*** WARNING: Unable to verify timestamp for CompositeBus.sys
*** WARNING: Unable to verify timestamp for ndistapi.sys
*** WARNING: Unable to verify timestamp for swenum.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for AgileVpn.sys
*** WARNING: Unable to verify timestamp for WudfPf.sys
*** WARNING: Unable to verify timestamp for usbhub.sys
*** WARNING: Unable to verify timestamp for NDProxy.SYS
*** WARNING: Unable to verify timestamp for portcls.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for cdfs.sys
*** WARNING: Unable to verify timestamp for hidusb.sys
*** WARNING: Unable to verify timestamp for HIDCLASS.SYS
*** WARNING: Unable to verify timestamp for HIDPARSE.SYS
*** WARNING: Unable to verify timestamp for kbdhid.sys
*** WARNING: Unable to verify timestamp for crashdmp.sys
*** WARNING: Unable to verify timestamp for dump_dumpata.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_dumpata.sys
*** WARNING: Unable to verify timestamp for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** WARNING: Unable to verify timestamp for dump_dumpfve.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_dumpfve.sys
*** WARNING: Unable to verify timestamp for mouhid.sys
*** WARNING: Unable to verify timestamp for monitor.sys
*** WARNING: Unable to verify timestamp for luafv.sys
*** WARNING: Unable to verify timestamp for lltdio.sys
*** WARNING: Unable to verify timestamp for ksthunk.sys
*** ERROR: Module load completed but symbols could not be loaded for ksthunk.sys
*** WARNING: Unable to verify timestamp for Dxapi.sys
*** WARNING: Unable to verify timestamp for USBD.SYS
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
*** WARNING: Unable to verify timestamp for mrxsmb10.sys
*** WARNING: Unable to verify timestamp for mrxsmb20.sys
*** WARNING: Unable to verify timestamp for HTTP.sys
*** WARNING: Unable to verify timestamp for bowser.sys
*** WARNING: Unable to verify timestamp for mpsdrv.sys
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** WARNING: Unable to verify timestamp for srv2.sys
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for srvnet.sys
*** WARNING: Unable to verify timestamp for tcpipreg.sys
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
*** WARNING: Unable to verify timestamp for asyncmac.sys
*** WARNING: Unable to verify timestamp for srv.sys
*** WARNING: Unable to verify timestamp for rdpbus.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for nvBridge.kmd
*** ERROR: Module load completed but symbols could not be loaded for nvBridge.kmd
*** WARNING: Unable to verify timestamp for m4cxvst64.sys
*** ERROR: Module load completed but symbols could not be loaded for m4cxvst64.sys
*** WARNING: Unable to verify timestamp for 1394ohci.sys
*** WARNING: Unable to verify timestamp for rasl2tp.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** WARNING: Unable to verify timestamp for cdd.dll
Couldn't resolve error at 'ymfix'


Thanks
Jon

 

Did you install the correct symbol pack for your version of Win7 (either 32bit or 64bit)?
Have you run extended RAM diagnostics or HD diagnostics?
From what I can tell (and I'm far from a debug expert) the error is caused by ntoskrnl.exe. These types of errors are commonly caused by bad RAM, faulty hard drives, and malware. Check out the MajorGeeks Guide To Malware Removal and follow the steps until you're sure you have no malware. Then run the diagnostic from your hard drive maker (available for free from their web site). Then run an extended memory diagnostic (I like this one; you can create a bootable CD or floppy, boot to it, press "T" for the extended tests, and run at least 3 passes). If all these come out 100% OK, and you install the symbol pack and still have problems, let us know, and we'll try some other stuff.... actually, let us know regardless of how the tests go, we (I) may come up with something in the meantime....

 

Yea I installed the correct symbols pack, 3 times actually. I had it working before but after the last re-image it no longer works.

as for Malware, I haven't had the comp running long enough to have it online, still using my old PC primarily. It has the problem right after clean install.

the MoBo just got replaced by intel under warrenty, both they and I thought it was the problem. I started with a used 300g hard drive and swapped it out for the new V-Raptor. I have run a short mem test with no errors but was thinking of running it again.

Thanks for the other suggestions I will give them all a try.

Jon

 

ok so I ran the memory diag. tool.

on the extended test I got an error on both the MATS+ and the Stride 6 test's

adress 235c7bb4 expected ffffffff actual fffdffff

same address expected and actual on all errors. it errored the MATS+ test 5 times out of 5 passes, and the Stride 6 test 3 out of 4 passes (I didn't let it finish the 5th pass)

Does this mean I have a bad RAM stick? I put in for an RMA as its new RAM with warranty on it.

I have not ran a HD test yet, but I have replaced the HD with a new one due to this error and have still been getting the error. Its possible I got a second bad HD but unlikely.

I am going to download the drive diag. tool anyway and run it just to be on the safe side at this point.

Thanks
Jon

 

Based on dlb's diagnosis of your issue I believe you have found the problem and solution. The RAM replacement should solve the problem.

 

Yup - you have bad RAM. If you have more than one memory stick, you'll need to run the test on each stick individually to find out which stick is bad. When you find the bad stick, pull it and leave it out until you can get your hands on a good replacement. If the replacement stick is not brand new, it may not be a bad idea to install it with your other memory sticks and run the diagnostic just to make sure that all sticks are 'playing' well together....