Random BSOD New build 0x800... event id 1001

[x BlueRobot]

The crash your looking for is a actual BSOD.

 

[kenh536]

The crash your looking for is a actual BSOD.

Okay I finally got an actual bsod after rebooting because of another screen freeze with the lines. I turned off driver verifier and here is the new report. What happened to cause those crashes with the lines?

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff8000394f51b, fffff88007aabe40, 0}

Probably caused by : ntkrnlmp.exe ( nt!ViZwCheckObjectAttributes+b )

Usual causes:  System service, Device driver, graphics driver, memory

Your graphics driver seem to likely to be contributing to the crashes, and may explain the white lines on the screen when running Driver Verifier:

0: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`05652000 fffff880`06168000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Wed Dec 19 20:38:55 2012[/COLOR] (50D225DF)
    CheckSum:         00AC6529
    ImageSize:        00B16000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update with the latest WHQL driver which is available to download from here - http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

 

[kenh536]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff8000394f51b, fffff88007aabe40, 0}

Probably caused by : ntkrnlmp.exe ( nt!ViZwCheckObjectAttributes+b )

Usual causes:  System service, Device driver, graphics driver, memory

Your graphics driver seem to likely to be contributing to the crashes, and may explain the white lines on the screen when running Driver Verifier:

0: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`05652000 fffff880`06168000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Wed Dec 19 20:38:55 2012[/COLOR] (50D225DF)
    CheckSum:         00AC6529
    ImageSize:        00B16000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update with the latest WHQL driver which is available to download from here - http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Okay I uninstalled via device manager, rebooted, ran driver sweeper, clicked on AMD Display and clicked clean, rebooted and ran the installer for the driver 13.5 beta, rebooted and it took effect.

I do have a few concerns/things worth noting though:
-When I ran driver sweeper, it showed nvidea drivers (chipset, display, and Physx) which I thought was weird as I have no Nvidea hardware
-I quickly checked driver sweeper after reboot and it still showed two drivers under AMD-Display. I didn't touch them, wasn't sure if they needed to be cleaned as well
-After the driver installer installed it said warnings occurred during installation, however it also said it was successful.

 

[x BlueRobot]

The other entries are just default, and could you post a screenshot of your Device Manager with the Display section expanded:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[kenh536]

Okay I am pretty sure I did something wrong as I got another BSOD. I included the screenshot and the SF tool file just in case.

 

[x BlueRobot]

There's only one entry for your graphics card which is normal and no warning triangles next to any of the drivers which is another good point.

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d899271816, b3b7465eeba3e76c, fffff800034cb3fc, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="red"]memory_corruption[/COLOR]

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

It's best to install the WHQL driver not the Beta driver for the graphics card.

-----------------------------------------------------

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[kenh536]

There's only one entry for your graphics card which is normal and no warning triangles next to any of the drivers which is another good point.

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d899271816, b3b7465eeba3e76c, fffff800034cb3fc, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="red"]memory_corruption[/COLOR]

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

It's best to install the WHQL driver not the Beta driver for the graphics card.

-----------------------------------------------------

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

I did all of the tests besides the SeaTools because I didn't have a blank disc. I don't know if the disc check found any errors because I left it and came back and it had recovered after a blue screen or something. Also here is the screenshot.

 

[x BlueRobot]

Here's a Windows version of Seagate Tools - SeaTools for Windows | Seagate

For the chkdsk results, you can check here and then upload the file - http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

The Crystal Disk Info screenshot seems to be fine, however, this only gives the S.M.A.R.T values, but is a positive sign so far.

Could you also upload the new BSOD?

 

[kenh536]

Here's a Windows version of Seagate Tools - SeaTools for Windows | Seagate

For the chkdsk results, you can check here and then upload the file - http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

The Crystal Disk Info screenshot seems to be fine, however, this only gives the S.M.A.R.T values, but is a positive sign so far.

Could you also upload the new BSOD?

Seagate Tools came back with no errors. I think I got the right file for the chkdsc but I might have done it wrong. Also I have got a blue screen 2 or more times since my last post. I have included the new BSOD files. Sorry for the late reply as well.

 

[x BlueRobot]

It was the right file, and couldn't find any problems with it.

[COLOR="Red"]BugCheck 7F[/COLOR], {8, 80050031, 406f8, fffff88001217529}

Probably caused by : [COLOR="red"]memory_corruption[/COLOR]

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

A trap which was excepted happened in the Kernel, a trap is a type of exception, a interrupt occurs to enable the operating system to perform some functions before returning to the previous process, a trap can be caused by an invalid memory address which seems to be happening in this case.

CHKIMG_EXTENSION: [COLOR="SeaGreen"]!chkimg -lo 50 -d !Ntfs[/COLOR]
    fffff8800121751c - Ntfs!NtfsCleanupIrpContext+287
	[ 83:a3 ]
[COLOR="Red"]1 error : !Ntfs[/COLOR] (fffff8800121751c)

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 10-15 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

There has been some cases, whereby errors have been found at 20 passes.

 

[kenh536]

It was the right file, and couldn't find any problems with it.

[COLOR="Red"]BugCheck 7F[/COLOR], {8, 80050031, 406f8, fffff88001217529}

Probably caused by : [COLOR="red"]memory_corruption[/COLOR]

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

A trap which was excepted happened in the Kernel, a trap is a type of exception, a interrupt occurs to enable the operating system to perform some functions before returning to the previous process, a trap can be caused by an invalid memory address which seems to be happening in this case.

CHKIMG_EXTENSION: [COLOR="SeaGreen"]!chkimg -lo 50 -d !Ntfs[/COLOR]
    fffff8800121751c - Ntfs!NtfsCleanupIrpContext+287
	[ 83:a3 ]
[COLOR="Red"]1 error : !Ntfs[/COLOR] (fffff8800121751c)

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 10-15 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

There has been some cases, whereby errors have been found at 20 passes.

Okay so I need to run MemTest again. I'm assuming that I run the test with both sticks installed and if I get an error then I start testing individual sticks. Last time I had both RAM sticks in. I guess this time I am going to let it run for about 24 hours, or until 20 passes completes, to be sure. Ill get back to you after I have done this.

 

[x BlueRobot]

Okay thanks, there does seem to quite a few clues pointing to bad RAM, or other memory issues.

 

[kenh536]

Okay thanks, there does seem to quite a few clues pointing to bad RAM, or other memory issues.

About 9 passes in. But I was thinking, since it is a memory problem and I was getting weird video errors, could it be a problem with the gddr5 memory on the graphics card?

 

[VistaKing]

Take a look at the link below . It has a video memory test like memtest

:ar: HOME PAGE OF MISHA CHERKES

 

[kenh536]

Take a look at the link below . It has a video memory test like memtest

:ar: HOME PAGE OF MISHA CHERKES

Ok thanks. Ill check that out once Memtest finishes.. going to take more than 24 hrs, 14 passes in.

 

[x BlueRobot]

Okay, and bad video memory can be a possibility with the memory_corruption, the RAM is either corrupted or the !ntfs image within the RAM is corrupted itself.

 

[kenh536]

Okay I ran memtest for 46 hours and it ran 24 passes with no errors. I started the Video memory test and it has ran 6 passes with no errors so far. I didn't configure any of the settings for the test because there wasn't any instructions that I saw but I figured it was like memtest just let it run itself.

I was reading some stuff online and I am pretty sure I messed up installing drivers (which might be what caused this). I thought I was supposed to install ALL of the motherboard drivers from Gigabytes' site and I downloaded every file listed for my mobo and installed them, instead of just going into device manager and getting the ones I needed... Is this a big problem and can I fix it?

 

[x BlueRobot]

Yes, it's possible you can fix this problem, personally I would backup all your personal files using http://www.sevenforums.com/tutorials/615-backup-user-system-files.html, and then perform a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html.

By doing this, we can make sure you have the exact drivers, and eliminate any possible software cause for the BSODs.

Remember to download your Ethernet driver before clean install.

 

[kenh536]

Yes, it's possible you can fix this problem, personally I would backup all your personal files using http://www.sevenforums.com/tutorials/615-backup-user-system-files.html, and then perform a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html.

By doing this, we can make sure you have the exact drivers, and eliminate any possible software cause for the BSODs.

Remember to download your Ethernet driver before clean install.

Okay I read a bit about a clean install and theres a couple things I don't fully understand. Do I need to do a backup if there is no files I need to save on my hard drive? Also will my product key work again for reactivation or will I need to call Microsoft? (its an OEM win7)