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

All kinds of BSODs on vista 64


  • Please log in to reply

#1
Kolaholisti

Kolaholisti

    Member

  • Member
  • PipPip
  • 15 posts
Hello there!

So lately I have been getting alot of blue screens, mostly during booting or slightly after. I have formated my whole hard drive not so long ago (3 days to be exact..). I realized I should download the program (BlueScreenView) to identify the crashes properly.
So here it is:

==================================================
Dump File : Mini120511-03.dmp
Crash Time : 5.12.2011 23:32:48
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff800`0207bb1f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+55410
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+55410
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120511-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
Dump File Size : 270 904
==================================================

==================================================
Dump File : Mini120511-02.dmp
Crash Time : 5.12.2011 19:57:53
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa00`01d6e000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`020aa099
Caused By Driver : dfsc.sys
Caused By Address : dfsc.sys+2d5e2378
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+55410
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120511-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
Dump File Size : 267 704
==================================================

==================================================
Dump File : Mini120511-01.dmp
Crash Time : 5.12.2011 19:55:16
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffffa60`00e7acea
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+6dcea
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+55410
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120511-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
Dump File Size : 270 904
==================================================

==================================================
Dump File : Mini120311-02.dmp
Crash Time : 3.12.2011 22:22:13
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa60`060442c0
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`020752fd
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+55410
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+55410
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120311-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
Dump File Size : 270 904
==================================================

==================================================
Dump File : Mini120311-01.dmp
Crash Time : 3.12.2011 10:15:01
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa5f`852ef5c8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`01b005da
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+55390
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+55390
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120311-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
Dump File Size : 266 832
==================================================


Any help is greatly appreciated! :)
  • 0

Advertisements


#2
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
have you run chkdsk /r yet...if not do so first...
have you run memtest86 yet...if not do so after chkdsk /r
  • 0

#3
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
Hello,

after running chkdsk /r I haven't encoutered a blue screen. Guess it's some program / driver corrupting a Windows file. I will try to find out what is causing it.
  • 0

#4
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts

Guess it's some program / driver corrupting a Windows file. I will try to find out what is causing it.

it was probably just a bad sector or 3



when formatting a drive for a re-installation of the OS...never use the quick format option...
I highly recommend you backup all your data now...

if you start having BSOD again and chkdsk /r fixes it....it usually means the hard drive is going to fail soon
at that point you will want to buy a larger HD and then clone the old drive onto the new drive
  • 0

#5
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
Hello again,

you were absolutely right. The computer hardly boots today. It gets stuck when it should load Windows and reboots or gets stuck when it tries to "find" the HD (right after motherboards message). Also I got a BSOD earlier too. Good thing I backupped my datas, thanks alot for the tip. Gonna try and find another hard drive from some of my older computers :)

Thanks alot for your help happyrock :)
  • 0

#6
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
your welcome...and thanks for letting us know... :thumbsup:
  • 0

#7
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
Hmm now this is strange.. I took a hard drive from my older computer and booted with it. Well it worked but after a few minutes on desktop the whole system locked up. So couldn't move cursor, use CTRL+Alt+Delete etc. Now after this it happened quite several times and this also happened once before with the new hard drive. I really am lost right now, unable to figure out which part(s) is broken or not. Could all these be caused by a faulty RAM? BSODs, system lockouts, being unable to boot..?

I would be very grateful if you'd continue to help me with this problem as I really wouldn't like to take my PC to a overhaul. :)

Edited by Kolaholisti, 07 December 2011 - 11:17 PM.

  • 0

#8
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
did you test your ram using memtest yet...(post number 2) if not do so now...

is this a fresh install it happening to or did you just plug in a old drive and connect it up
  • 0

#9
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
Can't really test the RAM when system is locking up that fast.

Yes I just plugged the old drive in, of course removing the cables from new one.
  • 0

#10
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
you can't just plug in a drive from a different system...it won't work because the hardware is different...
you can plug it in and then boot from the windows install disk and reinstall the OS to the drive...
use the full format option because if you use the quick format option you may get a bad install if there are any bad sectors and windows writes to it/them...the full format will try to fix any bed sectors and if unable to fix them will mark them as bad so windows will not write to them
  • 0

Advertisements


#11
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
By only plugging the old drive booted and loaded the OS installed on it. Only problem was the screen lockups.

Guess I did a quick format on my new hard drive then. How do I do a full format? And should I do this to the new or old drive?
  • 0

#12
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
if you can boot from the cd drive to load a OS then use another computer to make the memtest disk and boot from that and test your ram
  • 0

#13
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
Tried to reproduce the freezing today by switching the RAM sticks back and forth.
At beginning I had my two sticks in slots 1 and 3. Computer froze pretty fast in BIOS. Rebooted, got into desktop and crashed right after that. Got stuck at BIOS screen.

So it went like this:

Stick 1 - Slot 1
Stick 2 - Slot 3
= Crash and freeze almost instantly. Another freeze when rebooting.

Stick 1 - Slot 1
= Worked flawlessy for 20 minutes without freezes/crash.

Stick 2 - Slot 1
= Worked flawlessy for 20 minutes without freezes/crash.

Stick 1 - Slot 3
Stick 2 - Slot 1
= Worked flawlessy for 20 minutes without freezes/crash.

Stick 1 - Slot 1
Stick 2 - Slot 3
= Same as first setup, this time working with no freezes or crashes

I don't really know.. maybe it was just coincidence that it didn't work when I first tried.. I will run the Memtest tomorrow and get back to you.
  • 0

#14
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
if you get no more freezing then one of the sticks wasn't making good contact...
another hang run memtest and if there are any errors then that stick is bad and MUST be replaced...
start the test with both sticks installed and run the test for 2 hours...
any error try running 1 stick at a time until you find the problem stick...throw it away and replace with a exact match for the remaining stick
  • 0

#15
Kolaholisti

Kolaholisti

    Member

  • Topic Starter
  • Member
  • PipPip
  • 15 posts
Ran it for 2 hours - got zero errors. Guess it wass bad contact with the RAM. Now the freezings seem to be gone but I still get occasional blue screens.
  • 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