Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #1
There was no blue screen(physically),but the CPU screen turned black.......suddenly,after, it went to the thing where it said(something like this....i forgot)
choose
Safe Mode
Normal
___________________
Anyway, I got this error after.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\073113-23821-01.dmp
C:\Users\kee lee\AppData\Local\Temp\WER-86611-0.sysdata.xml
______________________________________________
Thanks for solving it after.
choose
Safe Mode
Normal
___________________
Anyway, I got this error after.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\073113-23821-01.dmp
C:\Users\kee lee\AppData\Local\Temp\WER-86611-0.sysdata.xml
______________________________________________
Thanks for solving it after.
Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #2
- Joined
- Aug 27, 2008
- Messages
- 5,039
Not sure what you mean by CPU screen. Has the problem repeated/return? Try running sfc /scannow in a command prompt.
http://support.microsoft.com/kb/929833
http://support.microsoft.com/kb/929833
Vir Gnarus
Active Member
- Joined
- Jan 8, 2013
- Messages
- 199
Sounds like your system did an automatic restart but was too quick to show up the BSOD. The bugcheck output in the error message is insufficient, and I think the crashdump won't help us either.
As Bassfisher asked, has this been recurring? If it's just a single instance, just write it off as a fluke and forget about it. If you're still concerned, you can do an overnight Memtest followed by checking SMART data on your drive with CrystalDiskInfo. If nothing shows up warning or error on either, then you're ok for now.
As Bassfisher asked, has this been recurring? If it's just a single instance, just write it off as a fluke and forget about it. If you're still concerned, you can do an overnight Memtest followed by checking SMART data on your drive with CrystalDiskInfo. If nothing shows up warning or error on either, then you're ok for now.
Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #5
Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #6
It has been happening 2 times yesterday.Sounds like your system did an automatic restart but was too quick to show up the BSOD. The bugcheck output in the error message is insufficient, and I think the crashdump won't help us either.
As Bassfisher asked, has this been recurring? If it's just a single instance, just write it off as a fluke and forget about it. If you're still concerned, you can do an overnight Memtest followed by checking SMART data on your drive with CrystalDiskInfo. If nothing shows up warning or error on either, then you're ok for now.
Vir Gnarus
Active Member
- Joined
- Jan 8, 2013
- Messages
- 199
I recommend doing the aforementioned hardware checks just-in-case. In addition, turn on Link Removed and restart system, then let it crash the system and then send us resulting crashdumps. If it causes a restart loop, go into Safe Mode by tapping F8 before Windows logo appears, then go back into DV and disable it by selecting, "Disable existing settings" and click Finish, then restart into normal Windows.
Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #8
Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #9
It looks like it happened today/.....
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
It's the same thing.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
It's the same thing.
Vir Gnarus
Active Member
- Joined
- Jan 8, 2013
- Messages
- 199
Meleotta3
Member
- Joined
- Jul 31, 2013
- Messages
- 13
- Thread Author
- #11
Now I got a actual Blue-colored screen
and the crash dump was diffrent
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002E74B05
BCP3: FFFFF8800657EAA0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\080613-21465-01.dmp
C:\Users\kee lee\AppData\Local\Temp\WER-85160-0.sysdata.xml
and the crash dump was diffrent
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002E74B05
BCP3: FFFFF8800657EAA0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\080613-21465-01.dmp
C:\Users\kee lee\AppData\Local\Temp\WER-85160-0.sysdata.xml
Similar threads
- Replies
- 2
- Views
- 5K
- Replies
- 3
- Views
- 9K
- Replies
- 5
- Views
- 4K
- Replies
- 2
- Views
- 954