Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD crashes. 3D and Video editing machine. plenty of minidumps

21 Apr 2016   #1
sphenic

Windows 7 Professional X64
 
 
Random BSOD crashes. 3D and Video editing machine. plenty of minidumps

Hi everyone.

Could someone please have a look at the minidumps, and try to figure out what is causing this computer to BSOD regulary? Sometimes it crashes within an hour, sometimes it takes days.

EDIT: Just found a guide on here on troubleshooting BSOD which was a great resource. Have now activated the driver verifier with default settings. No experience using it before but we'll see...

Included 3 random windiag dumps underneath, but not sure what to look for

Thanks for any and all help




Attached Files
File Type: zip NOR-NX10036175 - 21.04.16.zip (3.25 MB, 2 views)
My System SpecsSystem Spec
.
21 Apr 2016   #2
sphenic

Windows 7 Professional X64
 
 

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6800050e000
Arg3: 8cd0000510f97867
Arg4: fffffa801e22f870

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


BUGCHECK_STR: 0x1a_41201

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff800034e74be to fffff80003488c80

STACK_TEXT:
fffff880`0d76a878 fffff800`034e74be : 00000000`0000001a 00000000`00041201 fffff680`0050e000 8cd00005`10f97867 : nt!KeBugCheckEx
fffff880`0d76a880 fffff800`03454461 : 00000000`00000000 00000000`00000000 00000000`00000000 8cd00005`10f97867 : nt! ?? ::FNODOBFM::`string'+0x13562
fffff880`0d76a8c0 fffff800`034540fa : fffffa80`1e22f870 fffffa80`1d6efb30 fffffa80`1d6efb30 00000000`a1c00000 : nt!MiQueryAddressState+0x2b1
fffff880`0d76a910 fffff800`0375fde4 : fffff880`00000004 00000000`a1c01000 fffffa80`1e22f870 fffff680`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`0d76a980 fffff800`03487f13 : 00000000`00000168 fffffa80`22cc5b50 fffff880`0d76aa88 00000000`001bad58 : nt!NtQueryVirtualMemory+0x382
fffff880`0d76aa70 00000000`76fbc04a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001bad38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fbc04a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+13562
fffff800`034e74be cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+13562

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5507a63e

IMAGE_VERSION: 6.1.7601.23002

FAILURE_BUCKET_ID: X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13562

BUCKET_ID: X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13562

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_41201_nt!_??_::fnodobfm::_string_+13562

FAILURE_ID_HASH: {6d563c2b-b273-054f-6a5e-f8fe3d3d2dd9}

Followup: MachineOwner
My System SpecsSystem Spec
21 Apr 2016   #3
sphenic

Windows 7 Professional X64
 
 

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80108873c0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: OUTLOOK.EXE

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff8000353b720 to fffff800034c9c80

STACK_TEXT:
fffff880`0fddbe68 fffff800`0353b720 : 00000000`0000001a 00000000`00041790 fffffa80`108873c0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0fddbe70 fffff800`034b71bf : fffffa80`00000000 00000000`2d2d3fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33964
fffff880`0fddc030 fffff800`034c8f13 : ffffffff`ffffffff fffff8a0`296620e8 fffff8a0`29662110 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0fddc130 fffff800`034c54d0 : fffff880`05a3562e fffff8a0`2c0c8010 fffffa80`23b25060 fffffa80`21ae8790 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0fddc2c8 fffff880`05a3562e : fffff8a0`2c0c8010 fffffa80`23b25060 fffffa80`21ae8790 fffff8a0`296620e0 : nt!KiServiceLinkage
fffff880`0fddc2d0 fffff880`05a20c93 : fffff880`0fddc2f8 fffff8a0`1b907420 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0fddc300 fffff880`05a1b637 : fffffa80`218ed290 00000000`00000000 fffff8a0`2c0c8010 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0fddc3b0 fffff880`05a01ecc : fffff8a0`00000000 fffff8a0`00000000 fffff8a0`4b677844 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0fddc480 fffff880`0651eccc : 00000000`00000000 fffff8a0`20da9000 fffff8a0`20da9000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0fddc4b0 fffff880`065318b8 : 00000000`00000001 fffff8a0`20da9000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE:estroyAllocations+0x248
fffff880`0fddc5a0 fffff880`06516815 : 00000000`fffffeda fffff8a0`1b2c3860 fffff8a0`20da9000 fffffa80`1ccf1000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0fddc610 fffff880`06554fee : 00000000`00000001 fffffa80`1ccf1000 fffff8a0`1b2c3860 fffff8a0`1b2c38e0 : dxgkrnl!DXGADAPTER:estroyDevice+0x1c9
fffff880`0fddc640 fffff880`06554984 : fffff900`c3146cd0 00000000`00000000 00000000`00000001 fffff900`c3146cd0 : dxgkrnl!DXGPROCESS:estroy+0xba
fffff880`0fddc6f0 fffff960`000e7900 : 00000000`000024e8 fffff900`c3146cd0 00000000`00000000 fffff900`c3146cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0fddc780 fffff960`000e7003 : fffffa80`1c889500 fffff880`0fddcae0 00000000`00000000 fffff880`0fddcae0 : win32k!GdiProcessCallout+0x244
fffff880`0fddc800 fffff800`0379bf83 : fffffa80`1c8895d0 00000000`00000000 00000000`00000000 fffffa80`22951060 : win32k!W32pProcessCallout+0x6b
fffff880`0fddc830 fffff800`0378140d : fffffa80`00000001 00000000`00000001 fffffa80`78457300 fffffa80`1dd86b50 : nt!PspExitThread+0x563
fffff880`0fddc8f0 fffff800`034bd454 : 00000000`00000000 00000000`00000001 fffffa80`22951060 fffff800`034cdc0d : nt!PsExitSpecialApc+0x1d
fffff880`0fddc920 fffff800`034bd7a0 : 00000000`000035c4 fffff880`0fddc9a0 fffff800`03781380 00000000`00000001 : nt!KiDeliverApc+0x2e4
fffff880`0fddc9a0 fffff800`034c8fb7 : fffffa80`22951060 00000000`000035c4 00000000`00000000 fffffa80`27889380 : nt!KiInitiateUserApc+0x70
fffff880`0fddcae0 00000000`74882e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0b84ed28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74882e09


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`05a3562e 488b0e mov rcx,qword ptr [rsi]

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13

IMAGE_VERSION: 6.1.7601.18126

FAILURE_BUCKET_ID: X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID: X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_41790_dxgmms1!vidmm_process_heap::free+a2

FAILURE_ID_HASH: {be43f1a4-3662-07ec-1c74-3b363fd9d97d}

Followup: MachineOwner
---------
My System SpecsSystem Spec
.

21 Apr 2016   #4
sphenic

Windows 7 Professional X64
 
 

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80108873f0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: WmiPrvSE.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff800034e5720 to fffff80003473c80

STACK_TEXT:
fffff880`133cd6e8 fffff800`034e5720 : 00000000`0000001a 00000000`00041790 fffffa80`108873f0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`133cd6f0 fffff800`034a7919 : 00000000`00000000 00000000`04d58fff ffffa3c3`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x33964
fffff880`133cd8b0 fffff800`0378afd1 : fffffa80`1da7e160 00000000`00000000 fffffa80`1e9aace0 fffffa80`1e9aace0 : nt!MiRemoveMappedView+0xd9
fffff880`133cd9d0 fffff800`0378b3df : 0000007f`00000000 00000000`04a50000 fffffa80`00000001 00000000`0098d901 : nt!MiUnmapViewOfSection+0x1b1
fffff880`133cda90 fffff800`03472f13 : 00000000`00000000 00000000`7779826b fffffa80`21c8c060 00000000`00990000 : nt!NtUnmapViewOfSection+0x5f
fffff880`133cdae0 00000000`776cc0ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0098de68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776cc0ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+33964
fffff800`034e5720 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33964

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5507a63e

IMAGE_VERSION: 6.1.7601.23002

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33964

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33964

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+33964

FAILURE_ID_HASH: {89dab576-991e-3957-26f8-0d54f026da3a}

Followup: MachineOwner
---------
My System SpecsSystem Spec
21 Apr 2016   #5
axe0

Windows 10 Pro
 
 

If those dumps are not included in the attached zip file, please run the DM Log Collector again.
According to the logs there hasn't been a crash in a few months.
My System SpecsSystem Spec
22 Apr 2016   #6
sphenic

Windows 7 Professional X64
 
 

That is correct axe0.

The computer has not been used for months now due to company reductions, so the user simply started using another workstation.

Thanks to everyone who wrote the detailed guides on how to troubleshoot. I managed to enable driver verifier, and pinpointed the cause of the issue. Its now being sorted.
My System SpecsSystem Spec
22 Apr 2016   #7
sphenic

Windows 7 Professional X64
 
 

Code:
BugCheck 1A, {5003, fffff781c0000000, 82c, 82e40001058}

*** ERROR: Module load completed but symbols could not be loaded for Parity.sys
Probably caused by : Parity.sys ( Parity+f25dc )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 000000000000082c
Arg4: 0000082e40001058

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


BUGCHECK_STR:  0x1a_5003

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  cb.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

TRAP_FRAME:  fffff8800cbccb30 -- (.trap 0xfffff8800cbccb30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9800ec48f80 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff98002332ec8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800153d5dc rsp=fffff8800cbcccc0 rbp=fffff8800cbcd950
 r8=0000000000000002  r9=fffff98002332ec8 r10=fffff80003449000
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Parity+0xf25dc:
fffff880`0153d5dc 0fb700          movzx   eax,word ptr [rax] ds:fffff980`0ec48f80=002a
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000351f659 to fffff800034bbc80

STACK_TEXT:  
fffff880`0cbcc7d8 fffff800`0351f659 : 00000000`0000001a 00000000`00005003 fffff781`c0000000 00000000`0000082c : nt!KeBugCheckEx
fffff880`0cbcc7e0 fffff800`034ed436 : 00000007`e1d0b963 fffff6fc`c0076240 fffffa80`17a57210 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x21b54
fffff880`0cbcc830 fffff800`034d9c8f : 00000000`00000000 38100007`e1d0b8c2 7ff00000`00000000 fffff800`036fa600 : nt!MiResolveTransitionFault+0x406
fffff880`0cbcc8c0 fffff800`034c99bb : 00000000`00000000 0000007f`fffffff8 fffff6fc`c0413050 fffff800`034d9c8f : nt!MiDispatchFault+0x95f
fffff880`0cbcc9d0 fffff800`034b9dae : 00000000`00000000 fffff980`0ec48f80 fffff880`0cbccb00 00000000`00000000 : nt!MmAccessFault+0xe1b
fffff880`0cbccb30 fffff880`0153d5dc : 00000000`00000011 fffff980`8262eca0 00000000`006e006c 00000000`045341d0 : nt!KiPageFault+0x16e
fffff880`0cbcccc0 fffff880`0153d7aa : fffff980`8260afe8 fffff980`02332ec8 fffff980`00000002 fffff880`0cbcce30 : Parity+0xf25dc
fffff880`0cbccd50 fffff880`0151b98c : fffff980`8260afe8 fffff980`02332ec8 fffff880`00000002 fffff880`015a9aa0 : Parity+0xf27aa
fffff880`0cbccd80 fffff880`015180d8 : fffff980`02332ec8 fffff980`8260afe8 00000000`00000000 fffff880`01518b47 : Parity+0xd098c
fffff880`0cbccdb0 fffff880`01518b6c : fffff980`8260afe0 fffff980`8262eca0 fffff980`02332e10 fffff980`02332ec8 : Parity+0xcd0d8
fffff880`0cbccdf0 fffff880`01518780 : fffff980`8262eca0 fffff980`02332e10 fffff980`02332e10 00000000`00000000 : Parity+0xcdb6c
fffff880`0cbcce50 fffff880`0151883b : fffff980`8262eca0 fffff980`02332e10 fffff880`015a6478 fffff880`0156be40 : Parity+0xcd780
fffff880`0cbccee0 fffff880`014afca9 : fffff980`8262eca0 fffff980`02332e10 fffff980`02332fc8 00000001`0144c501 : Parity+0xcd83b
fffff880`0cbccf20 fffff880`0151894c : fffff980`0e960f88 fffff880`015187f0 fffff980`02332e10 00000000`00000002 : Parity+0x64ca9
fffff880`0cbccf60 fffff880`01526407 : fffff980`0e960f70 fffff980`02332e10 fffff880`0cbcd078 fffff880`01450501 : Parity+0xcd94c
fffff880`0cbccfb0 fffff880`0151104a : fffff880`015a58e8 fffff980`02332e10 fffff980`00000001 fffff880`00000a5c : Parity+0xdb407
fffff880`0cbcd150 fffff880`0150f95a : fffff880`00000000 fffff880`00000001 fffff880`0cbcd230 00000000`00000000 : Parity+0xc604a
fffff880`0cbcd1e0 fffff880`0150f5a1 : fffff880`015a4b98 fffff880`0cbcd570 fffff8a0`00000040 fffff8a0`07cb2610 : Parity+0xc495a
fffff880`0cbcd2a0 fffff800`0386a9b0 : fffff880`015a4b98 00000000`0000001a fffff880`0cbcd570 00000000`000007ff : Parity+0xc45a1
fffff880`0cbcd310 fffff800`0371c12d : 00000000`0000001a fffff880`0cbcd570 00000000`00000001 00000000`0000001b : nt!CmpCallCallBacks+0x1c0
fffff880`0cbcd3e0 fffff800`037b4b6e : 00000000`00000040 fffff8a0`00000000 fffffa80`1f687010 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x4391d
fffff880`0cbcd6e0 fffff800`037b5656 : 00000000`00000044 fffff880`0cbcd860 78900000`00000040 fffffa80`19eac3b0 : nt!ObpLookupObjectName+0x784
fffff880`0cbcd7e0 fffff800`0376b604 : fffff880`0cbcda88 00000000`00000000 fffff880`0cbcd901 fffff800`034b9ebd : nt!ObOpenObjectByName+0x306
fffff880`0cbcd8b0 fffff800`0376bea2 : 00000000`01c4d9c8 fffff880`0003001f 00000000`01c4d9e8 fffff800`0376be74 : nt!CmCreateKey+0x2e1
fffff880`0cbcda20 fffff800`034baf13 : fffffa80`1d153b50 00000000`00000007 00000000`01c4d928 00000000`00000000 : nt!NtCreateKey+0x2e
fffff880`0cbcda70 00000000`7718bfea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01c4d978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7718bfea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Parity+f25dc
fffff880`0153d5dc 0fb700          movzx   eax,word ptr [rax]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Parity+f25dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Parity

IMAGE_NAME:  Parity.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  564b19a1

FAILURE_BUCKET_ID:  X64_0x1a_5003_VRF_Parity+f25dc

BUCKET_ID:  X64_0x1a_5003_VRF_Parity+f25dc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_5003_vrf_parity+f25dc

FAILURE_ID_HASH:  {cf0e2eff-b2c5-74ce-af4d-8f847aef8fd5}

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

6: kd> lmvm Parity
start             end                 module name
fffff880`0144b000 fffff880`015ca000   Parity     (no symbols)           
    Loaded symbol image file: Parity.sys
    Image path: \SystemRoot\system32\DRIVERS\Parity.sys
    Image name: Parity.sys
    Timestamp:        Tue Nov 17 13:12:17 2015 (564B19A1)
    CheckSum:         00178BC7
    ImageSize:        0017F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
22 Apr 2016   #8
axe0

Windows 10 Pro
 
 

If you want to post output from dumps, use code tags so it becomes better readable.
Or follow the BSOD Posting Instructions.
My System SpecsSystem Spec
Reply

 Random BSOD crashes. 3D and Video editing machine. plenty of minidumps




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD and Crashes - VFX & Video diting, HD Video Playback, 3D
Hello all, I am looking for some assistance as to what is causing my computer to crash. It doesn't happen insanely often, but the way it crashes makes me think there's a hardware issue going on. I am mostly thinking it's either my CPU or one of my two graphics cards installed, but I'd be more...
BSOD Help and Support
Windows 7 random crashes 0x00000004e and plenty others
Hey my computer has been bsoding quite a lot recently 3 times today and about 50 times in the past 2 months. I have brand new memory in my computer as my previous memory died. My spec's are listed in my profile, Since I ran SF diagnostics and put everything in a zip but i deleted like 40 of the...
BSOD Help and Support
Windows 8- Graphics Performance- Photo Editing/Video Editing
My question narrows down to what would be a better OS to use for Photo Editing and or occasional video editing. The software used for Photo Editing would be Adobe Lightroom 4.0 and Adobe Photoshop. All software versions using latest build- approved system requirements would meet critieria with...
Music, Pictures & Video
BSOD's not saving minidumps, multiple 0x9F crashes
Hi there, I have been getting lots of 9F crashes on a HP DV7 laptop running 64bit Windows 7 Home Premium. Problem is the the minidumps are not being saved! I have set it up to save them (small dumps) and not to automatically restart. I cant debug it without them :mad:. Any ideas why they...
BSOD Help and Support
Random BSOD errors with failed minidumps
Hi I have been getting random bsod errors and even the minidumps are not being created errors are not the same each time sometimes it is IRQL_not_less_or_equal and sometimes it is kernel_data_in_page error please help me in finding the root cause of the problem System Alienware m14x...
BSOD Help and Support
Crashes during sound/video but very random and weird crash, no BSOD
Hi folks I have an odd issue that I have come to the end of my knowledge about and I am stuck to be honest. My fairly new (6 months) PC has a very odd way of crashing on me at completely random times although it does seem to happen more regularly when playing sound or video content (VLC,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 20:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App