new build, nothing but bsods..

carterfickling · 20 Sep 2010

Hi all I've used windows 7 since release and never had these problems. A new build here - from the ground up..the only thing old is the hdds and I doubt they could be giving me this kind of trouble (didn't have any bsods on the old machine).

Anyways, here's my files, I'm sure it's a driver issue - but I'm not smart enough to figure out what to do next..i don't mind reformatting, but you know..I just got the system the way I like it...

I appreciate the help - thanks!!

usasma · 20 Sep 2010

A bunch of different BSOD errors mentioned in the MSINFO32 file says that this is most likely a hardware problem. As one of them is a STOP 0x116, I'd first suspect the video card or it's drivers. Other possibilities are the CD-ROM drive/driver and the network device/driver

Try this free stress test to see what it does for the video:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

More info on the STOP 0x116 error here: BSOD Index
Some suggested troubleshooting techniques here: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Troubleshooting the other devices involves removing the drivers and replacing them. If that doesn't work, then remove the CD-ROM to see if that fixes that problem. For the network card, just purchase a spare card (it's always good to have one on hand). They're about $15 US at most major retailers.

Uninstall the ATI Catalyst Control Center as it has had some issues with Win7. I've never seen the ATI customer care thingie before, but I expect it would be OK to uninstall also.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://<a href="http://www.carrona.o... Reference</a> ).
Please pay particular attention to any dated 2008 or earlier:

Code:


havair.sys   Mon May 21 08:09:11 2007 - Hava IR Driver for eHome by Monsoon Multimedia - http://www.carrona.org/dvrref.html#havair.sys
NCREMOTEPCI.SYS Mon Sep 11 16:47:38 2006 - Technisat digital satellite driver - http://www.carrona.org/dvrref.html#NCREMOTEPCI.SYS

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 12:07:07.876 2010 (UTC - 4:00)
System Uptime: 0 days 2:34:46.000
Probably caused by : cdrom.sys ( cdrom!RequestSetupMcnRequest+88 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments c0000005 82720b50 8c2b7ae0 8c2b76c0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 09:31:31.930 2010 (UTC - 4:00)
System Uptime: 0 days 2:00:21.038
Probably caused by : win32k.sys ( win32k!PushW32ThreadLock <PERF> (win32k+0x2a6)+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  csrss.exe
Bugcheck code 1000008E
Arguments c0000005 813802a6 95fa4c7c 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 06:16:16.894 2010 (UTC - 4:00)
System Uptime: 0 days 11:06:39.628
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
*** WARNING: Unable to verify timestamp for amdsata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdsata.sys
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** WARNING: Unable to verify timestamp for AtiPcie.sys
*** ERROR: Module load completed but symbols could not be loaded for AtiPcie.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 AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys
*** WARNING: Unable to verify timestamp for RtHDMIV.sys
*** ERROR: Module load completed but symbols could not be loaded for RtHDMIV.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 RTKVHDA.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys
*** WARNING: Unable to verify timestamp for dump_amdsata.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_amdsata.sys
*** WARNING: Unable to verify timestamp for LHidFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
*** WARNING: Unable to verify timestamp for LMouFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LMouFilt.Sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** 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 gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
*** WARNING: Unable to verify timestamp for havair.sys
*** ERROR: Module load completed but symbols could not be loaded for havair.sys
*** WARNING: Unable to verify timestamp for MpNWMon.sys
*** ERROR: Module load completed but symbols could not be loaded for MpNWMon.sys
*** WARNING: Unable to verify timestamp for atinavrr.sys
*** ERROR: Module load completed but symbols could not be loaded for atinavrr.sys
*** WARNING: Unable to verify timestamp for NCREMOTEPCI.SYS
*** ERROR: Module load completed but symbols could not be loaded for NCREMOTEPCI.SYS
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
Bugcheck code 000000C2
Arguments 00000007 00001097 b3744d20 b3744d88
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Sep 17 20:56:09.020 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:06.690
Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+2f )
BUGCHECK_STR:  0x7f_d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 0000000d 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 12:23:03.519 2010 (UTC - 4:00)
System Uptime: 0 days 4:35:45.627
Probably caused by : ntkrpamp.exe ( nt!KiDeliverApc+e1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  taskhost.exe
Bugcheck code 0000000A
Arguments 00000000 00000002 00000001 820f0f89
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 21:10:27.601 2010 (UTC - 4:00)
System Uptime: 0 days 3:56:25.725
Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+15d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000 00000002 00000001 820afdaf
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 14:28:45.742 2010 (UTC - 4:00)
System Uptime: 1 days 7:58:34.476
Probably caused by : ntkrpamp.exe ( nt!RtlSidHashLookup+21 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  iMON.exe
Bugcheck code 1000008E
Arguments c0000005 82072531 9f11f7bc 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 06:29:16.289 2010 (UTC - 4:00)
System Uptime: 1 days 7:34:26.414
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments bbb1c008 92cdb6fc 00000000 0000000d
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Sep  4 07:38:08.051 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:55.721
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  iMONAUDnldMng.
Bugcheck code 00000050
Arguments 8d65cff0 00000000 8b6a183d 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

carterfickling · 22 Sep 2010

Ok - so I've removed CCC and it seems a little more stable. But still getting BSODs. Is iTunes 10 causing bsods? I was syncing my phone, and absolutely nothing else, and it crashed. I didn't have anything in the CD drive at the time, but whether or not a faulty driver just pooched everything, I dunno. For those two old drivers, how do I go about removing them? Just search in regedit and take em out? The Hava thing can go no problem, I'm not sure what the other driver is anyways.

now..all this being said...I ran memtest and it flagged one spot. I rebooted, re ran it, and nothing (left it on for 3+ hours) was going to remove one stick of ram and try it one at a time. Would this be causing the random bluescreens? Does windows report a different type of error when it's supposedly bad ram? If I found one spot one time, why would I not find it again?

Sorry guys - n00b here, and not sure how to proceed.
Thanks

usasma · 22 Sep 2010

If you're getting errors in MemTest, then that must be resolved before proceeding elsewhere.
It may be that the stick wasn't seated properly, or it can be a broken trace that breaks the connection as it heats or cools.

That being said, try this procedure (start with step 6): Memory Diagnostics

carterfickling · 23 Sep 2010

Ok - here's the dumbest question you'll get today.
Would bad ram cause these random errors? I've done two memtests over night and errors both times. I removed, reseated, ran it from cold and hot..and problems.

Is that why it's tough to pinpoint exactly what's wrong?

Sorry to ask what may be a really stupid question - in all my years, I've never had a stick of ram go bad, or honestly, never had an issue like this before!
Thanks

usasma · 23 Sep 2010

Yes, bad RAM can cause these errors - but so can bad slots for the RAM on the motherboard.
Have you run the diagnostic steps that I recommended earlier? That'll tell you if it's RAM or the mobo slots.

carterfickling · 24 Sep 2010

Running tests, I've changed to the other ram slots and you were totally right usasma, the slots were bad. Is there anyway to fix them, or do I just send back? I've ran memtest 3 or 4 times now on the other slots and not one red flag. What would you do?

usasma · 24 Sep 2010

AFAIK there's no way to easily fix them (soldering skills and parts that exceed the cost of a new motherboard will probably be required).

If the mobo's still under warranty, return it for replacement.