Constant BSOD's on new system

pattitude87 · 06 Aug 2010

Hey guys,

I had a mate build me a new comp late last year and its been problems from day one.

Running Windows 7 professional 32bit. To begin with it would just randomly freeze to a light blue or gray screen which i would have to reset, normally within ten mins of running (even on login page), though normally if i had a fullscreen game running this would prevent it. Anything else (surfing the net, just working on word docs) and it would freeze up sooner or later.

Thought it might be a driver issue so i got driver genius and updated all of the drivers it suggested, since then it has stopped freezeing and started actually crashing and restarting itself (not sure if this is really an improvement or not). Really don't know much about this sort of thing so help on this would be appreciated.

I've attached the dump files and the system health report as per the thread instructions.

zigzag3143 · 07 Aug 2010

pattitude87 said:

Hey guys,

I had a mate build me a new comp late last year and its been problems from day one.

Running Windows 7 professional 32bit. To begin with it would just randomly freeze to a light blue or gray screen which i would have to reset, normally within ten mins of running (even on login page), though normally if i had a fullscreen game running this would prevent it. Anything else (surfing the net, just working on word docs) and it would freeze up sooner or later.

Thought it might be a driver issue so i got driver genius and updated all of the drivers it suggested, since then it has stopped freezeing and started actually crashing and restarting itself (not sure if this is really an improvement or not). Really don't know much about this sort of thing so help on this would be appreciated.

I've attached the dump files and the system health report as per the thread instructions.

There weren't any DMP files in it.

We really need the actual DMP file.

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

pattitude87 · 07 Aug 2010

Whoops sorry, here are the zipped dmp files...

ttran · 07 Aug 2010

Hi and welcome to SF!

Code:

 wg111v2  wg111v2.sys  Wed Dec 26 09:46:00 2007 (4771C068)

It was blamed in one of the DMP. It is your NETGEAR WG111v2 54Mbps Wireless USB 2.0 Adapter NT Driver.It's date from 2007 is way too old. I would suggest to update it now, that's critically important.
Answer

Another out of date driver:

Code:

 lirsgt   lirsgt.sys   Tue Jun 17 21:41:11 2008 (4857CD07)

It is part of a Copy Protection platform developed by Tages SA
TAGES, the AAA Copy Protection System

Code:

gdrv     gdrv.sys     Tue Dec 11 12:22:37 2007 (475E1E9D)
GIGABYTE Tools --may be Easytune?? Update it or uninstall it please

In looking through your drivers, I see that you have AVG anti virus installed. AVG is known to cause BSOD, on some systems. I suggest that you uninstall it while trouble shooting using the uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also >Info > Tool. I recommend that you install MSE and make sure Windows Firewall is turned on.

Also, 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.

BUGCHECK SUMMARY:

Code:

BugCheck 4E, {99, 8dc28, 0, 8dc30}

Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

Followup: MachineOwner
---------
BugCheck 1A, {1236, 88f08af0, 88f08b7c, 4d7bd}

Probably caused by : rdyboost.sys ( rdyboost!SMKM_STORE<SMD_TRAITS>::SmStReleaseRegion+1f )

Followup: MachineOwner
---------
BugCheck A, {da499304, 2, 1, 830d69e5}

Probably caused by : memory_corruption ( nt!MiRemoveLowestPriorityStandbyPage+163 )

Followup: MachineOwner
---------
BugCheck D1, {0, 2, 1, 8c09a748}

Unable to load image \SystemRoot\system32\DRIVERS\wg111v2.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wg111v2.sys
*** ERROR: Module load completed but symbols could not be loaded for wg111v2.sys
Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferListsComplete+b4 )

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

BugCheck 1A, {888a, 829f8008, c07e9491, 849edd7c}

Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+1c2 )

Followup: MachineOwner
---------
BugCheck 1000008E, {c0000005, 830b8897, a63e7a60, 0}

Probably caused by : ntkrpamp.exe ( nt!PspReturnQuota+25 )

Followup: MachineOwner
---------
BugCheck 1A, {41287, 0, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

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

Are you overclocking anything?

pattitude87 · 08 Aug 2010

Thanks for your reply, i'll do as you've suggested and let you know how it goes.