BlueScreen Crash! Please Help

Toggle sidebar Toggle sidebar
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680
so i was using my computer today and it crashed with bluescreen with this error

Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a

Please help as i just built this computer and used all my money. It doesnt happen all the time but it just happened for the first time.
 
Sort by date Sort by votes
nubbsauce

nubbsauce

Reputable
Jun 6, 2014
238
0
4,760


1033s are nice!

Anyways, Was there any BCP: codes after the BCCode? That will help determine the cause. But as of right now, it could be a memory issue, to a corruption with the OS installation.

There are plenty of Process of Eliminations I can give you, but one of the most common issues for BSOD is Memory.

But before I can assist, I need you to answer my questions! :)

 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


no is that what i need next time?
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


It happened again and heres the whole log

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: a
BCP1: FFFFF88042F698C0
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002E9C36F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\060814-18423-01.dmp
C:\Users\Bryce\AppData\Local\Temp\WER-37799-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt



what do you mean 1033's are nice? is that good or bad? I have used all my money on this computer
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


It happened again and heres the whole log

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: a
BCP1: FFFFF88042F698C0
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002E9C36F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\060814-18423-01.dmp
C:\Users\Bryce\AppData\Local\Temp\WER-37799-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
Upvote 0 Downvote
jkhoward

jkhoward

Distinguished
Nov 24, 2011
1,243
27
19,990
Can you download BlueScreenViewer and locate the minidump file and upload that information?

This is the information that you get when logging back into Windows. I would need the information that is displayed at the blue screen when you return to your computer. You computer may be set to automatically restart. You are going to want to disable that if you are not comfortable using BlueScreenViewer. It can be complicated. If you right-click on my computer and select Properties and then Advanced System Settings you will need to click on Startup and Recovery Settings. From there un-check automatically restart and make sure that the debugging information is set to Small Memory Dump.

I am looking for this..

http://www.maximumpc.com/files/u69/BSOD_Main.png

See where it says gv3.sys?

That is what I need. Generally most BSOD are related to driver issues. It would display the driver there, we can figure out which driver that is, and then update it, and it should resolve the problem.
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


I have whocrashed, will this work instread of bluescreenviewer?. Here is my most recent crash log from whocrashed.


On Fri 6/20/2014 4:58:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062014-26364-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x57F8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


ok i will go ahead and do that but before i looked at this i got another crash. Is it the same thing with my network drivers? amd do you mean network drivers on my mother board? So go on my brand of motherboard and download their network drivers? **edit** I have looked but im not to sure which one to download. My motherboard is the asrock 970 pro3 R.2


On Fri 6/20/2014 7:59:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062014-20311-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80002E2E7D0)
Bugcheck code: 0x50 (0xFFFFF80003E49598, 0x0, 0xFFFFF80002E2E7D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


I dont know if you saw but i updated my last post above. But anyways how would i update my drivers on my asrock 970 pro3 R.2. I looked but there are so many different drivers. Maybe a link if you could
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


Happened again in mid twitch stream and when i rebooted it happened right again! here are my last two logs. I hope we can fix this as i have no money to repair


On Sun 6/22/2014 5:07:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062214-20732-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 6/22/2014 5:07:56 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
jkhoward

jkhoward

Distinguished
Nov 24, 2011
1,243
27
19,990
I can't tell you exactly which driver/software is causing the issue at this point. I am not to keen on reading this dump files unfortunately. These errors are indicating that something in software is throwing an error, not hardware. The easiest way to fix the issue would be to re-install Windows. If that is not an option I would first download http://www.superantispyware.com/ and run a full virus scan. If there are any infections on your computer you are going to want to remove them as soon as possible. Once this is completed I would open a command prompt windows as an administrator and type in SFC /SCANNOW this command will check your OS for any issues and attempt to repair them. If this does not fix the issue you can keep posting the blue screens, hopefully they will actually show a faulty driver, or re-install Windows.

Sorry I couldn't be of more help. Good luck!
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


Its ok but i think i know why you cant find the problem. I just relized that every crash i get i get two logs so i guess two things are failing. these are the two logs and as u can see i got them on the same exact date on the same crash.


On Mon 6/23/2014 9:50:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062314-20170-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF80002E8478A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating 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 Mon 6/23/2014 9:50:21 PM 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, 0x406F8, 0xFFFFF80002E8478A)
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.
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


To continue the last post i downloaded superantispyware and got rid of 211 cookies. I do not know if this will help or not. I ran the sfc /scannow and it ended up saying windows resource protection did not find any integrity violations. Do you think anything has changed? or should i just go ahead and reinstall the OS?
 
Upvote 0 Downvote
jkhoward

jkhoward

Distinguished
Nov 24, 2011
1,243
27
19,990
Well your OS appears to be installed properly and there were no viruses detected. Nothing changed but the SFC doesn't always detect issue unrelated to the OS. I would download all of the latest drivers from the mobo website and save it to a USB if you plan on re-installing Windows.
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


Ya i went ahead and reinstalled windows as well as everything else. I hope this fixes it as i have lost all of my information
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


OMG! Im devastated! it happened again! I lost everything and it didnt work. What could this be? overheating? I did a memtest86 but only did one pass because i read that that should be fine.

Here is are my logs.



On Wed 6/25/2014 10:46:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062514-35115-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program 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.
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 6/25/2014 10:46:15 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
S

smallzZz8

Honorable
Sep 6, 2013
114
0
10,680


to add to my last post i ran a sfc /scannow and it says windows resource protection found corrupt files but was unable to fix some of them. details are included in the cbs.log at bla bla bla


but when i go to the location for the log and i try and open it it says access denied? The account i am on is an administrator as well?

##EDIT##
I found out how to get the cbs file and here is the log. Its too long for paste bin so i had to use another website :p http://tny.cz/7b4423a9
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom