So for the Last couple weeks now I have been experiancing Random BSOD, The Errors it tosses up are totally random at times. I will sometimes get them constantly like every 15 mins for a couple hours or not experiance one for several days.

I have looked into this issue myself over these last few weeks and have tried to troubleshoot the problem then entire time, I have issued commands via the CMD like scannow and checkdsk, I have made sure Memory is ok and run not only a virus scan but a rootkit scan for error, i even downloaded the C Cleaner to check the system and have for the most part not been able to stop these blue screens from happening, as well as done a drive check to make sure all drivers are up to date

I have also tried things like not using certain features to make sure if that wasn't the cause of it but have turned up nothing

I am starting to get to my wits end on this because this computer is newer then the laptop i have and even though the laptop is nearly 6 years old it doesn't have any of these issues ever. Please Help

 We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

here is a onedrive link to the zipped Minidump folder

https://onedrive.live.com/redir?resid=F79005B817F244F2!116&authkey=!AOqBLCpdxrCk4pc&ithint=file%2czip

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

If you are over-clocking anything reset to default before running these tests.
In other words STOP!!!  

If you do not know what this means you probably are not


1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)

Hi Neo,

According to one of analyzing results, this issue seems to be related to the USB driver. Please update the USB driver or reinstall the USB controller driver from the device manager to have a check .We also can try to unplugin all the USB devices to have a check a the symptom.

Here is the analysis result:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffd000dfe77545, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800d1a27265, address which referenced memory

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

OVERLAPPED_MODULE: Address regions for 'bthhfenum' and 'tunnel.sys' overlap

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8015b1f0138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffd000dfe77545

CURRENT_IRQL:  2

FAULTING_IP:
Wdf01000!FxRequest::_CreateForPackage+15
fffff800`d1a27265 4883ec30        sub     rsp,30h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFD000DFE8DFB0

TRAP_FRAME:  ffffd000dfe860c0 -- (.trap 0xffffd000dfe860c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd000dfe86258 rbx=0000000000000000 rcx=ffffe001697f7af0
rdx=ffffe001697f7d38 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800d1a27265 rsp=ffffd000dfe86250 rbp=ffffd000dfe862b0
 r8=ffffe0016b693010  r9=ffffd000dfe862a0 r10=0000000000000801
r11=ffffd000dfe86298 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Wdf01000!FxRequest::_CreateForPackage+0x15:
fffff800`d1a27265 4883ec30        sub     rsp,30h
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8015afe94e9 to fffff8015afdd9a0

STACK_TEXT: 
ffffd000`dfe85f78 fffff801`5afe94e9 : 00000000`0000000a ffffd000`dfe77545 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`dfe85f80 fffff801`5afe7d3a : 00000000`00000001 ffffe001`6b660ab0 00000000`00000000 00000000`c00000bb : nt!KiBugCheckDispatch+0x69
ffffd000`dfe860c0 fffff800`d1a27265 : 00000000`00000000 fffff800`d1a27ff3 ffffe001`6b660ab0 ffffd000`dfe862b0 : nt!KiPageFault+0x23a
ffffd000`dfe86250 fffff800`d1a27ff3 : ffffe001`6b660ab0 ffffd000`dfe862b0 ffffe001`697f7af0 ffffe001`6b693010 : Wdf01000!FxRequest::_CreateForPackage+0x15
ffffd000`dfe86260 fffff800`d3fda6ac : ffffe001`6b620778 00000000`00000000 fffff800`d3fd9d54 ffffe001`6b693010 : Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x1eb
ffffd000`dfe862e0 fffff800`d3fd9d31 : 00000000`00000000 00000000`00000009 ffffe001`6b620778 00000000`00000000 : ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x194
ffffd000`dfe86390 fffff800`d3fcfe30 : 00001ffe`96c386d8 ffffe001`6b693010 ffffd000`dfe86450 ffffe001`6b6933f8 : ucx01000!Urb_USBPORTStyle_ProcessURB+0x331
ffffd000`dfe863f0 fffff800`d1a06d43 : ffffe001`6b693010 ffffd000`dfe86520 00000000`0000000f ffffe001`693c7920 : ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x448
ffffd000`dfe86480 fffff800`d1b72c27 : 00000000`00220003 ffffd000`dfe865f0 00000001`00000001 000000e8`00000001 : Wdf01000!FxDevice::DispatchWithLock+0xb01
ffffd000`dfe86560 fffff800`d1b70147 : ffffe001`680a24f0 00000000`00000007 ffffe001`6b693010 fffff801`5ae44229 : ACPI!ACPIIrpDispatchDeviceControl+0x97
ffffd000`dfe86590 fffff800`d430ccae : 00000000`00000007 00000000`00000000 ffffd000`dfe86640 ffffe001`6b672b90 : ACPI!ACPIDispatchIrp+0x137
ffffd000`dfe86600 fffff800`d1a06d43 : ffffe001`6b693010 ffffd000`dfe86789 ffffe001`6b693010 ffffe001`6b6a5280 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xdf6
ffffd000`dfe86710 fffff800`d1b72c27 : 00000000`00000000 00000500`00000500 00001dfd`00001000 ffffe001`67d59010 : Wdf01000!FxDevice::DispatchWithLock+0xb01
ffffd000`dfe867f0 fffff800`d1b70147 : ffffe001`6b6312c0 00000000`00000007 ffffe001`6b693010 ffffe001`67d59060 : ACPI!ACPIIrpDispatchDeviceControl+0x97
ffffd000`dfe86820 fffff801`5af41d50 : 00000000`00000007 ffffd000`dfe1bf00 ffffd000`dfe86990 ffffd000`dfe86b30 : ACPI!ACPIDispatchIrp+0x137
ffffd000`dfe86890 fffff801`5af41007 : 00000000`00000001 ffffd000`dfe86b20 ffffd000`dfe19180 00000000`00000001 : nt!KiExecuteAllDpcs+0x1b0
ffffd000`dfe869e0 fffff801`5afe14ea : ffffd000`dfe19180 ffffd000`dfe19180 ffffd000`dfe253c0 ffffe001`6b2bd080 : nt!KiRetireDpcList+0xd7
ffffd000`dfe86c60 00000000`00000000 : ffffd000`dfe87000 ffffd000`dfe81000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb

FOLLOWUP_IP:
ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+194
fffff800`d3fda6ac b803010000      mov     eax,103h

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+194

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ucx01000

IMAGE_NAME:  ucx01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54337387

IMAGE_VERSION:  6.3.9600.17393

BUCKET_ID_FUNC_OFFSET:  194

FAILURE_BUCKET_ID:  AV_ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer

BUCKET_ID:  AV_ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_ucx01000!urbhandler_usbportstyle_legacy_bulkorinterrupttransfer

FAILURE_ID_HASH:  {ea6098da-d901-6f4c-146d-11eca068e7a2}

Followup: MachineOwner

Best r

You know I was wondering if that was the issue, right now my computer is going through a increase in BSOD and I haven't been able to figure it out this time around, I ran Memory tester and got no errors so no mem corruption and now its been a case of a single USB device causing major issues

Whats been happening is my computer doesnt have a wireless internet card, so when i got it I bought a wireless usb adapter, whenever I plug that adapter in now it seems to be causing the issue to arise, The adapter is a Netgear WNDA3100 v2, this morning when i tried to log in after going through login screen comp just started crashing but when i removed adapter it was fixed, could this be the cause and if it is, i know i have been trying to update it or fix it in any way should i contine looking at a fix for this or is it better to just replace the device?

should also note I just tried to set up internet connection for desktop via ethernet with Laptop and its also causing crashes

NBL

Upload the new DMPS

@MX  may also be bluetooth

OVERLAPPED_MODULE: Address regions for 'bthhfenum' and 'tunnel.sys' o

A new minidump zip was uploaded to onedrive

https://onedrive.live.com/redir?resid=F79005B817F244F2!117&authkey=!AG4f7CiOK5P_Q2w&ithint=file%2czip

NBL

None of these had verifier enabled and there are 6 different error codes.  The first thing you need to do is to update to win 8.1.  That in itself may fix the problem.  If it does not then run verifier so we can find the underlying cause

Took awhile for everything to finish, but comp finally crashed this should be the newest report

I let it run for like 2-3 hours with no crashing happening but as soon as i tried to watch a youtube video it crashed

https://onedrive.live.com/redir?resid=F79005B817F244F2!118&authkey=!AFdWUFj9kqCaOk4&ithint=file%2czip

NBL

Driver verified and related to your DirextX/video driver.  There is a known problem with the Feb 2015 nVidia drivers on some pci systems.  As a work around I would install a much older driver (~9months older) until they release a less buggy driver

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\minidump 2\030715-39265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: 
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff800`2621d000 PsLoadedModuleList = 0xfffff800`264f6250
Debug session time: Sat Mar  7 18:18:57.020 2015 (UTC - 5:00)
System Uptime: 0 days 2:58:52.730
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8011c53c580, b, 8, fffff8011c53c580}

GetPointerFromAddress: unable to read from fffff800265800e8
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrCollectDbgInfoStage1+0 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8011c53c580, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8011c53c580, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80026580138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 fffff8011c53c580 

CURRENT_IRQL:  b

FAULTING_IP: 
dxgkrnl!TdrCollectDbgInfoStage1+0
fffff801`1c53c580 48895c2410      mov     qword ptr [rsp+10h],rbx

IP_IN_PAGED_CODE: 
dxgkrnl!TdrCollectDbgInfoStage1+0
fffff801`1c53c580 48895c2410      mov     qword ptr [rsp+10h],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

TRAP_FRAME:  ffffd00020bd2470 -- (.trap 0xffffd00020bd2470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe0006dcf3000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8011c6eef80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8011c53c580 rsp=ffffd00020bd2608 rbp=fffff8011c6eef80
 r8=ffffe0006e3c0540  r9=0000000000000000 r10=0000000000000000
r11=fffff8011c6f044f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgkrnl!TdrCollectDbgInfoStage1:
fffff801`1c53c580 48895c2410      mov     qword ptr [rsp+10h],rbx ss:0018:ffffd000`20bd2618=ffffe0006e3c3010
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800263794e9 to fffff8002636d9a0

FAILED_INSTRUCTION_ADDRESS: 
dxgkrnl!TdrCollectDbgInfoStage1+0
fffff801`1c53c580 48895c2410      mov     qword ptr [rsp+10h],rbx

STACK_TEXT:  
ffffd000`20bd2328 fffff800`263794e9 : 00000000`0000000a fffff801`1c53c580 00000000`0000000b 00000000`00000008 : nt!KeBugCheckEx
ffffd000`20bd2330 fffff800`26377d3a : 00000000`00000008 ffffe000`6e3c0540 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`20bd2470 fffff801`1c53c580 : fffff801`1c6eefa9 00000000`00000006 ffffe000`6e3c3010 ffffe000`00000003 : nt!KiPageFault+0x23a
ffffd000`20bd2608 fffff801`1c6eefa9 : 00000000`00000006 ffffe000`6e3c3010 ffffe000`00000003 00000000`00000000 : dxgkrnl!TdrCollectDbgInfoStage1
ffffd000`20bd2610 fffff800`2636e632 : 00000000`00000008 ffffe000`6e3c1970 ffffd000`20bd2b68 ffffd000`20bd28c8 : dxgmms1!VidSchiStartContextRunningTimeAtISR+0x29
ffffd000`20bd2660 fffff801`1c44598f : ffffe000`69004ef0 fffff801`1c6eef80 ffffe000`6e3c0540 ffffe000`6e3aa010 : nt!KeSynchronizeExecution+0x42
ffffd000`20bd26a0 fffff801`1c6ec26b : 00000000`00000000 ffffd000`20bd2799 ffffe000`6dcf3c80 00000000`00000001 : dxgkrnl!DpSynchronizeExecution+0xaf
ffffd000`20bd26f0 fffff801`1c70db2e : ffffe000`6e3c1970 ffffe000`6e3c1970 ffffe000`6dcf3c80 ffffe000`6dcc1000 : dxgmms1!VidSchiSendToExecutionQueue+0x38b
ffffd000`20bd2800 fffff801`1c7231d2 : ffffe000`6e3c1970 ffffe000`6dcc1000 ffffe000`00000000 ffffe000`00000005 : dxgmms1!VidSchiSubmitRenderCommand+0x60e
ffffd000`20bd2b50 fffff801`1c722f7d : ffffe000`6dcc1000 ffffe000`00000000 00000000`00000080 ffffe000`6dd30500 : dxgmms1!VidSchiRun_PriorityTable+0x252
ffffd000`20bd2bc0 fffff800`262f5280 : ffffd001`7448f3c0 ffffe000`6dd30500 ffffd000`20bd2c90 fffff800`26370d7d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`20bd2c00 fffff800`26373fc6 : ffffd001`74483180 ffffe000`6dd30500 ffffd001`7448f3c0 fffff800`268a1be2 : nt!PspSystemThreadStartup+0x58
ffffd000`20bd2c60 00000000`00000000 : ffffd000`20bd3000 ffffd000`20bcd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!TdrCollectDbgInfoStage1+0
fffff801`1c53c580 48895c2410      mov     qword ptr [rsp+10h],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!TdrCollectDbgInfoStage1+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54505515

IMAGE_VERSION:  6.3.9600.17415

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_dxgkrnl!TdrCollectDbgInfoStage1

BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_dxgkrnl!TdrCollectDbgInfoStage1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_vrf_code_av_paged_ip_dxgkrnl!tdrcollectdbginfostage1

FAILURE_ID_HASH:  {14445528-6aa8-f622-6e6e-1a44c5bc2080}

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

Is there somewhere specific i should look to do this fix or a link to help me get this issue specifi issue resolved?

NBL

You can get a video driver from either nVidia or better yet your computer maker.  The procedure is simple.  Download the old driver>remove the current one>install the downloaded one.

Ok I'll try to get that done, unfortunatly when I tried opening my web browser(google Chrome) it crashed with a different error, i have uploaded a zip with the new dmp file created

https://onedrive.live.com/redir?resid=F79005B817F244F2!119&authkey=!AIkFbGVc9utnIEo&ithint=file%2czip

Ignore above link, I have reuploaded dmp files into new zip that should have ever dmp from today to just now

https://onedrive.live.com/redir?resid=F79005B817F244F2!120&authkey=!AHGQHRgB2G_oS6E&ithint=file%2czip

NBL

With this many different error codes and this many driver verified causes my first thought would be Malware and yes I did see that you ran a scan.  Please run a Malwarebytes scan just to eliminate the possibility and run a system file check.  If both of these come back clean it may be time to start thinking about either refreshing the OS

Please download the free version of Malwarebytes. Update it immediately.
Do a full system scan
Let us know the results at the end.

http://www.malwarebytes.org/products

Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.

System file check (SFC) Scan and Repair System Files

So I have done 2 runs of Malwarebytes, one in safe mode the other in normal, with most recent version of malwarebytes, it returned no threats detected, 

As for the SFC, I have run that many times since this issue has started, and maybe once or twice it found integrity errors it fixed early on, I had it run again

I have tried other issues to see if that was a problem, Like i ran memtest with no errors, done a chkdsk and it hasn't found errors, I have done a system refresh and it did not fix anything.

couple interesting Notes: the malwarebytes could not install initially it kept bsod when i tried to install, so i moved to safe mode and it installed, the other thing is that Last night I used the computer to its fullest playing a fullscreen game while using skype with firends and it didn't crash at all, instead when i stopped playing the games it went about 5 min on the desktop and crashed again, I have uploaded the newer DMP files

https://onedrive.live.com/redir?resid=F79005B817F244F2!139&authkey=!AMirCsHbBehGAZ8&ithint=file%2czip

NBL

Still memory corruption and driver verified.

Since we have eliminated malware, and syc finds nothing I am begging to think hardware.

Have you run memtest?  If not do so.

If that comes back clean we need to stress the CPU, GPU, etc.

note in answer above I have done the MemTest

NBL

I only see that you ran a memory test.  I did not see memtest nor how many passes you did.  If you are satisfied your memory is ok then move on to the other hardware.

Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:

- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
- Click "Quit" to exit

Try this free stress test:  http://www.mersenne.org/freesoft/
Prime95 Setup;
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
The Test selection box and the stress.txt file describes what components that the program stresses.

I used MemTest and did an overnight run of it which when i got back to it had done about 8-10 pass's with no errors detected, I have now run the Furmark setup and it stoped increasing at about 81C, the Prime95 is running now and will run for awhile, is there anything else I need to do and if there is not is there anything you will need me to upload once its done

Also Thanks in advance for helping me to try and solve this issue

So I have done the full Prim95 scan for a little over 24 hours and it did not crash system at all, when I ran the FurMark test it peaked at about 81 degrees C, no errors popped up, as stated above I did the MemTest for over a night before with 8-10 passes with no corruption, right now the system hasn't crashed, I don't know if i need to upload anything or if I need to test anything else

So Interesting Note: it has been a little over an hour since I stopped Stress testing the PC, and the n it BSOD and gave a IRQL_NOT_LESS_OR_EQUAL error

NBL

So you have tested CPU, RAM, video, and installed a fresh system.  The only things left are the power supply, motherboard, or some mechanical issue with a peripheral

I take it that means opening up the tower and looking?

NBL

Your call.  You can either try to track the BSOD down or live with it.  It might even be heat and opening the tower might shed a clue.

So over the last couple of days I have tried to track down BSOD, it hasnt happened often but I think i might have found something that is causing it, I don't know for 100% sure but when I try to do a system scan using Windows Defender it seems to BSOD a chunk of the way through the scan, don't know for sure when, could it be Defender has a problem or that it is scanning something that causes the problem?

NBL

We can only tell from the DMP files (hopefully with verifier enabled)

crap, I had turned that off again, Ill try to get the BSOD to happen again with Verifier enabled this time, ill upload DMP after that

So Interesting Note, I have tried to run windows defender several times, and not a single time did computer BSOD, every once and awhile the defender caused computer to become slower then molasses and i waited like 10 minutes for it to become responsive again, but it did not BSOD on me after i activated Verifier, I dont know if/when itll BSOD again but next time it does ill do the upload for sure

The only thing I dont see already in this thread is the possibility of disk failure? If Windows Defender crashes part way through a full scan, it could be encountering an I/O failure. You should run ChkDsk /R to verify the integrity of your file system and scan the disk for errors.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet