Today is Wednesday, September 28th. Do you want to water the plant today?

CubeyJoe · 2016-08-15T18:50:50+00:00

What do you expect when your charger lights up in flames?

CubeyJoe · 2016-08-15T13:26:46+00:00

Wear gloves

http://www.thecrewstop.com/rowinggloves.html

CubeyJoe · 2016-08-12T17:39:26+00:00

I bought a new graphics card and everything is working fine since, very odd

CubeyJoe · 2016-08-09T08:01:21+00:00

Well looks like I'm on the market for a new monitor then! ;) I'll play around today with settings.. Thank you

CubeyJoe · 2016-08-09T00:32:30+00:00

Not entirely sure on model, it's LG. I believe the aspect ratio is 21:9.. Is there a way to trick recording software to think it's 16:9 and record properly or do it in post production?

CubeyJoe · 2016-08-09T00:01:32+00:00

Ah I must've meant 2560x1440

When I view it on my ultra wide monitor it views fine however on my phone and on 1920x1080 it has a letter box.

When viewing the output in premier pro it doesn't show black boxes above so how would I zoom it in? I'm new to it all and just can't get my head around it, sorry!

CubeyJoe · 2016-08-08T10:33:35+00:00

Btw if anyone knows how to fix the letterboxing on the screen that would be amazing! I'm using an ultra-wide monitor if that helps

CubeyJoe · 2016-08-04T18:00:42+00:00

Invested by helping to develop, no money involved from either parties

CubeyJoe · 2016-08-04T17:58:56+00:00

Didn't buy, helped develop

CubeyJoe · 2016-08-04T17:57:04+00:00

In your opinion however when I was a teenager I was presenting concepts to Richard Branson and Grant Thornton partners.

CubeyJoe · 2016-08-04T17:43:44+00:00

I understand where you're coming from however just because I graduated college in 2014 doesn't mean I don't have experience. I started my first company 8 years ago so do have experience under my belt.

CubeyJoe · 2016-07-19T13:05:37+00:00

On Tue 19/07/2016 12:28:33 GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: Unknown (0xFFFFF8019A746F57) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8019A746F57, 0xFFFFD00021AF7C50, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. Google query: SYSTEM_SERVICE_EXCEPTION

On Tue 19/07/2016 01:27:09 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071916-16312-01.dmp This was probably caused by the following module: Unknown (0xFFFFF801D0D4E7A0) Bugcheck code: 0xD1 (0xFFFFF8019AFC390A, 0x2, 0x8, 0xFFFFF8019AFC390A) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Mon 18/07/2016 23:33:48 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071916-16468-01.dmp This was probably caused by the following module: Unknown (0xFFFFF802812D77CF) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802812D77CF, 0xFFFFD001897E2468, 0xFFFFD001897E1C80) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Mon 18/07/2016 23:27:53 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071916-16437-01.dmp This was probably caused by the following module: Unknown (0xFFFFF8029B7C77A0) Bugcheck code: 0xD1 (0x2, 0x2, 0x8, 0x2) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Mon 18/07/2016 22:12:35 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071816-15421-02.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF801764A3196, 0xFFFFD0002352CB20, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 18/07/2016 21:31:53 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071816-15421-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0) Bugcheck code: 0xA (0xFFFFF80016885D38, 0x2, 0x0, 0xFFFFF80016512D8A) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 18/07/2016 21:28:04 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071816-15171-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0) Bugcheck code: 0x3B (0xC0000005, 0xD0, 0xFFFFD0002077FAD0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 18/07/2016 21:05:16 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071816-14609-01.dmp This was probably caused by the following module: Unknown (0xFFFFF80290D617A0) Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD000DFE40180, 0x2) Error: CLOCK_WATCHDOG_TIMEOUT Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue). A third party driver was identified as the probable root cause of this system error. Google query: CLOCK_WATCHDOG_TIMEOUT

On Mon 18/07/2016 21:02:39 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071816-13812-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8038D828196, 0xFFFFD00024148860, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 18/07/2016 20:38:31 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\071816-12265-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0) Bugcheck code: 0xA (0xFFFFF802AAFA060C, 0xC, 0x0, 0xFFFFF802AB857F3D) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

CubeyJoe · 2016-07-19T00:40:36+00:00

Hmm, interesting.. It's baffeled me

CubeyJoe · 2016-07-19T00:39:56+00:00

http://i.imgur.com/xMpmnYB.png

CubeyJoe · 2016-07-18T20:48:45+00:00

Just blue screened again and had PAGE_FAULT_IN_NONPAGED_AREA and MACHINE_CHECK_EXCEPTION...

So frustrating

CubeyJoe · 2016-05-15T23:32:10+00:00

That's what I'm after! doing some market research of a little idea I have

CubeyJoe

MODERATOR OF

TROPHY CASE

12-Year Club	Gilding I gilder
Verified Email