Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD again tt


  • Please log in to reply

#121
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
BSOD again omg!


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 8/17/2012 5:47:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-15625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80092FDB30, 0xFFFFFA80092FDE10, 0xFFFFF80002FCC510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.


On Fri 8/17/2012 5:47:31 AM 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: 0xF4 (0x3, 0xFFFFFA80092FDB30, 0xFFFFFA80092FDE10, 0xFFFFF80002FCC510)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.


On Fri 8/17/2012 12:34:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081612-16437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80090DA060, 0xFFFFFA80090DA340, 0xFFFFF80002DE6510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
  • 0

Advertisements


#122
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
i found this page has the same issue i just dont understand wat peak voltage means :s

http://www.sevenforu...ile-gaming.html
  • 0

#123
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Peak voltage would mean that the PSU is either not powering enough or is over powering. In either case it would indicate a faulty PSU.
I did see they tested the graphics card using

Furmark, Video Card Stability Test and 3DMark 11 to stress my GPU

.
We could try that and see if it will cause the BSOD again.
Furmark

3DMark 11 Basic Edition Free Download

Try each test and report back with the findings. :thumbsup:
  • 0

#124
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
Here with 3D MArk 11

3DMark ScoreP2707
Graphics Score2420
Physics Score7384
Combined Score2553
Graphics Test1 11.63 FPS
Graphics Test2 11.48 FPS
Graphics Test3 14.61 FPS
Graphics Test4 7.22 FPS
Physics Test 23.44 FPS
Combined Test 11.88 FPS

PC HEALTH CHECK
Your PC is performing properly.
  • 0

#125
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
im scared of using the other program
  • 0

#126
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Ok did the system run correctly during the 3D Mark test? :confused:
  • 0

#127
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

im scared of using the other program

Why it is going to test everything and you should be able to see what is actually causing the BSOD's then.
  • 0

#128
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
wich option do i use furmark-1.10.0-main-interface.jpg
  • 0

#129
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Use the default because that is what we as technicians would do with a new build to stress test the system for a couple of hours. :thumbsup:
  • 0

#130
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
Ok i did the burn-in test and BSOD at 34 36 mins with the temp in 96c
  • 0

Advertisements


#131
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yeah I am 99.9% sure your issue is heat. If you don't feel comfortable opening the case and working on it I would say at this point take it to a shop and have them check that fan inside.
  • 0

#132
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
hmmmm ok ill see wat i can do and get back to u
  • 0

#133
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yeah that heat is way to high in my opinion. :thumbsup:
Something is stopping your air flow.
  • 0

#134
Joshua.Locke

Joshua.Locke

    Member

  • Topic Starter
  • Member
  • PipPip
  • 95 posts
i opened the case and i still got the bsod at 67c :(
  • 0

#135
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Better on the temps but still not making sense especially with the stress test on the graphics not causing it to error.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP