Please provide the American thread title you would like me to rewrite.

So, for about three days now, things have been getting weird; after I boot up and load Windows, the screen starts looking all "colorful" with these random lines and artifacts, usually right after I open a browser. Then, boom, BSOD. Once I reboot, everything seems fine, which is strange because this has happened twice in the last three days. WhoCrashed says it isn't even generating any crash dump reports, and I'm not seeing any red error flags in the Event Viewer either. One of the errors I did manage to dig up in the Event Viewer looks like this:

- System

- Provider

[ Name] volmgr

- EventID 46

[ Qualifiers] 49156

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-08-12T11:08:56.437200000Z

EventRecordID 5314049

Channel System

Computer lionheart-PC

Security

- EventData

\Device\HarddiskVolume2
HarddiskVolume2 0000000001000000000000002 E0004C004100000080000C000 000000000000000000000000000000

The thing that's tripping me up is that the crash actually happened at roughly 1:09 PM, but the system time in the log says 11:08 AM. I guess maybe there's a sync issue somewhere.

Right when the crash hit, this log was generated:

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-08-12T11:09:32.000000000Z

EventRecordID 5314062

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer lionheart-PC

Security

- EventData

param1 0x00000019 (0x0000000000000003, 0xfffffa8003c5d350, 0xfffffa8003c5d350, 0x0061007400610044)
param2 C:\Windows\MEMORY.DMP
param3 081214-43477-01

just grab WhoCrashed and dump whatever it spits out right here.

placidrider48 said:So, for about three days now, things have been getting weird; after I boot up and load Windows, the screen starts looking all "colorful" with these random lines and artifacts, usually right after I open a browser. Then, boom, BSOD. Once I reboot, everything seems fine, which is strange because this has happened twice in the last three days. WhoCrashed says it isn't even generating any crash dump reports, and I'm not seeing any red error flags in the Event Viewer either. One of the errors I did manage to dig up in the Event Viewer looks like this:

- System

- Provider

[ Name] volmgr

- EventID 46

[ Qualifiers] 49156

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-08-12T11:08:56.437200000Z

EventRecordID 5314049

Channel System

Computer lionheart-PC

Security

- EventData

\Device\HarddiskVolume2
HarddiskVolume2 0000000001000000000000002 E0004C004100000080000C000 000000000000000000000000000000

The thing that's tripping me up is that the crash actually happened at roughly 1:09 PM, but the system time in the log says 11:08 AM. I guess maybe there's a sync issue somewhere.

Right when the crash hit, this log was generated:

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-08-12T11:09:32.000000000Z

EventRecordID 5314062

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer lionheart-PC

Security

- EventData

param1 0x00000019 (0x0000000000000003, 0xfffffa8003c5d350, 0xfffffa8003c5d350, 0x0061007400610044)
param2 C:\Windows\MEMORY.DMP
param3 081214-43477-01

GPU dying on me?

William Richardson12 said:just grab WhoCrashed and dump whatever it spits out right here.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

No valid crash dumps have been found on your computer

I guess I mentioned this in my first post, but the system might be auto-deleting them since your C drive looks pretty much maxed out.

Alright, based on what you told me, let's try tackling this another way. Just follow the steps in this link http://repairerrors.net/0x80000000000000.html...

William Richardson12 said:Alright, based on what you told me, let's try tackling this another way. Just follow the steps in this link http://repairerrors.net/0x80000000000000.html...

I guess you were talking about the automatic or manual option?

Go automatic if you can. Manual is always the last resort...

William Richardson12 said:Go automatic if you can. Manual is always the last resort...

So RegCure wants me to cough up cash just to fix my issues. I honestly figured there wouldn't be much of a problem since I've already got ASC 7, which pretty much does the same thing as RegCure anyway.

It happened again. Now I’ve got these crash dumps:

On Wed 13.8.2014. 12:03:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081314-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000308D001)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows ® Operating system company : Microsoft Corporation description : NT kernel & system
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13.8.2014. 12:03:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000308D001)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Basically, just wipe it and reinstall Windows. Something went sideways in the Windows kernel and it's crashing everything... a clean install is really the only sure way to fix this.

Tried fixing Windows, but I guess it’s a lost cause. Memory tests are pointing toward some hardware headache, though the whole thing just froze up before it could even finish—it wouldn't even respond to F1 or Esc. It isn't the hard drive, though, since I ran a diagnostic from Western Digital on it just a few days ago.