Nesagsar

https://techcrunch.com/2018/05/24/uber-in-fatal-crash-detected-pedestrian-but-had-emergency-braking-disabled/

My Nvidia driver is currently on 388.59, I should probably update some time.

I'm getting very frequent BSOD crashes with no known cause. Crash dumps below. On Thu 4/12/2018 4:54:31 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\041218-13265-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x175930) Bugcheck code: 0xC1 (0xFFFFDB0376AEA9D0, 0xFFFFDB0376AEA51E, 0x9B0628, 0x32) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 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 the driver wrote to an invalid section of the special pool. 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 Thu 4/12/2018 4:54:31 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt+0x175930) Bugcheck code: 0xC1 (0xFFFFDB0376AEA9D0, 0xFFFFDB0376AEA51E, 0x9B0628, 0x32) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Bug check description: This indicates that the driver wrote to an invalid section of the special pool. 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 Wed 4/11/2018 12:52:01 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\041118-13140-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x175930) Bugcheck code: 0xA (0xFFFF800172AFE740, 0x2, 0x1, 0xFFFFF800951D2F38) 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 is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 4/10/2018 8:36:45 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\041018-15281-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x175510) Bugcheck code: 0xA (0xFFFFA48BEDBED740, 0x2, 0x1, 0xFFFFF80272A468B8) 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 is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 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 4/9/2018 4:32:47 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\040918-14578-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x175510) Bugcheck code: 0xA (0xFFFF8F8403F360C0, 0x2, 0x1, 0xFFFFF8033F3BD8B8) 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 is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 4/7/2018 2:08:36 AM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\040718-13031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x175510) Bugcheck code: 0xA (0xFFFFBC0B027170C0, 0x2, 0x1, 0xFFFFF800F44548B8) 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 is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 4/6/2018 5:55:56 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\040618-11984-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x175510) Bugcheck code: 0x4E (0x9A, 0x0, 0x0, 0x0) Error: PFN_LIST_CORRUPT 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 the page frame number (PFN) list is corrupted. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This is why I figured a "Fast as Possible" would work better than a build guide. I dont accomplish the task by recommending specific hardware, what I need is an explanation for why better hardware is necessary. Essentially, run through each of the components and explain why professionals need better components than business users and gamers. Explain why high core counts are better than clock speed when multitasking. Explain why pros need lots of RAM due to RAM enabled preview in linear editors. Explain why RAID is important to data security. Essentially the same thing as the "What is the difference between a PC and a server?" video but for workstations instead.

I certainly agree that graphics shops all have different requirements but I would argue that there are some general items that we can all agree on. Our computers are doing okay on CPU and RAM with Xeons and 32 GB of DDR3. However - they put NVS 510 graphics in there, the HDD isnt in RAID and we have bricked three systems because the HDDs had mechanical failures, and these things are running on 350 watt PSUs. This is not how professionals are supposed to work. I just need some sort of resource that tells what a content creation PC is supposed to be so I can show my leadership how much they are screwing us. We are doing extremely important work and everybody should be concerned that our systems are holding us back.

I'd love to see a video that lays out the requirements for a serious professional content creation PC. My current job is as a designer and graphic artist but our computers and IT infrastructure are nowhere near what we are supposed to have, they have even tried to take away our real PCs and use thin clients. This network cant even transfer a 200 MB file reliably, I'm not going to attempt running After Effects over it. If LMG could make a Fast as Possible or something which lays out what a real professional system looks like compared to a standard business, home, and gaming PC setup it would be really useful in helping us explain why the graphics and media team needs different hardware than people who work in Excel and Word. Threadripper seems like a good starting point for such a video.

I already did that. Only the mouse, keyboard, LAN cable, boot SSD and the install USB are connected. If I wait long enough, around 45-70 minutes, the computer will load into windows from a standard power-on boot, but after logging into the user profile Explorer is completely mad. The windows key does not work, the taskbar is consistently in a loading state, no loaded windows appear in the taskbar, the start menu and cortana are unclickable, application icons on the desktop are white rectangles, the names of drives are reset to just their drive letter, windows applications take abnormally long time to startup, the desktop occasionally flickers to black and closes open windows, restarting explorer from the task manager (which is only accessable from ctrl-alt-del) has no effect at all. Obviously an NVME SSD should not be booting to windows so slowly and explorer should not be behaving so oddly. I originally tried SFC but it returned no problems. I ran DISM but it stalled at 87.2% and crashed 20 min later. I tried an in place upgrade repair installation but the Media Creation Tool froze for an hour and then crashed. If I hard reset I either get a long wait followed by "attempting automatic repairs" and an infinite system hang or I get "press any key to prevent disk checking" which freezes infinitely if I press anything. I also just noticed that there is an :S: drive listed in My Computer which does not exist and Task Manager says it is at 100% disk utilization constantly but the read and write speeds are both zero kilobytes.s

Ny retail copy of Windows 10 will not install to my SSD. I had a working installation on this drive but today it started acting unstable. I attmpted all the normal checks with no solution so I have decided ro just do a clean install onto the disk since my data is stored on other drives. I put in the original retail win10 USB and set my bios ro load it up but when I get passed the "choose language: screen it hangs on "setup starting" for over an hour.

I have added a new news source to the initial post. I honestly dont know enough about Canadian journalism to evaluate these sources so I would appreciate if anyone with better context could help with that.

I have no idea how to do that - we should all be lucky that I figured out how to use the quotes function at all. I miss BBcode.

Having worked at HHS I can definitively state that if any of the pharma companies know how to fix it they haven't informed CDC or NIH yet.

Ok, I grant that but what if we used the processing power of their systems to solve cancer? Or to run traces on the people who threaten transpeople.

A Canadian cartoonist has been targeted by anti-LGBT cyberterrorists in an attack which resulted in thousands of death threats, placed her personal information online, threatened the launch of her newest book at a Halifax bookstore, and replaced her website with Nazi imagery. The attack has reportedly caused the cartoonist to "go into hiding". The attack appears to have been coordinated and service providers / law enforcement are involved. Along with threats against the cartoonist other threats were made against the book store hosting the launch event of her book. Original Article: http://www.metronews.ca/news/halifax/2017/05/18/trans-cartoonist-forced-cancel-book-launch-halifax.html Second Source: http://www.gaystarnews.com/article/trans-cartoonists-website-hacked-replaced-nazi-imagery-alt-righ t-trolls/ Secondary Source: http://www.cbc.ca/news/canada/nova-scotia/transgender-cartoonist-sophie-labelle-hate-death-threats-book-launch-1.4123683

Good news is that I was able to verify all of my data is good. I was only able to afford an exterior drive dock so I still dont know if any PC components are bad.

Did that help?