BSOD occuring with increased frequency, no definite cause on new build

Welcome to SF :) !

Your bugchecks you're experiencing are indicative of a bad driver please run Driver Verifier
following the tutorial below.

• Using Driver Verifier to identify issues with Drivers

Arc said:

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.

Let us know the results!

I ran DV without success, my computer just froze and no new .dmp files were created. In frustration I reinstalled my OS, but im still getting the BSOD. This time it happened when I loaded chrome, but that could be just a coincidence. Is it possible that it is a hardware problem? Also included new .dmp files after installation.

Unfortunately the dump file is corrupt.
Attachment 283970


The intel HD graphics driver didn't install correctly, as well are the drivers for your USB add on card.

Code:

Universal Serial Bus (USB) Controller        The drivers for this device are not installed.
Intel(R) HD Graphics 4000       39

Update the intel graphics drivers by using this utility.

• Intel® Driver Update Utility

Check for the firmware updates for your SSD:

• Neutron Series

Test Your RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• 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.

Thanks for the update, keep us posted :) .

Most bugchecks didn't offer much information and require you to enable Driver verifier
but one did manage to show something.

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031c2261, Address of the instruction which caused the bugcheck
Arg3: fffff88002b1b020, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


OVERLAPPED_MODULE: Address regions for 'hiber_iaStor' and 'hiber_iaStor' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

Code:

lmvm iastor
start             end                 module name
fffff880`01049000 fffff880`013ed000   iaStor     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Thu Feb 02 02:15:24 2012 (4F29D59C)
    CheckSum:         0008B2F8
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Arc said:

Get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

Then enable driver verifier as detalied in post #2.

gpzeke said:

Here should be an updated dmp that hopefully isn't corrupt. I uninstalled the intel rapid storage after the fact and I will be running driver verifier this weekend whilst I am away.

It's the same file actually which means no new dumps .

If you're going to use Driver Verifier do with the intention of using the PC as you would normally,
with the exception of handling any important data keeping in mind that
the system can crash at any moment.