Random BSODs in clean install...

[Exothermia]

Hey all, I got Windows 7 x64 Pro last week, upgrading from XP Pro 32. I keep getting random BSOD crashes. I'm not overclocking, I've done thorough memory tests and came back fine, and the system ran stably without ever crashing in XP for a month before installing 7.

I've included some of the recent minidumps. Hopefully you can open them, I had a hell of a time getting the permissions set so even I could open them. The gist of them is that they are all coming from different places except for netio.sys which is represented in two dumps.

I'm running an AMD Phenom II x4 3.0ghz processor, 4 gigs of patriot ddr1600 ram, 500 western digital caviar hd. The system is only a month old, and like I said, ran fine in XP.

Any ideas would be greatly appreciated.

 

[torrentg]

Probably caused by i8042prt.sys

That is either your mouse, keyboard or port driver causing.

i8042prt.sys Windows process - What is it?

Update your Logitech devices if you have those. Visit Logitech.com

Also visit your motherboard manufacturer's site for any chipset driver updates or bios updates.

Use only usb mouse and keyboard to test if this is really cause, if you don't find drivers. No PS/2.

 

[usasma]

I'm wondering about the 102709-16114.dmp file because a cryptographic driver was involved (Cng.sys).

Otherwise, 3 of the 5 memory dumps seem to point at networking components. One in particular at Rt64win7.sys - your Realtek Ethernet driver. I would suggest downloading a fresh copy, uninstalling the current copy, and installing the fresh copy.

Also, this outdated driver could be causing issues, so I'd suggest updating it also (it's only present in the first and last dump files tho'): GVTDrv64.sys Tue Sep 05 03:10:02 2006 This is probably some sort of Gigabyte driver for your motherboard - but I can't find any more information about it.

Here's the summary of the BSOD's:

Debug session time: Sun Oct 25 20:50:15.595 2015 (GMT-4)
System Uptime: 0 days 0:07:08.312
BugCheck D1, {46, 8, 0, fffff88003eb2468}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Oct 26 20:49:40.918 2009 (GMT-4)
System Uptime: 0 days 11:21:17.635
BugCheck 1E, {ffffffffc0000005, fffff88002f885a0, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!FilterMatch+7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Oct 26 09:27:13.927 2009 (GMT-4)
System Uptime: 0 days 0:41:07.990
BugCheck 1E, {ffffffffc0000005, fffff880009aec50, 0, 0}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+11af7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  HandBrakeCLI.e
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Oct 27 09:31:59.283 2009 (GMT-4)
System Uptime: 0 days 0:02:40.000
BugCheck 1000007E, {ffffffffc0000005, fffff8000289603b, fffff88002fc3f08, fffff88002fc3760}
Probably caused by : cng.sys ( cng!GatherRandomKey+22c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Oct 27 16:29:05.674 2009 (GMT-4)
System Uptime: 0 days 2:40:38.001
BugCheck 1E, {ffffffffc0000005, fffff88002f885a0, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!FilterMatch+7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[Exothermia]

Okay, I updated my network adapter driver and am no longer using any ps/2 devices, and I got two more BSODs. One was while shutting down and the other while watching a movie in windows media player. I've included these two dumps. Any idea what the problem could be now?

I wasn't able to find a more recent version of the Gigabyte driver you mentioned anywhere.

 

[torrentg]

How many watts is your power supply rated?
Are you doing any type of overclocking at all?

Please fill in your system specs. It's important to know how much power your system is using. Or at least attempt to make an educated guess.

dxgmms1.sys is cause and that's why I suggest.

Another was ntfs.sys.

Run memtest to check your ram. A few hours should be fine.

 

[Exothermia]

My power supply is rated for 585 watts. I'm not doing any overclocking, and I've done the memory tests and came back with no problems.

 

[torrentg]

There is only 32 minutes between our posts? How did you possibly run memtest for a few hours? At least 5 hours necessary.

 

[Exothermia]

As I said in my original post, that I had already run memory diagnostics before I ever created this thread.

 

[ickymay]

As I said in my original post, that I had already run memory diagnostics before I ever created this thread.

could you fill out your system specs so we have them to refer to on every post you make, and a simple idea of your software environment