Constant freezing, BSOD driver has attempted to corrupt system

[Codswallop]

Hey everyone,

For ages, I've been having these issues of my laptop constantly freezing, crashing, programs not responding, etc. Well, I've finally decided to do something about it.

SPECS:
Device: HP Pavilion m6
Windows 7 x64
AMD A10-4600M Processor APU with Radeon 2.29GHz
RAM: 6GB
Available space on the C: drive: 330GB

The current problem: Windows will not start in normal mode. Upon entering the login screen, it will crash and enter a BDOS screen reading, "A device driver attempting to corrupt the system has been caught." I have been having problems with perpetual freezing for months now, but it has never gotten this bad before.
NOTE: Windows will run smoothly in safe mode, which is why I have narrowed the most probable cause to be a driver issue

Steps I have already taken:

-Ran CCleaner with no issues
-Defragged the disk with no issues
-Scanned for viruses with multiple antivirus programs (Vipre security, Malware bytes, and RogueKiller)
-Have gone into MSconfig and have disabled all startup programs and all startup services EXCEPT FOR MICROSOFT services
-I have attempted to do a system scan several times, but it would always get stuck at 64% of verification scan, even in safe mode
-I have checked the Event Viewer. The errors that appear at the time of the two most recent crashes are:
1. The DHCP Client service depends on the Ancillary Function Driver for Winsock service which failed to start because of the following error:
A device attached to the system is not functioning.
2. The DNS Client service depends on the NetIO Legacy TDI Support Driver service which failed to start because of the following error:
A device attached to the system is not functioning.
3. The following boot-start or system-start driver(s) failed to load:
AFD
DfsC
4. The following boot-start or system-start driver(s) failed to load:
discache
spld

-I have attempted to do a system restore. It made no difference to the situation.

I have attached the 3 most recent dump files. I cannot view them myself since I do not have the software and cannot download it due to being in safe mode


UPDATE: I have checked the device manager while in safe mode. There were no indicators . I'm not sure if that's because there are none or if it was because I was in safe mode
UPDATE 2: I have updated and repaired the ASUS network driver. No difference was made


Cheers

 

[essenbe]

I read the dump files you posted. They all gave the same cause

tcpipreg
start             end                 module name
fffff880`081e0000 fffff880`081f2000   tcpipreg   (pdb symbols)          c:\symcache\tcpipreg.pdb\2E2DF5F7FC39481BBAF303EBD91BB0721\tcpipreg.pdb
    Loaded symbol image file: tcpipreg.sys
    Mapped memory image file: c:\symcache\tcpipreg.sys\506C62BE12000\tcpipreg.sys
    Image path: \SystemRoot\System32\drivers\tcpipreg.sys
    Image name: tcpipreg.sys
    Timestamp:        Wed Oct 03 11:07:26 2012 (506C62BE)
    CheckSum:         00010902
    ImageSize:        00012000
    File version:     6.1.7601.17964
    Product version:  6.1.7601.17964
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     tcpipreg.sys
    OriginalFilename: tcpipreg.sys
    ProductVersion:   6.1.7601.17964
    FileVersion:      6.1.7601.17964 (win7sp1_gdr.121003-0333)
    FileDescription:  TCP/IP Registry Compatibility Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That is a Windows update driver - TCP/IP Registry Compatibility Driver

 

[Codswallop]

Wonderful, wonderful. Thank you for that. Any advice on how to fix it? I haven't really been able to find much on google other than "here! Come pay $150 to buy our registry cleaning software."

 

[Codswallop]

I read the dump files you posted. They all gave the same cause

tcpipreg
start             end                 module name
fffff880`081e0000 fffff880`081f2000   tcpipreg   (pdb symbols)          c:\symcache\tcpipreg.pdb\2E2DF5F7FC39481BBAF303EBD91BB0721\tcpipreg.pdb
    Loaded symbol image file: tcpipreg.sys
    Mapped memory image file: c:\symcache\tcpipreg.sys\506C62BE12000\tcpipreg.sys
    Image path: \SystemRoot\System32\drivers\tcpipreg.sys
    Image name: tcpipreg.sys
    Timestamp:        Wed Oct 03 11:07:26 2012 (506C62BE)
    CheckSum:         00010902
    ImageSize:        00012000
    File version:     6.1.7601.17964
    Product version:  6.1.7601.17964
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     tcpipreg.sys
    OriginalFilename: tcpipreg.sys
    ProductVersion:   6.1.7601.17964
    FileVersion:      6.1.7601.17964 (win7sp1_gdr.121003-0333)
    FileDescription:  TCP/IP Registry Compatibility Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That is a Windows update driver - TCP/IP Registry Compatibility Driver

Wonderful, wonderful. Thank you for that. Any advice on how to fix it? I haven't really been able to find much on google other than "here! Come pay $150 to buy our registry cleaning software."

 

[essenbe]

Please run http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and upload the results here.

It's a Windows Update driver.