BSOD - Bugcheck in Windows 7

[dgafin]

I'm having a weird issue with a new computer I just built for a friend. He is going to mostly be using this to record audio using Cool Edit Pro, Adobe Audition, and Audicity. After building the computer and installing Windows 7 Ultimate x64 everything seemed like it was working great for me, and I had no BSODs or reboots. I had the latest BIOS and drivers installed from the Biostar website.

He then got the computer and started recording using Cool Edit Pro and ended up getting some BSODs and the computer would restart on it's own. He said it did this about 4-5 times in two days. I got the computer back and ran the MS Memory diagnostics and it came up with no errors. I tried Memtest86 but it wouldn't even run for some reason. Probably a quad-core processor thing. Anyways, the memory seems to be ok. I then ran Prime95 for about an hour and a half with no reboots or errors. I'm guessing if there was something really wrong hardware wise this would never hold up, and it did. So, does anyone have any idea what this could be? Below is a couple screenshots of what the error in event viewer says and also the list of parts for this build. Not included in that list is a WD Caviar Black 640GB drive I had laying around that I put in there. Any help would be greatly appreciated.

 

[Demon10000]

I would look further into why Memtest wouldn't work. I wouldn't expect it to fail with a quadcore processors, especially if you were running a new version.

The last couple of biostar boards I had came with Memtest86 built into it. Check to see if it's an option in the BIOS, or an option to boot to when you manually choose the boot device at Post.


You'll have to look in the dump file to find the module thats causing the issue. It's most likely a driver.

 

[dgafin]

Ok, I'll check that when I get home. In the meantime here is what I gathered from the dump file:

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002c1d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

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

FAULTING_IP:
nt!FsRtlLookupPerStreamContextInternal+33f
fffff800`02c6d7e7 66390a cmp word ptr [rdx],cx

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000007efa0000

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
000000007efa0000

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

BUGCHECK_STR: 0x1E_c0000005

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cc7a39 to fffff80002c8d740

STACK_TEXT:
fffff880`031a0c68 fffff800`02cc7a39 : 00000000`0000001e ffffffff`c0000005 fffff800`02c6d7e7 00000000`00000000 : nt!KeBugCheckEx
fffff880`031a0c70 fffff800`02c8cd82 : fffff880`031a1438 fffff880`08a8a8d0 fffff880`031a14e0 00000000`00000000 : nt!FsRtlInitializeBaseMcbEx+0x4345
fffff880`031a1300 fffff800`02c8b8fa : 00000000`00000000 fffff880`08a8a8d0 fffffa80`048bbe00 fffff800`02fa3d2e : nt!KeSynchronizeExecution+0x3e32
fffff880`031a14e0 fffff800`02c6d7e7 : fffff800`02c6d872 00000000`00000010 00000000`00000082 fffff880`031a16a8 : nt!KeSynchronizeExecution+0x29aa
fffff880`031a1678 fffff800`02c6d872 : 00000000`00000010 00000000`00000082 fffff880`031a16a8 fffffa80`03726680 : nt!FsRtlLookupPerStreamContextInternal+0x33f
fffff880`031a1680 fffffa80`047e7bc6 : fffff880`031a17b0 00000000`00000000 fffffa80`047ec260 fffffa80`047f0300 : nt!RtlImageNtHeader+0x1e
fffff880`031a16b0 fffff880`031a17b0 : 00000000`00000000 fffffa80`047ec260 fffffa80`047f0300 00000000`00000000 : 0xfffffa80`047e7bc6
fffff880`031a16b8 00000000`00000000 : fffffa80`047ec260 fffffa80`047f0300 00000000`00000000 00000000`00000000 : 0xfffff880`031a17b0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!FsRtlLookupPerStreamContextInternal+33f
fffff800`02c6d7e7 66390a cmp word ptr [rdx],cx

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!FsRtlLookupPerStreamContextInternal+33f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

 

[Demon10000]

I think you've got a driver causing issues or memory problems. I am leaning towards memory problems, only because of the issues you mentioned with memtest. I've never seen it not run!

Try this -- grab a few more dumps and analyze them -- see if you get simiar results. It almost seems like you've got a memory problem that is causing a driver problem...

 

[dgafin]

I think the reason the memtest wasn't working was because I was trying to use the 3.5 which doesn't work with 4GB of ram. I need to try 3.4 when I get home. I'll let you know what happens. Don't you think if it was a memory issue it would have failed the MS memory test? I'm not sure how well that test actually works...just a thought. Thanks for your help thus far.

 

[dgafin]

Running memtest86 version 3.4 for an hour caused no errors. Should I let it run longer, or do you think the errors would come up pretty rapidly?

 

[ehksohset]

That crash dump seems to indicate either a driver or memory issue. Here's how I'd approach the situation:

If you're overclocking, return to stock speeds. Make sure you're running the latest BIOS version and update your chipset/mobo drivers. During a brief google search, I saw one reference to updating the video card driver, but that would be lower on my list to check. If you have multiple sticks of RAM, pull all of them out except for one at a time, and see if these BSODs occur with a particular stick. Goodluck troubleshooting..