Windows 7 Forums


Reply
Thread Tools

BSODs persist after a clean OS install

 
 
MscTch MscTch is offline
New Member
Join Date: Jun 2012
Location: Hampton, Virginia USA
Posts: 8
Thanked: 0
 
      06-19-2012
Reinstalled the OS last week & I'm still experiencing numerous BSODs. MiniDump Files are attached. "RAMMon - SPD Info" also attached. CPU-Z screenshots also attached.

MemTest86+ Results:
1st Test Results: No Errors after 8 passes taking nearly 18 hours
SETTINGS: **668 MHz (DDR3-1337)** CAS 9-9-9-24

2nd Test Results: No Errors after 8 passes taking 17 1/2 hours
SETTINGS: **802 MHz (DDR3-1605)** CAS 9-9-9-24
Attached Thumbnails
BSODs persist after a clean OS install-mainboard.jpg   BSODs persist after a clean OS install-memory.jpg   BSODs persist after a clean OS install-spd-slot1.jpg   BSODs persist after a clean OS install-spd-slot-2.jpg   BSODs persist after a clean OS install-spd-slot-3.jpg  

BSODs persist after a clean OS install-spd-slot-4.jpg  
Attached Files
File Type: zip Minidump.zip (195.0 KB, 12 views)
File Type: zip RAMMon - SPD Info.zip (3.2 KB, 11 views)
 
Reply With Quote
 
 
 
 
Shintaro Shintaro is offline
Established Member
Shintaro's Avatar
Join Date: Mar 2012
Location: Sydney, Australia
Posts: 1,232
Thanked: 147
Send a message via MSN to Shintaro
 
      06-19-2012
Have you installed ALL the drivers for the motherboard?
http://www.asus.com/Motherboards/Int...Z68V/#download

If you used the CD that came with the motherboard they could be old. So it is best to use the ones from the internet.

Hope this helps.
 
Reply With Quote
 
 
 
 
MscTch MscTch is offline
New Member
Join Date: Jun 2012
Location: Hampton, Virginia USA
Posts: 8
Thanked: 0
 
      06-19-2012
The short answer is most assuredly yes. Checked and double checked laboriously. I've lived on that page...it feels...after this latest clean OS install. A long answer is as follows:

-I purchased the hardware & assembled my machine in late December 2011
-Full Retail version of Windows 7 Home Premium 64bit
-Multiple (at least 4) clean installations of the OS over the past 6 months, all BSODing
-Initial OS installations (at least 2 from Dec. to Feb.) were performed on a WD hdd...all had BSOD problems
-RAM: In January performed "stick by stick" & "slot by slot" testing with Memtest86+. No reported errors on Corsair Vengeance 16GB (4x4GB) DDR3 1600 CMZ16GX3M4A1600C9B
-SSD: This latest clean OS installation is the 2nd clean OS installation onto a Samsung 128GB SSD 830 Series purchased & installed in late February & updated to the latest FW update (CXM03B1Q) prior to any OS installations. Using the latest Samsung SSD Magician software & its OS optimization
-CPU: Intel i7-2600K Sandy Bridge 3.4GHz LGA 1155 95W Quad-Core cooled with Cooler Master Hyper 212 EVO
-Video Card: XFX DoubleD HD-687A-ZDFC Radeon 6870 1GB 256bit GDDR5 PCIe
-MB: Asus P8Z68-V PRO/GEN3 LGA 1155 SATA 6Gb/s USB 3.0 ATX w/ UEFI bios

Secondly, I have a 'method' whereby I've been able to increase my chances and/or rapidity of this intermittent but consistent BSOD I'm experiencing. Although I've experienced BSODs while doing all of these particular things in this combined method singly, I've seemingly had it happen in any and many other unremembered scenarios. In other words, I'm not necessarily convinced of any specific causation or any conclusion as a result of using this method to more quickly guarantee the eventual BSOD. It just works. I used this method to solve my curiosity as to whether I could induce a BSOD while also in SAFE MODE a few days ago. It was successful. I'm not sure if this fact is helpful or not.

All the programs or tasks comprising this are opened and then ran simultaneously. This "method" of inducing an eventual BSOD...sooner rather than later...is as follows:
1. Open Media Center and play a recorded show. (When attempted in Safe Mode, I was only able to open WMC but unable to playback an actual recorded show.)
2. Run a full scan of Microsoft Security Essentials
3. Run a full scan of Malwarebytes
4. Open 3 different browsers (Chrome, IE & FF) and have all 3 browsers simultaneously playing a lengthy YouTube video playlist.

Again, this is after yet another clean install of the OS. I most often get through full scans of MSE or Malwarebytes w/ no problem or detections just in case someone is trying to send me down the malware causation route. These are a compilation of tasks that where more notably underway in a singular form when previous BSODs occurred. These are however not the only singular or combined scenarios in which BSODs have happened over the past 6 months of numerous clean OS installations on both an HDD & an SSD.

Thirdly, more in regards to the Asus motherboard and Corsair RAM. In this latest clean installation of the OS (6/13/2012), I've updated the MB with the very latest bios and been sure that any other Asus available download for my MB is up-to-date via the MB's OS specific support page. I've also used the Intel Driver Update Utility to be sure that everything is current on that front also.

Having previously completed (back in January) both a full 16GB config test AND also literally every conceivable "stick by stick" & "slot by slot" & 'extended tests' testing possibility with no errors, I opted this time to only run the Memtest86+ in my full 16GB configuration since I seriously doubted to encounter any error detection anyway. Here are results of Memtest 86+ over the past 2 days for my Corsair Vengeance 16GB (4 x 4 GB) 240-pin DDR3 SDRAM DDR3 1600 (PC3 12800) CMZ16GX3M4A1600C9B:

1st Test Results: No Errors after 8 passes taking nearly 18 hours
SETTINGS: **668 MHz (DDR3-1337)** CAS 9-9-9-24

2nd Test Results: No Errors after 8 passes taking 17 1/2 hours
SETTINGS: **802 MHz (DDR3-1605)** CAS 9-9-9-24
 
Reply With Quote
 
Shintaro Shintaro is offline
Established Member
Shintaro's Avatar
Join Date: Mar 2012
Location: Sydney, Australia
Posts: 1,232
Thanked: 147
Send a message via MSN to Shintaro
 
      06-19-2012
So the latest points to the Video card.
Who is the manufacturer ?

I would suggest that you uninstall the video card driver -> reboot -> reinstall -> reboot.

Quote:
BUGCHECK_STR: 0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE: 23

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: ehshell.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000316534a to fffff800030df1c0

STACK_TEXT:
fffff880`0c2b6318 fffff800`0316534a : 00000000`000000c1 fffff980`1f4a0f90 fffff980`1f4a0d04 00000000`00b14070 : nt!KeBugCheckEx
fffff880`0c2b6320 fffff800`031ddfa3 : fffff6fb`7dbf1000 fffff880`0c2b6430 00000000`00000000 00000000`c0000001 : nt!MiCheckSpecialPoolSlop+0x9a
fffff880`0c2b6360 fffff800`0320993b : fffff800`03060000 00000000`5958504b 00000000`00007e10 00000000`00000000 : nt!MmFreeSpecialPool+0x1d3
fffff880`0c2b64a0 fffff880`05607388 : fffff980`037f4540 fffff880`040890d1 00000000`00000001 fffffa80`1141c000 : nt!ExDeferredFreePool+0xf33
fffff880`0c2b6550 fffff980`037f4540 : fffff880`040890d1 00000000`00000001 fffffa80`1141c000 fffff8a0`00000001 : atikmpag+0x7388
fffff880`0c2b6558 fffff880`040890d1 : 00000000`00000001 fffffa80`1141c000 fffff8a0`00000001 fffff8a0`0db589d0 : 0xfffff980`037f4540
fffff880`0c2b6560 fffff880`040bc204 : fffffa80`1141c000 fffff880`0c2b6600 00000000`00000000 00000000`00000001 : dxgkrnl!DXGADAPTER::AcquireDdiSync+0xc9
fffff880`0c2b65a0 fffff880`040c02c1 : fffff8a0`0db589d0 00000000`00000000 00000000`00000000 fffff8a0`0a3e5000 : dxgkrnl!DXGADAPTERDdiDestroyAllocation+0x50
fffff880`0c2b65d0 fffff880`040bf65f : fffff8a0`0a3e5000 00000000`00000000 fffff8a0`00000000 fffff880`00000799 : dxgkrnl!DXGDEVICEDestroyAllocations+0x83d
fffff880`0c2b66c0 fffff880`040bf8e1 : 00000000`00000010 fffff8a0`0a3e5000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0c2b6710 fffff880`040c379c : fffff8a0`138ba800 fffff880`0c2b6b60 fffffa80`1141c000 fffff880`0408a3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0c2b6760 fffff880`040c5e57 : fffff8a0`0a3e5000 fffff880`0c2b6870 00000000`00000001 00000000`e0a91701 : dxgkrnl!DXGDEVICEDestroyAllocation+0x448
fffff880`0c2b67f0 fffff960`001ff82e : 00000000`00000000 fffffa80`0d572060 00000000`00000020 00000000`40002180 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0c2b6ab0 fffff800`030de453 : fffffa80`0d572060 fffff880`0c2b6b60 00000000`00000000 fffffa80`12b6cd50 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0c2b6ae0 000007fe`ff924a4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`2899f2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff924a4a


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmpag+7388
fffff880`05607388 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: atikmpag+7388

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e4294

FAILURE_BUCKET_ID: X64_0xC1_23_VRF_atikmpag+7388

BUCKET_ID: X64_0xC1_23_VRF_atikmpag+7388
Also have you been to Intels site:
http://downloadcenter.intel.com/Default.aspx

Let us know how you go.

Hope this helps.

Last edited by Shintaro; 06-19-2012 at 08:34 PM..
 
Reply With Quote
 
MscTch MscTch is offline
New Member
Join Date: Jun 2012
Location: Hampton, Virginia USA
Posts: 8
Thanked: 0
 
      06-19-2012
yes, on the Intel site as previously mentioned I used the Intel Driver Update Utility to make sure all their items were u-to-date. Additionally when updating the BIOS I was careful to note and install an Intel driver in the proper order after the recent BIOS update...which also didn't improve my BSOD situation.

I'll try to reinstall the video drivers after uninstalling them but I'm not quite sure how I should handle that this time. First of all, I'll use Driver Sweeper v3.2 to uninstall it, but it's the re-installation that has me baffled since I was careful how I did it on the last 2 clean installs. When I reboot Windows is going to install its version of the ATI/AMD Radeon 6870 driver for my video card (built by XFX.) I always then go to the AMD support site and both manually find my OS specific driver and use their auto-detect utility to download the driver and ensure that they are both indeed the same and then install the version I downloaded. I then install that version to get full use of it's features. Although that is apparently the best practice, it isn't working out for me. If I only allow the update that Windows update provides, I lose a lot of customization of the CatalystControl Center. Although right now I'd gladly do without that additional functionality if I just had a stable system with the apparently lighter driver that Windows update pushes upon it after thoroughly & cleanly uninstalling my appropriate video driver. If what I'm supposed to do doesn't work then I guess I should defer to the less desirable practice. I'll do that again any how...uninstall, reboot, let windows install it, reboot and try to induce another BSOD. That's all I know to do that is remotely any different from my previous attempts. It seems as if I can usually induce a BSOD within an hour if I put the system to the task. Many thanks mate. I'll let you know how it goes Shintaro
 
Reply With Quote
 
Shintaro Shintaro is offline
Established Member
Shintaro's Avatar
Join Date: Mar 2012
Location: Sydney, Australia
Posts: 1,232
Thanked: 147
Send a message via MSN to Shintaro
 
      06-19-2012
I would suggest that you download the driver. And only install the driver not the other stuff.
Try not to let windows install the driver if you can. Just cancel it, if you can.
 
Reply With Quote
 
brkkab123 brkkab123 is offline
Established Member
brkkab123's Avatar
Join Date: May 2010
Location: Florida
Posts: 1,273
Thanked: 112
 
      06-19-2012
Try setting the RAM's tRC to 41 in your bios. In your CPU-z Memory tab screenshot tRC is blank in the CPU-z SPD tab, screenshot CPU-z says it should be 41 for your ram. Try that and see if bsod's go away. If they don't then rule out your drivers next. Also, what antivirus software are you using ? AVG is known to cause bsod's. Upload your
Quote:
Originally Posted by Shintaro View Post
I would suggest that you download the driver. And only install the driver not the other stuff.
Try not to let windows install the driver if you can. Just cancel it, if you can.

Last edited by brkkab123; 06-19-2012 at 10:08 PM..
 
Reply With Quote
 
MscTch MscTch is offline
New Member
Join Date: Jun 2012
Location: Hampton, Virginia USA
Posts: 8
Thanked: 0
 
      06-20-2012
@brkkab123 I'm using Microsoft Security Essential antivirus. I've spent this past week extensively looking thru RAM settings on on my BIOS. I saw many, many settings in every single sub-menu & any other possible setting and none that specifically addresses setting "tRC" to 41...many that look similar but nothing exactly by that name. I'm far from even remotely knowledgeable about those settings so I'm sure my not finding it or being able to make it show up via some other "non-auto" setting is probably my lack of knowledge.

@Shintaro I first uninstalled the driver via the "uninstall Programs" menu then rebooted. I then ran Driver Sweeper and uninstalled all remains of the AMD Catalyst Center & video drivers then again rebooted. Then again checked with Driver Sweeper and verified that there were no remains and then turned OFF the computer. I decided to chose another path because I've uninstalled the correct manufacturer's recommended driver numerous times cleanly and reinstalled it again and apparently to no differing results. I'm not up for being insane so as to expect a different result. I've done it correctly in the past and this is no different than what I haven't already done before.

So I thought this a good opportunity while the computer was off, to make use of why I purchased the particular Motherboard and Processor I bought and see if that would help my troubleshooting. I have onboard IGX (Intel 3000 HD) graphics. I plugged the DVI cable for the monitor into the appropriate DVI cable for the MB and physically removed my AMD (XFX) video card and then restarted the computer.

I again verified there was no remnants of AMD drivers on my computer and then began my tried and true method of expediting and inducing a BSOD. It indeed happened within approximately 45 minutes. Now I say that with one possible caveat that I'm not sure that matters or not...I still have Driver Verifier enabled for everything but Microsoft items...but I'm not sure if that is relevant or not. I've attached the new minidump files and it may be important to note the following things about those dumps. There was a BSOD that happened @ 6/19 9:30 PM GMT was while I was first uninstalling the AMD video card drivers. I was however subsequently successful at the uninstallation. The following BSOD on 6/19 @ 10:17 PM happened while using the onboard Intel Graphics. "WhoCrashed" is apparently pointing to the Intel RST drivers. Again, I'm not sure if having Driver Verifier in use is noteworthy in that regard. That brings me to my next question. Being that I'm not using a RAID setup, I don't believe I need to have the Intel RST installed. Can't I just go ahead and uninstall that and also eliminate that from this whole ongoing BSOD situation.
Attached Files
File Type: zip minidump.zip (247.5 KB, 16 views)
 
Reply With Quote
 
Shintaro Shintaro is offline
Established Member
Shintaro's Avatar
Join Date: Mar 2012
Location: Sydney, Australia
Posts: 1,232
Thanked: 147
Send a message via MSN to Shintaro
 
      06-20-2012
Mate,

Just a quick question, have you installed the latest motherboard BIOS?
 
Reply With Quote
 
Shintaro Shintaro is offline
Established Member
Shintaro's Avatar
Join Date: Mar 2012
Location: Sydney, Australia
Posts: 1,232
Thanked: 147
Send a message via MSN to Shintaro
 
      06-20-2012
Mate,

Could you give this a try:
http://support.amd.com/us/kbarticles...AGPHotfix.aspx
From that site:
Quote:
A conflict between Microsoft DirectX® and the AMD Radeon™ HD AGP series graphics cards.


Quote:
STACK_TEXT:
nt!KeBugCheckEx
dxgkrnl!TdrBugcheckOnTimeout+0xec
dxgkrnl!TdrIsRecoveryRequired+0x1a2
dxgmms1!VidSchiReportHwHang+0x40b
dxgmms1!VidSchiCheckHwProgress+0x71
dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
dxgmms1!VidSchiScheduleCommandToRun+0x1da
dxgmms1!VidSchiWorkerThread+0xba
nt!PspSystemThreadStartup+0x5a
nt!KxStartSystemThread+0x16
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BSODs even after clean install BulletGT90 Crashes, BSODs and Debugging 25 12-18-2012 01:31 AM
[SOLVED] After clean install mouse (driver?) has unwanted extra features jmk50 Customization 16 09-18-2012 02:27 PM
BSOD...After Clean Install Tothelight Crashes, BSODs and Debugging 5 09-12-2012 08:22 PM
[SOLVED] BSOD after clean install HairyScot Crashes, BSODs and Debugging 4 05-26-2012 02:01 AM
After Clean Install: Major Boot Errors... Hannes84 Windows 7 Support 4 04-08-2010 07:50 PM


All times are GMT +1. The time now is 08:13 PM.
W7Forums is an independent website and is not affiliated with Microsoft Corporation.