BSOD issues, please help!

Toggle sidebar Toggle sidebar
V

Volcanicstrad37

Distinguished
Jun 7, 2008
51
0
18,630
Hi folks, been tinkering with getting my wife a computer set up, long story short I am having bsod issues. I had them with the full computer I started working with, then I put in my old motherboard and processor, did a fresh install. They came back, at that time I had memtest errors, so I bought new memory. I thought they were gone, but are back. My assumption, gfx card, PSW , dvd drive, or Hard drive. That is all that is left that I can replace. I can't figure out my bsod, but here is the dump

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa80080d2bb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa8000, Parameter 1 of the exception

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


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

FAULTING_IP:
+3337313636333663
fffffa80`080d2bb0 f3a4 rep movs byte ptr [rdi],byte ptr [rsi]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000007efa8000

READ_ADDRESS: 000000007efa8000

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dllhost.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff880031af888 -- (.exr 0xfffff880031af888)
ExceptionAddress: fffffa80080d2bb0
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000007efa8000
Attempt to read from address 000000007efa8000

TRAP_FRAME: fffff880031af930 -- (.trap 0xfffff880031af930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002998 rbx=0000000000000000 rcx=0000000000001b98
rdx=000000007efa0248 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa80080d2bb0 rsp=fffff880031afac0 rbp=fffff880031afbc0
r8=0000000000000002 r9=fffffa8008d20290 r10=fffffa800c0726b0
r11=fffffa8006a38680 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fffffa80`080d2bb0 f3a4 rep movs byte ptr [rdi],byte ptr [rsi]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002abc719 to fffff80002a82880

STACK_TEXT:
fffff880`031af0b8 fffff800`02abc719 : 00000000`0000001e ffffffff`c0000005 fffffa80`080d2bb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`031af0c0 fffff800`02a81ec2 : fffff880`031af888 fffffa80`0ce01010 fffff880`031af930 00000000`7efa8000 : nt!KiDispatchException+0x1b9
fffff880`031af750 fffff800`02a80a3a : 00000000`00000000 fffffa80`0ce01010 fffff880`031afa00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`031af930 fffffa80`080d2bb0 : fffff880`031afbc0 00000000`7efa00f8 fffffa80`080d6250 fffffa80`080d9750 : nt!KiPageFault+0x23a
fffff880`031afac0 fffff880`031afbc0 : 00000000`7efa00f8 fffffa80`080d6250 fffffa80`080d9750 00000000`00003000 : 0xfffffa80`080d2bb0
fffff880`031afac8 00000000`7efa00f8 : fffffa80`080d6250 fffffa80`080d9750 00000000`00003000 00000000`00000040 : 0xfffff880`031afbc0
fffff880`031afad0 fffffa80`080d6250 : fffffa80`080d9750 00000000`00003000 00000000`00000040 fffff880`031afb40 : 0x7efa00f8
fffff880`031afad8 fffffa80`080d9750 : 00000000`00003000 00000000`00000040 fffff880`031afb40 00000000`00000002 : 0xfffffa80`080d6250
fffff880`031afae0 00000000`00003000 : 00000000`00000040 fffff880`031afb40 00000000`00000002 00000000`00100000 : 0xfffffa80`080d9750
fffff880`031afae8 00000000`00000040 : fffff880`031afb40 00000000`00000002 00000000`00100000 00000000`00000002 : 0x3000
fffff880`031afaf0 fffff880`031afb40 : 00000000`00000002 00000000`00100000 00000000`00000002 00000000`7efa0000 : 0x40
fffff880`031afaf8 00000000`00000002 : 00000000`00100000 00000000`00000002 00000000`7efa0000 fffffa80`08177200 : 0xfffff880`031afb40
fffff880`031afb00 00000000`00100000 : 00000000`00000002 00000000`7efa0000 fffffa80`08177200 00000000`00000020 : 0x2
fffff880`031afb08 00000000`00000002 : 00000000`7efa0000 fffffa80`08177200 00000000`00000020 ffffffff`80000770 : 0x100000
fffff880`031afb10 00000000`7efa0000 : fffffa80`08177200 00000000`00000020 ffffffff`80000770 00000000`00010000 : 0x2
fffff880`031afb18 fffffa80`08177200 : 00000000`00000020 ffffffff`80000770 00000000`00010000 fffff880`02fd5180 : 0x7efa0000
fffff880`031afb20 00000000`00000020 : ffffffff`80000770 00000000`00010000 fffff880`02fd5180 00000000`0000d000 : 0xfffffa80`08177200
fffff880`031afb28 ffffffff`80000770 : 00000000`00010000 fffff880`02fd5180 00000000`0000d000 00000000`00000030 : 0x20
fffff880`031afb30 00000000`00010000 : fffff880`02fd5180 00000000`0000d000 00000000`00000030 00000000`00000000 : 0xffffffff`80000770
fffff880`031afb38 fffff880`02fd5180 : 00000000`0000d000 00000000`00000030 00000000`00000000 fffff880`031afb78 : 0x10000
fffff880`031afb40 00000000`0000d000 : 00000000`00000030 00000000`00000000 fffff880`031afb78 00000000`00000240 : 0xfffff880`02fd5180
fffff880`031afb48 00000000`00000030 : 00000000`00000000 fffff880`031afb78 00000000`00000240 00000000`00000000 : 0xd000
fffff880`031afb50 00000000`00000000 : fffff880`031afb78 00000000`00000240 00000000`00000000 00000000`00000000 : 0x30


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDispatchException+1b9
fffff800`02abc719 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiDispatchException+1b9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147dc36

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiDispatchException+1b9

BUCKET_ID: X64_0x1E_c0000005_nt!KiDispatchException+1b9

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa80080d2bb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa8000, Parameter 1 of the exception

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


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

FAULTING_IP:
+3337313636333663
fffffa80`080d2bb0 f3a4 rep movs byte ptr [rdi],byte ptr [rsi]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000007efa8000

READ_ADDRESS: 000000007efa8000

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dllhost.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff880031af888 -- (.exr 0xfffff880031af888)
ExceptionAddress: fffffa80080d2bb0
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000007efa8000
Attempt to read from address 000000007efa8000

TRAP_FRAME: fffff880031af930 -- (.trap 0xfffff880031af930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002998 rbx=0000000000000000 rcx=0000000000001b98
rdx=000000007efa0248 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa80080d2bb0 rsp=fffff880031afac0 rbp=fffff880031afbc0
r8=0000000000000002 r9=fffffa8008d20290 r10=fffffa800c0726b0
r11=fffffa8006a38680 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fffffa80`080d2bb0 f3a4 rep movs byte ptr [rdi],byte ptr [rsi]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002abc719 to fffff80002a82880

STACK_TEXT:
fffff880`031af0b8 fffff800`02abc719 : 00000000`0000001e ffffffff`c0000005 fffffa80`080d2bb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`031af0c0 fffff800`02a81ec2 : fffff880`031af888 fffffa80`0ce01010 fffff880`031af930 00000000`7efa8000 : nt!KiDispatchException+0x1b9
fffff880`031af750 fffff800`02a80a3a : 00000000`00000000 fffffa80`0ce01010 fffff880`031afa00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`031af930 fffffa80`080d2bb0 : fffff880`031afbc0 00000000`7efa00f8 fffffa80`080d6250 fffffa80`080d9750 : nt!KiPageFault+0x23a
fffff880`031afac0 fffff880`031afbc0 : 00000000`7efa00f8 fffffa80`080d6250 fffffa80`080d9750 00000000`00003000 : 0xfffffa80`080d2bb0
fffff880`031afac8 00000000`7efa00f8 : fffffa80`080d6250 fffffa80`080d9750 00000000`00003000 00000000`00000040 : 0xfffff880`031afbc0
fffff880`031afad0 fffffa80`080d6250 : fffffa80`080d9750 00000000`00003000 00000000`00000040 fffff880`031afb40 : 0x7efa00f8
fffff880`031afad8 fffffa80`080d9750 : 00000000`00003000 00000000`00000040 fffff880`031afb40 00000000`00000002 : 0xfffffa80`080d6250
fffff880`031afae0 00000000`00003000 : 00000000`00000040 fffff880`031afb40 00000000`00000002 00000000`00100000 : 0xfffffa80`080d9750
fffff880`031afae8 00000000`00000040 : fffff880`031afb40 00000000`00000002 00000000`00100000 00000000`00000002 : 0x3000
fffff880`031afaf0 fffff880`031afb40 : 00000000`00000002 00000000`00100000 00000000`00000002 00000000`7efa0000 : 0x40
fffff880`031afaf8 00000000`00000002 : 00000000`00100000 00000000`00000002 00000000`7efa0000 fffffa80`08177200 : 0xfffff880`031afb40
fffff880`031afb00 00000000`00100000 : 00000000`00000002 00000000`7efa0000 fffffa80`08177200 00000000`00000020 : 0x2
fffff880`031afb08 00000000`00000002 : 00000000`7efa0000 fffffa80`08177200 00000000`00000020 ffffffff`80000770 : 0x100000
fffff880`031afb10 00000000`7efa0000 : fffffa80`08177200 00000000`00000020 ffffffff`80000770 00000000`00010000 : 0x2
fffff880`031afb18 fffffa80`08177200 : 00000000`00000020 ffffffff`80000770 00000000`00010000 fffff880`02fd5180 : 0x7efa0000
fffff880`031afb20 00000000`00000020 : ffffffff`80000770 00000000`00010000 fffff880`02fd5180 00000000`0000d000 : 0xfffffa80`08177200
fffff880`031afb28 ffffffff`80000770 : 00000000`00010000 fffff880`02fd5180 00000000`0000d000 00000000`00000030 : 0x20
fffff880`031afb30 00000000`00010000 : fffff880`02fd5180 00000000`0000d000 00000000`00000030 00000000`00000000 : 0xffffffff`80000770
fffff880`031afb38 fffff880`02fd5180 : 00000000`0000d000 00000000`00000030 00000000`00000000 fffff880`031afb78 : 0x10000
fffff880`031afb40 00000000`0000d000 : 00000000`00000030 00000000`00000000 fffff880`031afb78 00000000`00000240 : 0xfffff880`02fd5180
fffff880`031afb48 00000000`00000030 : 00000000`00000000 fffff880`031afb78 00000000`00000240 00000000`00000000 : 0xd000
fffff880`031afb50 00000000`00000000 : fffff880`031afb78 00000000`00000240 00000000`00000000 00000000`00000000 : 0x30


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDispatchException+1b9
fffff800`02abc719 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiDispatchException+1b9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147dc36

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiDispatchException+1b9

BUCKET_ID: X64_0x1E_c0000005_nt!KiDispatchException+1b9

Followup: MachineOwner



Any Help would be GREATLY appreciated, my wife needs to get her FF14 ON! :)
System specs now are amd phenom 965, nvidia 260, 700w CM PSU, 8g ram, win7
 
Sort by date Sort by votes
RaDiKaL_

RaDiKaL_

Splendid
Apr 17, 2006
3,702
1
26,960
So initially the BSODs occurred with new CPU + MOBO + RAM, then you used an old CPU+MOBO and another new set of RAM...

on both setups you got the same BSODs? when does it occur, while heavy load,specific use of an application, idle, after several hours of usage, random times?

For the problem to persist after changing core pieces + fresh install... any PSU issue is usually accompanied with power instability issues, so if you're not having any of those then I'd discard it from the list (check the PSU voltages in BIOS or with a multimeter if you wanna be sure)

DVD Drive... I had some cases where the DVD Drive would cause a BSOD, but only when used, so in order to discard it try booting your pc with the dvd drive disconnected and see if the BSODs dissapear.

HDD... you could check its status booting with Hiren's Boot or Seagate Tools.

GPU... mostly this cause issues when on load, further help on this will depend on answering some of my previous questions in this post.

Anyways... the fact that dllhost.exe is the one causing the BSOD leads me to think that it's a software issue, either because the HDD is getting the files corrupted or because some driver you've used in both installations is faulty, if crashes happen at random times (happening while on idle) try booting your PC on safe mode and leave it there for several hours, see if the BSOD replicates.

 
Upvote 0 Downvote
V

Volcanicstrad37

Distinguished
Jun 7, 2008
51
0
18,630


Yeah initially the bsod was happening to a full setup I was given. I since swapped out the mobo, cpu, and ram. So theoretically it should be any of those. The BSOD is intermittent, it happens at times when she is in a game, but also we can leave the room and have nothing but chrome running and it could blue screen. There is nothing in the dvd drive and we havent been using it other than installing drivers/windows. I will have to try Hirens Boot or Seagates tools to check drives, I will report back on that.
After further investigation thinking driver related, could it be Windows Update related? It is failing to install an update, and I just tried again, it failed and I got the BSOD.
 
Upvote 0 Downvote
RaDiKaL_

RaDiKaL_

Splendid
Apr 17, 2006
3,702
1
26,960
Indeed, Windows Updates are known from locking/crashing PCs more frequently than MS would like to admit (though again if HDD is corrupting data it could be the cause that the windows updates are failing), so 1st test the HDDs, then test in safe mode to see if BSODs appear, and then a final fresh install disabling windows updates, if successful you could download the stand-alone updates in order to keep your windows updated.
 
Upvote 0 Downvote
V

Volcanicstrad37

Distinguished
Jun 7, 2008
51
0
18,630


Did a manual install of SP1 which was not installing as a normal update. Still got a blue screen. Also ran Seagate's tools and had no errors. With intermittent bsods as far as "testing in safe mode" Would I just go in safe mode and wait? The biggest problem is I can't replicate it. I Ran Furmark and got a bsod, then did it again and no bsod. Ran system files check for windows and got no errors. I'm losing patience at this point. Any other suggestions? Also the last dump said nsft.sys was the error.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom