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

[gpzeke]

Ok, so I just built a new computer and when I booted it up for the first time after installing the OS it BSOD'd on me. I figured once could just be a fluke and I won't let it concern me unless it becomes a frequent problem. Well last night it occurred three times and once right before I wrote this post. I can't seem to find a specific trigger for this event, but it is becoming increasingly frustrating. I know this isn't a lot of information to go on, but I have included the .dmp information.

Thanks in Advance.

 

[YoYo155]

Welcome to SF !

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

• http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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!

 

[gpzeke]

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.

 

[YoYo155]

Unfortunately the dump file is corrupt.
View attachment 283970


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

Universal Serial Bus (USB) Controller        [B]The drivers for this device are not installed.[/B]
Intel(R) HD Graphics 4000       [COLOR=Red][B]39[/B][/COLOR]

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:

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.

 

[gpzeke]

It appears my RAM is bad, I am working on replacing and then I will update the SSD and check the intel drivers.

 

[YoYo155]

Thanks for the update, keep us posted .

 

[gpzeke]

Sorry for the long gap, I didn't want to mark it as solved just yet. I wanted to let it run for a bit and see if anymore problems would arise. I replaced the ram last Saturday, August 31st. It's run fine up until a few seconds ago. The blue screen didn't pop up this time but I will attach the .dmp file and see if you can determine the issue this time.

 

[YoYo155]

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

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 '[COLOR=Red][U][B]hiber_iaStor[/B][/U][/COLOR]' overlap

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

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

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]

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.

 

[YoYo155]

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.

 

[gpzeke]

Oh, I understand. I will run it for the remainder of the week and see if it causes another BSOD. If not I guess I will mark this post as solved. Thank you for your help and I appreciate the time you have dedicated to help me solve this problem.

-gpzeke

 

[YoYo155]

Take your time .
It's my pleasure, fingers crossed !