Various BSOD

[xanderg]

I was getting 2+ BSOD daily until memtest told me I had faulty memory which I then replaced. Many BSOD's later and I've also replaced my CPU, MOBO and HDD.
My PC is a custom build and all of these parts came from the same place.

I still get occasional BSOD's and I'm really hoping it's not my GPU (the only other original part left besides the PSU and DVD burner).

I've updated drivers, flashed BIOS, etc but nothing seems to do the trick.
My computer also crashes on startup several times for which no dump file is created.

I've attached the dumps if somebody can please suggest possible causes for them.

 

[Capt.Jack Sparrow]

I was getting 2+ BSOD daily until memtest told me I had faulty memory which I then replaced. Many BSOD's later and I've also replaced my CPU, MOBO and HDD.
My PC is a custom build and all of these parts came from the same place.

I still get occasional BSOD's and I'm really hoping it's not my GPU (the only other original part left besides the PSU and DVD burner).

I've updated drivers, flashed BIOS, etc but nothing seems to do the trick.
My computer also crashes on startup several times for which no dump file is created.

I've attached the dumps if somebody can please suggest possible causes for them.

Hello Welcome to SF !!

I guess it's an issue with your Memory. Run a complete diagnostic mentioned below. Update your Chipset drivers as well because most of the USB Drivers are not verified properly. Also reinstall your Display driver.

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Update the Following Driver

DlinkUDSMBus.sys Mon Aug 18 11:50:27 2008

Bugcheck Anaylsis

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002acad50

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  TrustedInstall

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002acc469 to fffff80002accf00

STACK_TEXT:  
fffff880`009b8de8 fffff800`02acc469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009b8df0 fffff800`02aca932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009b8f30 fffff800`02acad50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0aec4b70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10


STACK_COMMAND:  kb

[FONT=Tahoma][COLOR=Red]CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
16 errors : !nt (fffff80002acad46-fffff80002acadfe)
fffff80002acad40  55  48  81  ec  58  01 *7a  00  48  8d  ac  24  80  00 *d8  00 UH..X.z.H..$....
fffff80002acad50  c6  45  ab  01  48  89 *28  b0  48  89  4d  b8  48  89 *12  c0 .E..H.(.H.M.H...
fffff80002acad60  4c  89  45  c8  4c  89 *74  d0  4c  89  55  d8  4c  89 *e1  e0 L.E.L.t.L.U.L...
fffff80002acad70  f6  85  f0  00  00  00 *93  74  64  0f  01  f8  65  4c *2e  14 .......td...eL..
...
fffff80002acadc0  00  48  89  82  80  00 *48  00  41  f6  42  03  03  66 *1f  85 .H....H.A.B..f..
fffff80002acadd0  80  00  00  00  00  00 *52  05  e8  d3  25  00  00  fc *d0  ae ......R...%.....
fffff80002acade0  5d  ac  65  0f  ae  14 *ae  80  01  00  00  0f  29  45 *01  0f ].e.........)E..
fffff80002acadf0  29  4d  00  0f  29  55 *0b  0f  29  5d  20  0f  29  65 *63  0f )M..)U..)] .)ec.[/COLOR][/FONT]

MODULE_NAME: memory_corruption

IMAGE_NAME:  [B][FONT=Tahoma][COLOR=Red]memory_corruption[/COLOR][/FONT][/B]

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Hope this helps,
Captain

 

[xanderg]

Thanks Jack.

I ran a memory test overnight twice and it picks up nothing.
Could it be the memory/cpu on the GPU since it came from the same place as all the other parts (which were all faulty)?

Since the original post, I've gotten 4 more blue screens, only 2 of which dumps got created for. They happened when I had several IE tabs open (You Tube in several), Media Player and Visual Studio open and in use so could it be GPU related?

Could you please take a look at these 2 new ones?

 

[YakSipper]

You can test the video card memory by using this:

|MG| Video Memory Stress Test 1.7.116 Download

Also, update these drivers by visiting D-Link's website:

DlinkUDSMBus DlinkUDSMBus.sys Mon Aug 18 02:20:27 2008 
DlinkUDSTcpBus DlinkUDSTcpBus.sys Mon Aug 18 02:20:20 2008

 

[xanderg]

Those drivers are for my new router which I have only recently got. The BSOD's were occuring long before so I don't think that's the problem (I'm downloading the new drivers now anyway).

I ran the stress test and it only gets error when 'ingore colors bit mask' is unchecked. The documentation is too great so I'm not sure what this means.

I did however get a BSOD whilst testing and it was a DRIVER_IRQL_NOT_LESS_OR_EQUAL so could you please take a look the dump?