Solved BSOD with Qualcomm WLAN(?) - BCCode d1, 4a

[asura8]

Not sure what to put here that isn't included within the diagnostic files below. In a nutshell though, I've just built a new computer with Windows 7 64x Ultimate, Intel i5-4670K, and nVidia GTX 760 video card. Drives are a Samsung SSD 840 Pro and a WD Caviar Blue mechanical drive. Motherboard is an ASUS Z87-PRO.

I've updated all the drivers I can find (I think), and the computer still BSOD, even in safe mode. Sometimes it will be stable for upwards of 10 hours, but on a clean boot it will start giving BSOD again. I would appreciate if anybody can help me track down the specific driver which is the cause of this!

Samsung Magician seems to verify the SSD as fine, the Caviar Blue checks out by chkdsk, and both sticks of memory have passed multiple runs of the Windows 7 Memory test. I do not know if these are verifiable evidence as to these working or not; I seem to think that it is confined to a driver error, but I may be wrong.

Edit: Admittedly, I am concerned some of the problem, as silly as it may be, may boil down to the right choice of Wireless drivers for the ASUS Z87-PRO. They list four different ones which seem to have large overlap; if somebody could sort that out for me, I will bow before your superior knowledge. And also be incredibly grateful.

 

[YoYo155]

The bugchecks do point to your wireless network adapter:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Arguments:
Arg1: [COLOR=Red][U][B]0000000000000024[/B][/U][/COLOR], memory referenced
Arg2: 000000000000000[COLOR=Blue][U][B]2[/B][/U][/COLOR], IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800366a73e, address which referenced memory

• An attempt was made to access a pageable (or completely invalid) address at an
  interrupt request level (IRQL) that is too high. This is usually
  caused by drivers using improper addresses.

the Stack:

fffff800`00b9a000  fffff880`0366a73e [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x2c73e
fffff800`00b9a0f8  fffff880`0363faa0 [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x1aa0
fffff800`00b9a100  fffff880`0363f960 [COLOR=Red][B][U]athrx[/U][/B][/COLOR]+0x1960
fffff800`00b9a128  fffff880`03667f00 [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x29f00
fffff800`00b9a288  fffff880`0366a73e [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x2c73e
fffff800`00b9a2b8  fffff880`03647ced [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x9ced
fffff800`00b9a2f8  fffff880`0366b56c [COLOR=Red][B][U]athrx[/U][/B][/COLOR]+0x2d56c
fffff800`00b9a318  fffff880`036c21bf [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x841bf
fffff800`00b9a328  fffff880`036689fe [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x2a9fe
fffff800`00b9a358  fffff880`0366ee6d [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x30e6d
fffff800`00b9a3b8  fffff880`0376ef33 [COLOR=Red][B][U]athrx[/U][/B][/COLOR]+0x130f33
fffff800`00b9a3c8  fffff880`0376f63f [COLOR=Red][U][B]athrx[/B][/U][/COLOR]+0x13163f

In-order to receive more information about the driver
we use the lmvm command:

[COLOR=SeaGreen][U][B]lmvm [COLOR=Red]athrx[/COLOR][/B][/U][/COLOR]
start             end                 module name
fffff880`0363e000 fffff880`039d8000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        [COLOR=Red][U][B]Tue Apr 24 08:00:41 2012[/B][/U][/COLOR] (4F963379)

The driver is clearly outdated.

• Driver Reference Table - athrx.sys

Download the current version:

Name: [B]Atheros AR946x[/B]
[LEFT][COLOR=black]Version:[/COLOR] [B]10.0.0.251
[/B][COLOR=black]Release: [/COLOR][B]2013-05-27[/B] 
[LEFT][COLOR=black]Status: [/COLOR][B]WHQL[/B][/LEFT]
[/LEFT]

• >Download<

Your startup is pretty full as well, clear it up by following this tutorial.

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Keep us posted!

​

 

[asura8]

I don't think that was exciting enough on its own as a problem. Let's make it more interesting.

I uninstalled the existing Wifi driver and attempted to update it with the new driver. The computer claimed it was lacking the correct driver file or something of the like. I do not remember the exact term, because as I was working to at least get the old WiFi driver working again, it promptly gave me a BSOD with an error of BAD_POOL_HEADING.

I attempted to restart the computer, it gave me CORRUPT_REGISTRY, and forced me into a System Restore from two days ago, prior to when I removed Avast as a potential cause.

I'm currently running on a Clean Startup and running Windows Update to make sure the main system needs are up to date. Afterward, I'll go to the ASUS web page, run through their drivers on the support for the ASUS Z87-PRO (with the exception of the Wifi, in which I'll try again to get the same one running), and hope for the best.

If there's another BSOD, I'll put it up immediately. I will note the vast majority have been ntoskrnl.exe though - the three linked in the file were after the most recent batch of updates. I assumed I had narrowed it down to just a problem with the WiFi card, but I am beginning to wonder if that was incorrect.

Edit: As though by black magic, the driver installed correctly for the WiFi after this System Restore. I'll just stare in confusion now. This is almost as bad as some of my programming results.

Edit Edit: New BSOD while restarting between installing drivers. Including the ZIP here.

 

[YoYo155]

Did you not upload all of the available .dump files?

Anyway the last dump show signs of a possible infection.

• Download TDSS-Killer and scan for rootkits.
• Download Windows Defender Offline and scan for other types of infections.
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

Let us know the results .

 

[asura8]

I had attempted to isolate the issue on my own prior to setting it up to properly keep the .dmp files and such. I figured that it might be worth avoiding problems such as "PC User could not properly connect SATA cable" from contaminating the data.

I'll get to work on those rootkit checks though.

Edit: TDSS-Killer finds Intel(R) Capability Licensing Service Interface as a "Suspicious object, medium risk." But only as an unsigned file.

 

[asura8]

Needing to switch computers to get Windows Defender Offline working - the computer is crashing at any attempt to put in a USB now. Attached is another set of .dmp files from that set of adventures, if this helps narrow things down.

 

[asura8]

Okay. So here are the results from Windows Defender Offline and scp /scannow.

Windows Defender Offline finds nothing on the quick scan. On the full scan, it gives the error: "Your PC couldn't be scanned" with the Error Code of 0x800106ba.

scp /scannow gives "Windows Resource Protection did not find any integrity violations."

And TDSS-Killer found nothing it seems.

Am I looking at the worst case of "reinstall and hope for the best"? Or can those errors help us narrow it down?

 

[YoYo155]

Actually those dumps do help. For future reference the more information
we have to work with the better .

Now back to business, the majority of the dumps are 0x3b with c0000005 as the value for
the 1st argument. This bugcheck has been linked to graphics cards drivers passing
bad data into the kernel.

I see you using a GTX 760.

Adapter Description    NVIDIA GeForce GTX 760
Driver Version    9.18.1[COLOR=Red][U][B]3.2018[/B][/U][/COLOR]

The driver version you are using is 320.18 which isn't even listed under the compatible
driver versions for your card.
On top of that nvidia is having issue with their 320.xx family of drivers,
being that your card is a 7xx series card unfortunately that is all that is available at the moment.


Here's how we can try and mitigate the problem.

• Uninstall the nVidia display drivers and software using:
  • How do I uninstall my NVIDIA display drivers?
  • Follow though with a pass of Driver Sweeper.
• Install a the latest WHQL release:
  • Download 320.49
    When installing select Custom Settings and uncheck:
    
    3D Vision (all of them).
    HD Audio.
    Nvidia Updates.
    
    
    Do check Preform a clean installation.

If the bugchecks persists follow the same procedure but with 326.80 - BETA.
If the PC still bugchecks remove the GPU physically from the machine and use the on-board graphics.
When and if it will persist in producing bugchecks post the new .zip the SFDT generates
back here and we'll have a look .






Bugcheck summary:

Debug session time: Wed Aug 28 01:53:43.067 2013 (UTC + 3:00) 
Loading Dump File [C:\Users\Or\Desktop\comm dump\7forums\SysnativeBSOD\SysnativeBSODApps\082713-9063-01.dmp] 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532 
System Uptime: 0 days 0:00:49.285 
Probably caused by : win32k.sys ( win32k!GreSelectRedirectionBitmap+201 ) 
BugCheck 3B, {c0000005, fffff96000276c8d, fffff880076ad750, 0} 
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000003B"]SYSTEM_SERVICE_EXCEPTION (3b)[/URL] 
Bugcheck code 0000003B 
Arguments:  
Arg1: 00000000c0000005, Exception code that caused the bugcheck 
Arg2: fffff96000276c8d, Address of the instruction which caused the bugcheck 
Arg3: fffff880076ad750, Address of the context record for the exception that caused the bugcheck 
Arg4: 0000000000000000, zero. 
BUGCHECK_STR:  0x3B 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
PROCESS_NAME:  explorer.exe 
FAILURE_BUCKET_ID:  X64_0x3B_win32k!GreSelectRedirectionBitmap+201 
MaxSpeed:     3400 
CurrentSpeed: 3398 
BiosVersion = 1007 
BiosReleaseDate = 05/17/2013 
SystemManufacturer = ASUS 
SystemProductName = All Series 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Debug session time: Wed Aug 28 01:51:37.429 2013 (UTC + 3:00) 
Loading Dump File [C:\Users\Or\Desktop\comm dump\7forums\SysnativeBSOD\SysnativeBSODApps\082713-16863-01.dmp] 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532 
System Uptime: 0 days 0:00:05.647 
Probably caused by : memory_corruption ( nt!MmExtendSection+1f ) 
BugCheck 3B, {c0000005, fffff80002ff2c07, fffff88002afcce0, 0} 
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000003B"]SYSTEM_SERVICE_EXCEPTION (3b)[/URL] 
Bugcheck code 0000003B 
Arguments:  
Arg1: 00000000c0000005, Exception code that caused the bugcheck 
Arg2: fffff80002ff2c07, Address of the instruction which caused the bugcheck 
Arg3: fffff88002afcce0, Address of the context record for the exception that caused the bugcheck 
Arg4: 0000000000000000, zero. 
BUGCHECK_STR:  0x3B 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
PROCESS_NAME:  svchost.exe 
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmExtendSection+1f 
MaxSpeed:     3400 
CurrentSpeed: 3398 
BiosVersion = 1007 
BiosReleaseDate = 05/17/2013 
SystemManufacturer = ASUS 
SystemProductName = All Series 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Debug session time: Wed Aug 28 01:49:29.379 2013 (UTC + 3:00) 
Loading Dump File [C:\Users\Or\Desktop\comm dump\7forums\SysnativeBSOD\SysnativeBSODApps\082713-3213-01.dmp] 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532 
System Uptime: 0 days 0:03:02.597 
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 ) 
BugCheck BE, {fffff8a0018ec650, 30e00003e6f8b331, fffff88002754600, c} 
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x000000BE"]ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)[/URL] 
Bugcheck code 000000bE 
Arguments:  
Arg1: fffff8a0018ec650, Virtual address for the attempted write. 
Arg2: 30e00003e6f8b331, PTE contents. 
Arg3: fffff88002754600, (reserved) 
Arg4: 000000000000000c, (reserved) 
BUGCHECK_STR:  0xBE 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
PROCESS_NAME:  System 
FAILURE_BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 
MaxSpeed:     3400 
CurrentSpeed: 3398 
BiosVersion = 1007 
BiosReleaseDate = 05/17/2013 
SystemManufacturer = ASUS 
SystemProductName = All Series 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Debug session time: Wed Aug 28 01:46:07.951 2013 (UTC + 3:00) 
Loading Dump File [C:\Users\Or\Desktop\comm dump\7forums\SysnativeBSOD\SysnativeBSODApps\082713-8626-01.dmp] 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532 
System Uptime: 0 days 0:04:25.169 
Probably caused by : win32k.sys ( win32k!NtUserPeekMessage+5 ) 
BugCheck 50, {fffff88011cb47f9, 1, fffff960001748f5, 2} 
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000050"]PAGE_FAULT_IN_NONPAGED_AREA (50)[/URL] 
Bugcheck code 00000050 
Arguments:  
Arg1: fffff88011cb47f9, memory referenced. 
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. 
Arg3: fffff960001748f5, If non-zero, the instruction address which referenced the bad memory 
    address. 
Arg4: 0000000000000002, (reserved) 
BUGCHECK_STR:  0x50 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
PROCESS_NAME:  crashreporter. 
FAILURE_BUCKET_ID:  X64_0x50_win32k!NtUserPeekMessage+5 
MaxSpeed:     3400 
CurrentSpeed: 3398 
BiosVersion = 1007 
BiosReleaseDate = 05/17/2013 
SystemManufacturer = ASUS 
SystemProductName = All Series 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Debug session time: Wed Aug 28 01:37:52.712 2013 (UTC + 3:00) 
Loading Dump File [C:\Users\Or\Desktop\comm dump\7forums\SysnativeBSOD\SysnativeBSODApps\082713-5787-01.dmp] 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532 
System Uptime: 0 days 0:05:20.539 
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+51 ) 
BugCheck 3B, {c0000005, fffff80002fc9fe1, fffff8800a1e0020, 0} 
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000003B"]SYSTEM_SERVICE_EXCEPTION (3b)[/URL] 
Bugcheck code 0000003B 
Arguments:  
Arg1: 00000000c0000005, Exception code that caused the bugcheck 
Arg2: fffff80002fc9fe1, Address of the instruction which caused the bugcheck 
Arg3: fffff8800a1e0020, Address of the context record for the exception that caused the bugcheck 
Arg4: 0000000000000000, zero. 
BUGCHECK_STR:  0x3B 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
PROCESS_NAME:  audiodg.exe 
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpCloseHandleTableEntry+51 
MaxSpeed:     3400 
CurrentSpeed: 3398 
BiosVersion = 1007 
BiosReleaseDate = 05/17/2013 
SystemManufacturer = ASUS 
SystemProductName = All Series 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Debug session time: Wed Aug 28 01:32:15.930 2013 (UTC + 3:00) 
Loading Dump File [C:\Users\Or\Desktop\comm dump\7forums\SysnativeBSOD\SysnativeBSODApps\082713-6380-01.dmp] 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532 
System Uptime: 0 days 0:00:05.148 
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c ) 
BugCheck 3B, {c0000005, fffff80002c889e3, fffff88006715f60, 0} 
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000003B"]SYSTEM_SERVICE_EXCEPTION (3b)[/URL] 
Bugcheck code 0000003B 
Arguments:  
Arg1: 00000000c0000005, Exception code that caused the bugcheck 
Arg2: fffff80002c889e3, Address of the instruction which caused the bugcheck 
Arg3: fffff88006715f60, Address of the context record for the exception that caused the bugcheck 
Arg4: 0000000000000000, zero. 
BUGCHECK_STR:  0x3B 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
PROCESS_NAME:  services.exe 
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c 
MaxSpeed:     3400 
CurrentSpeed: 3398 
BiosVersion = 1007 
BiosReleaseDate = 05/17/2013 
SystemManufacturer = ASUS 
SystemProductName = All Series 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[asura8]

Attempted to install the non-beta drivers; included here is the logs from the resulting stop error. I'll work on the beta immediately, though I do not know if I'll have time to test it prior to tomorrow.

And the second attachment is from a stop error with the beta drivers. Uninstalling now.

 

[YoYo155]

The new bugchecks are spelling out driver issues, one of which
you mentioned in post #6 about the USB failing.

IRQL_NOT_LESS_OR_EQUAL (a)

Arguments:
Arg1: 0000000000000037, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002caa642, address which referenced memory

• An attempt was made to access a pageable (or completely invalid) address at an
  interrupt request level (IRQL) that is too high. This is usually
  caused by drivers using improper addresses.

fffff880`031ee3b0  fffff880`04879f60 [COLOR=Red][B][U]iusb3xhc[/U][/B][/COLOR]+0x79f60
fffff880`031ee3d0  fffff880`0486adc0 [COLOR=Red][U][B]iusb3xhc[/B][/U][/COLOR]+0x6adc0
fffff880`031ee3e8  fffff880`04832c35 [COLOR=Red][U][B]iusb3xhc[/B][/U][/COLOR]+0x32c35
fffff880`031ee4a8  fffff880`048278a6 [COLOR=Red][U][B]iusb3xhc[/B][/U][/COLOR]+0x278a6
fffff880`031ee558  fffff880`0482fc37 [COLOR=Red][U][B]iusb3xhc[/B][/U][/COLOR]+0x2fc37
fffff880`031ee580  fffff880`04879f60 [COLOR=Red][B][U]iusb3xhc[/U][/B][/COLOR]+0x79f60
fffff880`031ee5a8  fffff880`04831489 [COLOR=Red][U][B]iusb3xhc[/B][/U][/COLOR]+0x31489

• Driver Reference Table - iusb3xhc.sys

Update any intel driver using this online utility.

• Intel® Driver Update Utility

Please remove the GPU from the system and use the iGPU (onboard graphics)
for troubleshooting purposes.




Enable Driver Verifier to test other potentially problematic drivers.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Keep updating .

 

[asura8]

So. An update is in order.

Attempted to run the Intel Driver Utility, but it never completed. Tried to manually find the Intel USB 30 eXtensible Host Controller driver for Windows 7, and it gives me "This computer does not meet the minimum requirements for installing the software" as an error.

Turned on verifier.exe, crashed instantly upon restart, turned it off, as according to instructions. The current log is attached.

During all of this, the nVidia GTX 760 card has been removed.

 

[YoYo155]

Usually when Driver Verifier finds nothing, which is the case we are facing, and the bugchecks are consistently
faulting on core Windows components it's time to test the hardware.

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Post back with the results .

 

[asura8]

You had previous stately not to check the SSD drive; the link you had provided for checking the hard drives seemed to indicate a CD requirement, while I don't have any burnable CDs at the moment. Is there a utility for checking a Western Digital hard drive from a USB drive?

 

[YoYo155]

You had previous stately not to check the SSD drive; the link you had provided for checking the hard drives seemed to indicate a CD requirement, while I don't have any burnable CDs at the moment. Is there a utility for checking a Western Digital hard drive from a USB drive?

I meant not to use the CHKDSK utility on the SSD.
For now let's focus on the RAM as it seems to play a bigger role in the bugchecks.

If you don't want to use a CD to test you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of the page).

 

[asura8]

Memtest86 is now running merrily along; though I imagine it'll be about an hour and a half before even one pass is done, so full results will not be available until tomorrow.

I will note, aside from verifier.exe having a brief blue screen on an attempt to boot, it seemed to be doing pretty dandy. But I'm not even sure it GOT to really crash with verifier.exe working - it literally crashed on boot. Is that relevant?

 

[YoYo155]

Memtest86 is now running merrily along; though I imagine it'll be about an hour and a half before even one pass is done, so full results will not be available until tomorrow.

Yes memtest is an "all-nighter" type of test, that's normal.

I will note, aside from verifier.exe having a brief blue screen on an attempt to boot, it seemed to be doing pretty dandy. But I'm not even sure it GOT to really crash with verifier.exe working - it literally crashed on boot. Is that relevant?

Driver Verifier is designed to crash as soon as it detects drivers trying to commit "bad moves"
in the kernel which will lead to a crash anyway.
The benefit of a crash initiated by Driver Verifier is that the driver at fault is usually
caught red handed, so yes it should have crashed with DV enabled but nothing was detected
which sometimes happens.
That usually suggests a memory issue.
By the way make sure you read Part 3 of the tutorial if errors are found during the test.

 

[asura8]

Memtest86+ is now about twelve hours in. Seven passes have been completed, with no errors read. I'll leave it running while I am at work today to see if anything else is found - I think it'll get another 4-5 passes in during that time frame.

Given the following assumptions:
1. The memory is fine, if it passes these extra tests with no errors.
2. The video card is fine, since it crashed after being removed.
3. The second internal drive is fine, since it passed a chkdsk.
4. The SSD is fine, since Samsung Magician tells me it is.

Would it make sense to format both drives and just make a clean Windows 7 installation at this point, since it's faulting on core Windows components? I had previously installed off a boot USB - now I have the Windows 7 installation DVD. In addition, it bothers me that the Intel Driver Utility was entirely unable to recognize the chipset drivers, as well as the fact that sometimes drivers just failed to allow me to install them.

It's a fresh computer, so a new installation would not kill me to do.

 

[YoYo155]

Assuming that the memory is ok, a fresh installation is always a good idea but we want to avoid
making the same mistakes on the newly installed OS.

I would start backing up the data in preparation for a clean install.
Once that is done I suggest you run driver verifier using THIS METHOD and wait for the system
to crash a couple of times it might shed some more light as to what's really going on.

BTW aside from the SSD being in good condition, is the firmware up to date?

 

[asura8]

Samsung Magician reports the firmware as up to date of the hard drive.

So - the installation is new enough that there is literally nothing that NEEDS backing up. Just some software like Steam that is easily (and perhaps better) reinstalled. In that case, do I need a full back-up to restore from, or would it suffice to just make a System Restore point prior to using DriverVerifier?

And just to check to make sure I understand, we're essentially doing a DriverVerifier test again, except this time with Force Pending I/O Requests set to off, and waiting for a couple of crashes this time rather than the first one.

 

[YoYo155]

Samsung Magician reports the firmware as up to date of the hard drive.

So - the installation is new enough that there is literally nothing that NEEDS backing up. Just some software like Steam that is easily (and perhaps better) reinstalled. In that case, do I need a full back-up to restore from, or would it suffice to just make a System Restore point prior to using DriverVerifier?

By backup I meant your personal files, which you can't reinstall or download.
A system restore point will suffice.

And just to check to make sure I understand, we're essentially doing a DriverVerifier test again, except this time with Force Pending I/O Requests set to off, and waiting for a couple of crashes this time rather than the first one.

Correct, but these are the settings that needs to be applied (quoted from the tutorial):

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation", "and "Force Pending I/O Requests" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft and click "Next"
7. Select "Finish" on the next page.