BSOD Screen freezes with red/blue/yellow horizontal lines then BSOD

alw · 14 Jun 2014

This normally happens when I first start using the computer for the day. Sometimes when it happens there is a sound to it when it freezes but not always. Once the computer is going good for around 15-20mins then it no longer happens until the next reboot.

derekimo · 14 Jun 2014

Hi There,

Your video driver seems to be the problem,

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8800424f152, fffff880021b69e8, fffff880021b6240}

Probably caused by : atipmdag.sys ( atipmdag+39a152 )

Followup: MachineOwner

It is pretty old,

Code:

Loaded symbol image file: atipmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atipmdag.sys
    Image name: atipmdag.sys
    Timestamp:        Mon Mar 29 05:26:02 2010 (4BB09C5A)
    CheckSum:         0062931D
    ImageSize:        0066F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There doesn't seem to be an update from Gateway either.

Let's try uninstalling that driver and let windows install a WHQL driver,

How-To Uninstall AMD Catalyst Drivers From A Windows Based System

After uninstalling from programs and features,

1. Go to Device Manager and expand Display Adapters.

2. Right click on your adapter and choose properties.

3. Select the Driver tab and choose uninstall.

4. When finished, reboot the computer and let Windows install the available WHQL driver.

koolkat77 · 14 Jun 2014

Information

Please follow Derekimo's instructions first.

Welcome to the forum alw,

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

NTIDrvr.sys Wed Mar 25 09:09:39 2009 (49C9A073)
NTI CD-ROM Filter Driver by NewTech Infosystems (likely a part of Acer Empowering Technology)
Driver Reference Table - NTIDrvr.sys

UBHelper.sys Mon Apr 27 14:48:19 2009 (49F57153)
NTI CD &DVD-Maker or NTI Backup NOW! or NTI CD-Maker by NewTech Infosystems (usually in Acer Empowering Technology)
Driver Reference Table - UBHelper.sys

atikmpag.sys Mon Mar 29 17:46:26 2010 (4BB09312)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
Driver Reference Table - atikmpag.sys

atipmdag.sys Mon Mar 29 18:26:02 2010 (4BB09C5A)
ATI Video
Driver Reference Table - atipmdag.sys

athrx.sys Fri May 7 06:00:58 2010 (4BE3583A)
Atheros network adapter driver
Driver Reference Table - athrx.sys

k57nd60a.sys Sat May 15 18:51:06 2010 (4BEE98BA)
Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
Driver Reference Table - k57nd60a.sys

RTKVHD64.sys Tue Jun 22 15:27:26 2010 (4C2081FE)
Realtek High Definition Audio Function Driver
Driver Reference Table - RTKVHD64.sys

Uninstall Norton, it contributes to BSOD's.

Recommended antivirus software for Windows 7 based on stability compared to others:-

Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Reduce items at start-up:

How to Change, Add, or Remove Startup Programs in Windows 7

Perform a clean boot:

How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

How to Repair Windows 7 System Files with System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

How to Run Disk Check in Windows 7

Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test:

How to Use SeaTools for DOS and Windows Disk Check Utility

Check for heating issues using Speccy or HWmonitor

Upload a screen shot:

Screenshots and Files - Upload and Post in Seven Forums

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Jun 15 05:24:12.422 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:39.858
BugCheck 1000007E, {ffffffffc0000005, fffff8800424f152, fffff880021b69e8, fffff880021b6240}
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : atipmdag.sys ( atipmdag+39a152 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sat Jun 14 10:06:06.581 2014 (UTC + 6:00)
System Uptime: 0 days 0:21:29.017
BugCheck 1000007E, {ffffffffc0000005, fffff88004ba1152, fffff880021b99e8, fffff880021b9240}
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : atipmdag.sys ( atipmdag+39a152 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun 13 09:42:04.122 2014 (UTC + 6:00)
System Uptime: 0 days 0:27:23.558
BugCheck 3B, {c0000005, fffff80002fae127, fffff88008579df0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+517 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun 13 09:12:32.162 2014 (UTC + 6:00)
System Uptime: 0 days 0:03:44.614
BugCheck 50, {ffffffffd00b48bd, 1, fffff88004bff0bd, 2}
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : atipmdag.sys ( atipmdag+39a0bd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun  6 09:54:13.741 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:06.177
BugCheck D1, {ff, 2, 0, fffff880018a6058}
Probably caused by : hardware ( rdyboost!SmdIoTreeIoInit+21c )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun  6 09:29:55.576 2014 (UTC + 6:00)
System Uptime: 0 days 0:13:59.012
BugCheck 3B, {c000001d, fffff80002eb8e04, fffff88008262140, 0}
Probably caused by : hardware ( nt!NtWaitForWorkViaWorkerFactory+283 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Jun  2 05:45:04.956 2014 (UTC + 6:00)
System Uptime: 0 days 0:09:42.392
BugCheck D1, {40, 2, 0, fffff88001666036}
Probably caused by : tcpip.sys ( tcpip!TcpSegmentTcbSend+166 )
BUGCHECK_STR:  0xD1
PROCESS_NAME: NOT FOUND
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``