Windows 7: BSoD/Vertical Gray Line crash

bsimps3 · 17 Jan 2010

**Minidump attatched

Here's my system:
Mobo: Asus M4A78 Plus (latest bios version 1214, also latest chipset update)
Processor: AMD Phenom II X2 550 BE (i planned on OC'ing, but have not yet because of the crashes)
Overclocking: Not yet because the system is already unstable.
Vid Card: SAPPHIRE 100283L Radeon HD 5770 (Juniper XT) 1GB 128-bit GDDR5 PCI Express 2.0 x16
RAM: G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel
PSU: Thermaltake toughpower W0103RU 600W ATX12V / EPS12V
HDD: Western Digital Caviar Black WD5001AALS 500GB 7200 RPM SATA 3.0Gb/s 3.5"
OS: Windows 7 64-bit
I've got a 3rd party Zalman CNPS10X Extreme cpu cooler on the phenom II. (which I have already taken off, removed the paste, and reapplied much more carefully).
I've got the latest of all drivers/software (all Win 7 64 bit compatible). I have completely reseated every component.
Problem: Annoying gray vertical line/restart (various colored vertical lines suddenly appear and then the system restarts) OR BSoD which can be counted on to occur VERY often. The gray vertical line issue has been widely reported by other ATI 5XXX owners. I ruled out this problem by first trying all of the proposed tweaks in that thread, and finally by replacing my Radeon by an old nVidia... the crash persists but manifests itself as only a BSoD and not vertical line crash (I assume the difference here is just the same crash but different expressions of it because of the vid card switch).
Testing:
*Memtest86+ v4.00 ran overnight (12hrs) with 0 errors.
*Prime95 crashes for small FFT's, in place large FFT's, and Blend. At first it gave me the Fatal Error: rounding was 0.5, expected less than 0.4. I manually set the ram to 400 frequency and 5-5-5-15 with 2.0 volts (the specs recommended). The rounding error goes away but the system still crashes (either lines or BSoD) before 15 minutes pass.
*Since Prime95 crashes quickly, it isn't surprising that all games i've tried also crash.
*All temperatures are normal: GPU never above 65C, CPU never above 39C, mobo never above ~33C.

zigzag3143 · 17 Jan 2010

Quote: Originally Posted by bsimps3

**Minidump attatched

Here's my system:
Mobo: Asus M4A78 Plus (latest bios version 1214, also latest chipset update)
Processor: AMD Phenom II X2 550 BE (i planned on OC'ing, but have not yet because of the crashes)
Overclocking: Not yet because the system is already unstable.
Vid Card: SAPPHIRE 100283L Radeon HD 5770 (Juniper XT) 1GB 128-bit GDDR5 PCI Express 2.0 x16
RAM: G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel
PSU: Thermaltake toughpower W0103RU 600W ATX12V / EPS12V
HDD: Western Digital Caviar Black WD5001AALS 500GB 7200 RPM SATA 3.0Gb/s 3.5"
OS: Windows 7 64-bit
I've got a 3rd party Zalman CNPS10X Extreme cpu cooler on the phenom II. (which I have already taken off, removed the paste, and reapplied much more carefully).
I've got the latest of all drivers/software (all Win 7 64 bit compatible). I have completely reseated every component.
Problem: Annoying gray vertical line/restart (various colored vertical lines suddenly appear and then the system restarts) OR BSoD which can be counted on to occur VERY often. The gray vertical line issue has been widely reported by other ATI 5XXX owners. I ruled out this problem by first trying all of the proposed tweaks in that thread, and finally by replacing my Radeon by an old nVidia... the crash persists but manifests itself as only a BSoD and not vertical line crash (I assume the difference here is just the same crash but different expressions of it because of the vid card switch).
Testing:
*Memtest86+ v4.00 ran overnight (12hrs) with 0 errors.
*Prime95 crashes for small FFT's, in place large FFT's, and Blend. At first it gave me the Fatal Error: rounding was 0.5, expected less than 0.4. I manually set the ram to 400 frequency and 5-5-5-15 with 2.0 volts (the specs recommended). The rounding error goes away but the system still crashes (either lines or BSoD) before 15 minutes pass.
*Since Prime95 crashes quickly, it isn't surprising that all games i've tried also crash.
*All temperatures are normal: GPU never above 65C, CPU never above 39C, mobo never above ~33C.

Hi and welcome

Bunch of BSOD's you have here. they are virtaully identical. they all ppoint to the same thing. This type of crash can be caused by the following.

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

Now since you have rum memtestx86 is it passed, we may have to start looking at the other vaiables.

How much ram do you have?

I would just try prime 95 with only one ram stick it.

you could also run a system file check
type cmd in search>right click and run as admin>sfc /scannow.

the next step is to run driver verifier.
Make sure you have a current backup and a win 7 dvd in case you cant get back into the system.

Code:

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press  Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and  click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click  "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.  Continue to use your system normally, and if you know what causes the  crash, do that repeatedly. The objective here is to get the system to  crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier  by going back in and selecting "Delete existing settings" on the first  page, then locate and zip up the memory dump file and upload it with  your next post.

If you can't get into Windows because it crashes too soon, try it in  Safe Mode.
If you can't get into Safe Mode, try using System Restore from your  installation DVD to set the system back to the previous restore point  that you created.
If that doesn't work, post back and we'll have to see about fixing the  registry entry off-line.

More info on this at this link:  http://support.microsoft.com/?kbid=244617&
bsods

Code:

011310-22479-01.dmp    1/13/2010 8:48:08 PM        0x00000116    fffffa80`0594f010    fffff880`09aa469c    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\011310-22479-01.dmp    2    15    7600    
011310-15225-01.dmp    1/13/2010 11:45:28 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c58798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-15225-01.dmp    2    15    7600    
011310-19812-01.dmp    1/13/2010 10:31:14 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c8f798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-19812-01.dmp    2    15    7600    
011310-20451-01.dmp    1/13/2010 7:33:17 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c86798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-20451-01.dmp    2    15    7600    
011310-20576-01.dmp    1/13/2010 10:33:25 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c8f798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-20576-01.dmp    2    15    7600    
011310-25646-01.dmp    1/13/2010 9:33:58 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c40798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-25646-01.dmp    2    15    7600    
011310-26348-01.dmp    1/13/2010 9:36:15 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c56798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-26348-01.dmp    2    15    7600    
011310-26488-01.dmp    1/13/2010 7:26:51 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c49798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-26488-01.dmp    2    15    7600    
011310-26722-01.dmp    1/13/2010 9:03:07 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c9a798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-26722-01.dmp    2    15    7600    
011310-26816-01.dmp    1/13/2010 8:39:09 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c4c798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-26816-01.dmp    2    15    7600    
011310-27019-01.dmp    1/13/2010 9:17:42 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c4e798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011310-27019-01.dmp    2    15    7600    
011410-15787-01.dmp    1/14/2010 3:09:53 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c57798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-15787-01.dmp    2    15    7600    
011410-15927-01.dmp    1/14/2010 2:56:04 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c95798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-15927-01.dmp    2    15    7600    
011410-16021-01.dmp    1/14/2010 3:15:51 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c3b798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-16021-01.dmp    2    15    7600    
011410-16083-01.dmp    1/14/2010 2:50:02 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c42798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-16083-01.dmp    2    15    7600    
011410-16941-01.dmp    1/14/2010 6:48:06 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c54798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-16941-01.dmp    2    15    7600    
011410-16972-01.dmp    1/14/2010 12:53:29 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02ca1798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-16972-01.dmp    2    15    7600    
011410-17284-01.dmp    1/14/2010 6:59:21 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c87798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-17284-01.dmp    2    15    7600    
011410-18220-01.dmp    1/14/2010 7:47:39 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c86798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-18220-01.dmp    2    15    7600    
011410-19500-01.dmp    1/14/2010 12:55:39 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c97798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-19500-01.dmp    2    15    7600    
011410-20170-01.dmp    1/14/2010 10:31:47 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c3c798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-20170-01.dmp    2    15    7600    
011410-20326-01.dmp    1/14/2010 12:43:38 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c8f798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011410-20326-01.dmp    2    15    7600    
011510-15085-01.dmp    1/15/2010 7:16:54 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e43798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-15085-01.dmp    2    15    7600    
011510-15709-01.dmp    1/15/2010 11:59:34 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e4a798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-15709-01.dmp    2    15    7600    
011510-16052-01.dmp    1/15/2010 3:46:59 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e4c798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-16052-01.dmp    2    15    7600    
011510-16208-01.dmp    1/15/2010 9:59:44 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e57798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-16208-01.dmp    2    15    7600    
011510-16926-01.dmp    1/15/2010 4:23:24 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e9d798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-16926-01.dmp    2    15    7600    
011510-17440-01.dmp    1/15/2010 2:41:01 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02c4e798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-17440-01.dmp    2    15    7600    
011510-17706-01.dmp    1/15/2010 7:00:56 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e87798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-17706-01.dmp    2    15    7600    
011510-20716-01.dmp    1/15/2010 3:29:15 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e83798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-20716-01.dmp    2    15    7600    
011510-21840-01.dmp    1/15/2010 3:23:16 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e4f798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-21840-01.dmp    2    15    7600    
011510-28189-01.dmp    1/15/2010 4:05:41 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e49798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011510-28189-01.dmp    2    15    7600    
011610-16239-01.dmp    1/16/2010 10:57:42 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e87798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011610-16239-01.dmp    2    15    7600    
011610-16255-01.dmp    1/16/2010 10:21:53 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e96798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011610-16255-01.dmp    2    15    7600    
011610-18501-01.dmp    1/16/2010 11:09:33 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e52798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011610-18501-01.dmp    2    15    7600    
011610-24991-01.dmp    1/16/2010 11:16:17 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02ea0798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011610-24991-01.dmp    2    15    7600    
011710-15397-01.dmp    1/17/2010 3:43:57 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02edd3f0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-15397-01.dmp    2    15    7600    
011710-15709-01.dmp    1/17/2010 10:41:33 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e83798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-15709-01.dmp    2    15    7600    
011710-15724-01.dmp    1/17/2010 3:49:52 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e789df    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-15724-01.dmp    2    15    7600    
011710-16114-01.dmp    1/17/2010 10:37:48 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e4d798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-16114-01.dmp    2    15    7600    
011710-16426-01.dmp    1/17/2010 3:25:58 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e973f0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-16426-01.dmp    2    15    7600    
011710-16458-01.dmp    1/17/2010 4:22:31 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e8b3f0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-16458-01.dmp    2    15    7600    
011710-17082-01.dmp    1/17/2010 4:25:54 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02eda9df    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-17082-01.dmp    2    15    7600    
011710-17269-01.dmp    1/17/2010 1:24:38 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02ea1798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-17269-01.dmp    2    15    7600    
011710-17487-01.dmp    1/17/2010 1:19:05 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e99798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-17487-01.dmp    2    15    7600    
011710-17752-01.dmp    1/17/2010 1:42:58 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e59798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-17752-01.dmp    2    15    7600    
011710-17924-01.dmp    1/17/2010 3:37:36 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02ed89df    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-17924-01.dmp    2    15    7600    
011710-18033-01.dmp    1/17/2010 12:26:04 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e9f798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-18033-01.dmp    2    15    7600    
011710-18673-01.dmp    1/17/2010 3:31:37 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02ed69df    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-18673-01.dmp    2    15    7600    
011710-21715-01.dmp    1/17/2010 10:47:49 AM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02e59798    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011710-21715-01.dmp    2    15    7600

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidump\011310-25646-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e50
Debug session time: Wed Jan 13 22:32:01.091 2010 (GMT-5)
System Uptime: 0 days 0:05:53.855
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002c40798}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002c40798

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c77469 to fffff80002c77f00

STACK_TEXT:  
fffff880`009ecc68 fffff800`02c77469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009ecc70 fffff800`02c75932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ecdb0 fffff800`02c40798 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`08074c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02c75932 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

bsimps3 · 17 Jan 2010

Quote:

How much ram do you have?

4GB 2 sticks of 2GB

Quote:

I would just try prime 95 with only one ram stick it.

I've done this with each stick in each slot on the motherboard (1 stick in first slot... crash, same stick in 2nd slot... crash, etc... then same thing with other stick).

I've also manually set the timings and voltage to the memory in BIOS. I've then tried relaxing the timings, still crashes. All timings set to AUTO, still crashes.

Quote:

you could also run a system file check
type cmd in search>right click and run as admin>sfc /scannow.

Done: Windows Resource Protection did not find any integrity violations.
I take that to mean it didn't find anything wrong.

Quote:

the next step is to run driver verifier.

Done done and done.

So i followed all the directions, immediately after setting up verifier I rebooted... but before windows loaded a BSOD occurred.

It then restarted and prompted me if I wanted to run startup repair or start windows normally, I chose start windows normally. It bsod'ed again, so next I chose startup repair. Startup repair ran and successfully did a system restore (in the advanced details somewhere I read that a recent driver installation/update had caused the problem... i take that to mean verifier did its job). Windows then started correctly and I am attaching the minidump.

zigzag3143 · 17 Jan 2010

Quote: Originally Posted by bsimps3

Quote:

How much ram do you have?

4GB 2 sticks of 2GB

Quote:

I would just try prime 95 with only one ram stick it.

I've done this with each stick in each slot on the motherboard (1 stick in first slot... crash, same stick in 2nd slot... crash, etc... then same thing with other stick).

I've also manually set the timings and voltage to the memory in BIOS. I've then tried relaxing the timings, still crashes. All timings set to AUTO, still crashes.

Quote:

you could also run a system file check
type cmd in search>right click and run as admin>sfc /scannow.

Done: Windows Resource Protection did not find any integrity violations.
I take that to mean it didn't find anything wrong.

Quote:

the next step is to run driver verifier.

Done done and done.

So i followed all the directions, immediately after setting up verifier I rebooted... but before windows loaded a BSOD occurred.

It then restarted and prompted me if I wanted to run startup repair or start windows normally, I chose start windows normally. It bsod'ed again, so next I chose startup repair. Startup repair ran and successfully did a system restore (in the advanced details somewhere I read that a recent driver installation/update had caused the problem... i take that to mean verifier did its job). Windows then started correctly and I am attaching the minidump.

Well that is a bit better. Your zone alarm caused verifier to puke and die. I was a big zone alarm fan until win 7. had similar problems

If I were you just to test I would uninstall ZAP and see if the problems resolve. You can always re-install or change to a different firewall. the specific file that triggered it is vsdatant.sys. you might want to google that. you will see the problems and its correct removal.

Let us know the results

Ken J+

[code]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\011710-18174-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Sun Jan 17 19:42:25.421 2010 (GMT-5)
System Uptime: 0 days 0:00:11.154
Loading Kernel Symbols
...............................................................
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {121, 2, fffff88002dba4b0, 0}

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

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000121, Waiting at DISPATCH_LEVEL, without a timeout.
Arg2: 0000000000000002, IRQL value.
Arg3: fffff88002dba4b0, Object to wait on.
Arg4: 0000000000000000, Timeout parameter.

Debugging Details:
------------------

BUGCHECK_STR: 0xc4_121

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800033043dc to fffff80002e7af00

STACK_TEXT:
fffff880`009a91d8 fffff800`033043dc : 00000000`000000c4 00000000`00000121 00000000`00000002 fffff880`02dba4b0 : nt!KeBugCheckEx
fffff880`009a91e0 fffff800`03317654 : fffff780`00000320 fffff880`000e0082 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009a9220 fffff880`02d6c9f2 : fffff880`02dba4b0 00000000`00000000 fffff880`02dba440 fffff880`02d97c2e : nt!VerifierKeWaitForSingleObject+0x94
fffff880`009a92a0 fffff880`02dba4b0 : 00000000`00000000 fffff880`02dba440 fffff880`02d97c2e 00000000`00000000 : vsdatant+0x199f2
fffff880`009a92a8 00000000`00000000 : fffff880`02dba440 fffff880`02d97c2e 00000000`00000000 fffffa80`004e004c : vsdatant+0x674b0

STACK_COMMAND: kb

FOLLOWUP_IP:
vsdatant+199f2
fffff880`02d6c9f2 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: vsdatant+199f2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\011710-18174-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Sun Jan 17 19:42:25.421 2010 (GMT-5)
System Uptime: 0 days 0:00:11.154
Loading Kernel Symbols
...............................................................
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {121, 2, fffff88002dba4b0, 0}

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

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000121, Waiting at DISPATCH_LEVEL, without a timeout.
Arg2: 0000000000000002, IRQL value.
Arg3: fffff88002dba4b0, Object to wait on.
Arg4: 0000000000000000, Timeout parameter.

Debugging Details:
------------------

BUGCHECK_STR: 0xc4_121

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800033043dc to fffff80002e7af00

STACK_TEXT:
fffff880`009a91d8 fffff800`033043dc : 00000000`000000c4 00000000`00000121 00000000`00000002 fffff880`02dba4b0 : nt!KeBugCheckEx
fffff880`009a91e0 fffff800`03317654 : fffff780`00000320 fffff880`000e0082 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009a9220 fffff880`02d6c9f2 : fffff880`02dba4b0 00000000`00000000 fffff880`02dba440 fffff880`02d97c2e : nt!VerifierKeWaitForSingleObject+0x94
fffff880`009a92a0 fffff880`02dba4b0 : 00000000`00000000 fffff880`02dba440 fffff880`02d97c2e 00000000`00000000 : vsdatant+0x199f2
fffff880`009a92a8 00000000`00000000 : fffff880`02dba440 fffff880`02d97c2e 00000000`00000000 fffffa80`004e004c : vsdatant+0x674b0

STACK_COMMAND: kb

FOLLOWUP_IP:
vsdatant+199f2
fffff880`02d6c9f2 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: vsdatant+199f2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME: vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b09cb48

FAILURE_BUCKET_ID: X64_0xc4_121_VRF_vsdatant+199f2

BUCKET_ID: X64_0xc4_121_VRF_vsdatant+199f2

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

DEBUG_FLR_IMAGE_TIMESTAMP: 4b09cb48

FAILURE_BUCKET_ID: X64_0xc4_121_VRF_vsdatant+199f2

BUCKET_ID: X64_0xc4_121_VRF_vsdatant+199f2

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

bsimps3 · 17 Jan 2010

So I started uninstalling zonealarm, and it required a shutdown. Windows starts the shutdown process and seems to get stuck at a screen that says "Windows is shutting down". It stayed there for ~10 minutes. Then all of a sudden that same crash i've been experiencing occurs. That sort of lead me to believe we might have found the issue. Windows restarted and I made sure that vsdatant.sys was not on my system anymore.

I'm running Prime95 and playing a game at the same time, each of which cause the crash separately. So far so good, but it's only been about 15 minutes.

I'll post again in a day or two after running Prime95 for much longer (or if it crashes i'll post again tonight). But even if this isn't the problem, thank you very much for your help and quick replies. I've spent over 3 weeks trying to figure this out.

zigzag3143 · 17 Jan 2010

Quote: Originally Posted by bsimps3

So I started uninstalling zonealarm, and it required a shutdown. Windows starts the shutdown process and seems to get stuck at a screen that says "Windows is shutting down". It stayed there for ~10 minutes. Then all of a sudden that same crash i've been experiencing occurs. That sort of lead me to believe we might have found the issue. Windows restarted and I made sure that vsdatant.sys was not on my system anymore.

I'm running Prime95 and playing a game at the same time, each of which cause the crash separately. So far so good, but it's only been about 15 minutes.

I'll post again in a day or two after running Prime95 for much longer (or if it crashes i'll post again tonight). But even if this isn't the problem, thank you very much for your help and quick replies. I've spent over 3 weeks trying to figure this out.

Hey I learned from this too. Thats why we do this. I happpened to remember several other ZAP problems even with their most current version. I stopped using it a year ago. I now run eset smart security (AV and firewall) works so well I forget its there.

bsimps3 · 18 Jan 2010

15 hour 22 minute Prime95 Blend torture test successful with no errors.

zigzag3143 · 18 Jan 2010

Quote: Originally Posted by bsimps3

15 hour 22 minute Prime95 Blend torture test successful with no errors.

So it was ZAP?

bsimps3 · 18 Jan 2010

I just had the basic free firewall... if that is ZAP, then yes.