Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD HELP!!!


  • Please log in to reply
11 replies to this topic

#1 Blaze413

Blaze413

  • Members
  • 330 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:19 AM

Posted 22 December 2010 - 03:53 PM

ok so ive randomly all of a sudden been experiencing BSOD crashes when playing games suck as black ops and sometimes when not doing anything at all.....i downloaded the program WhoCrashed? and it tells me stuff but have no clue how to fix it, after melting my brain with pages upon pages of google i have high hopes that the good techies at bleeping can help me!! here is what the WhoCrashed says:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 12/22/2010 8:09:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122210-25187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
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 which cannot be identified at this time.


i have tried a spare vid card and it does the same thing so i know its not a vid card and ive done memtest on all 4 sticks of ram individually...they are fine, so im just lost as to how to stop the evil blue screen visits

please help!!!!!

thanks!

p.s if u need cpuz images or anything i can provide them i just need to know how to upload images on forum thanks again!

Edited by Blaze413, 22 December 2010 - 03:55 PM.


BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,719 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:12:19 AM

Posted 22 December 2010 - 06:31 PM

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

================================================================

Download System Information for Windows (SIW free version)
No installation required.

After it scans your computer, navigate to Hardware>Sensors and post all info from there.

Posted Image

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 Blaze413

Blaze413
  • Topic Starter

  • Members
  • 330 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:19 AM

Posted 23 December 2010 - 10:11 AM

ok here is the info:

==================================================
Dump File : 122210-25859-01.dmp
Crash Time : 12/22/2010 4:18:49 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+74700
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122210-25859-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122210-25187-01.dmp
Crash Time : 12/22/2010 3:10:55 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70710
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122210-25187-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122210-20031-01.dmp
Crash Time : 12/22/2010 1:53:25 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`0307affb
Parameter 3 : fffff880`0650c658
Parameter 4 : fffff880`0650bec0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+73ffb
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122210-20031-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122210-26984-01.dmp
Crash Time : 12/22/2010 1:27:07 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`030ca391
Parameter 3 : 00000000`0000000d
Parameter 4 : fffffa80`0706cb00
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122210-26984-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122210-21734-01.dmp
Crash Time : 12/22/2010 12:47:13 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`000000d0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030fe9bf
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122210-21734-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122210-20937-01.dmp
Crash Time : 12/22/2010 11:12:21 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff800`0356d054
Parameter 2 : 00000000`00000008
Parameter 3 : fffff800`0356d054
Parameter 4 : 00000000`00000000
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+de905
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122210-20937-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-23234-01.dmp
Crash Time : 12/21/2010 11:04:03 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70710
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-23234-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-28343-01.dmp
Crash Time : 12/21/2010 4:55:55 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+47c63
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-28343-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-32750-01.dmp
Crash Time : 12/21/2010 4:21:36 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+4a56
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-32750-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-43375-01.dmp
Crash Time : 12/21/2010 4:12:28 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000001
Parameter 2 : 00000000`0000000d
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030e03a8
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-43375-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-23687-01.dmp
Crash Time : 12/21/2010 2:59:34 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff980`28e4ed20
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030a798b
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+bc764
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-23687-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-24531-01.dmp
Crash Time : 12/21/2010 2:34:34 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`074d6150
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03095131
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+c4a4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-24531-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-23328-01.dmp
Crash Time : 12/21/2010 1:56:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2593
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-23328-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 122110-29875-01.dmp
Crash Time : 12/21/2010 12:52:13 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff800`02f8e054
Parameter 2 : 00000000`00000008
Parameter 3 : fffff800`02f8e054
Parameter 4 : 00000000`00000000
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+3e32
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122110-29875-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 121410-26406-01.dmp
Crash Time : 12/14/2010 6:59:54 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+4a56
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\121410-26406-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

all temps are fine gpu:58C (4870 they run hot anyway)
system total is only 32C
CPU is 31C
HDD's are 21C and 23C

the only weird thing is that under where is says the cores for thr processor they are all 0C like no registering at all...i noticed this with HWMonitor actually now that i think about it around the same time the crashes stated to happen....does it just mean that the cpu has come out or something?

well thats the info u wanted...thanks for all ure help!

Edited by Blaze413, 23 December 2010 - 10:14 AM.


#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,719 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:12:19 AM

Posted 23 December 2010 - 12:08 PM

the cores for thr processor they are all 0C like no registering at all...i noticed this with HWMonitor actually now that i think about it around the same time the crashes stated to happen

I'm not sure. It looks like SIW was able to read it.

You have a various type of errors, involving various system files.
I'd probably start with testing your RAM.

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#5 Blaze413

Blaze413
  • Topic Starter

  • Members
  • 330 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:19 AM

Posted 23 December 2010 - 12:51 PM

im on a dif pc now but i was already running memtest86 when i got ure reply.....one question though can i just run memtest with all 4 sticks of ram (i have 4x2gb sticks) at once or do i need to run memtest with only 1 in at a time?

i did boot up with each stick just fine though....but thanks for the help and ill keep you posted on memtest results when its done

and as for the temp thing...the weird thing is, is that is told me a total temp, but not for each core like it used to do...just weird but it doesnt bother me as long as i have a overall temp

Edited by Blaze413, 23 December 2010 - 12:54 PM.


#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,719 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:12:19 AM

Posted 23 December 2010 - 12:54 PM

Software testing is not always accurate, especially, when you run it with all sticks installed.
That's why, I said:

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.


My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#7 Blaze413

Blaze413
  • Topic Starter

  • Members
  • 330 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:19 AM

Posted 23 December 2010 - 05:03 PM

lol im lost all the ram tested with no errors at all...any other ideas? u said i had a lot of errors though...what might those be?

#8 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,719 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:12:19 AM

Posted 23 December 2010 - 05:25 PM

I'm not sure, if you understood, what i was saying.
Remove all RAM sticks, but ONE.
Run the computer for a few hours, like you normally do.
From your log, I can see, you're getting some BSOD almost every hour.
If no BSOD, replace stick #1 with a stick #2.
Run computer for a few hours.....and so on.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#9 Blaze413

Blaze413
  • Topic Starter

  • Members
  • 330 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:19 AM

Posted 23 December 2010 - 05:29 PM

no i didnt ....i just thought u were saying run the pc with memtest 1 stick at a time...not just have the pc on but i will try this and leave it up...btw it never bluescreened while under the memtest

#10 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,719 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:12:19 AM

Posted 23 December 2010 - 05:39 PM

i will try this and leave it up

Make sure, you keep it busy.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#11 Blaze413

Blaze413
  • Topic Starter

  • Members
  • 330 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:19 AM

Posted 23 December 2010 - 07:35 PM

fixed it....i feel sooo dumb but it seems all i had to do was load the bios defaults and now it works with no crashes...even the things like playing black ops that made it crash before...but thank you soo much for ure help :)

#12 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,719 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:12:19 AM

Posted 23 December 2010 - 07:50 PM

Wow! Nice fix :)

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users