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 Crash


  • Please log in to reply
3 replies to this topic

#1 Schuyler

Schuyler

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:46 PM

Posted 26 April 2009 - 10:02 PM

I am getting these BSOD Crashes, this one was random, and simply said to protect you, computer has been shut down. Others consist of ntfs, ks.sys, nv4_disp.dll, IRQL_NOT_LESS_OR_EQUAL, win32k.sys, and PAGE_NOT_…something. Any help would be greatly appreciated. Few Notes:
-installed on new parition, installed nvidia drivers, and problem persisited, driver issues maybe?
-Left 4 Dead crashes either on loading screen or within 5 minutes of playing.
-Call of Duty 4 lasts a little longer, but usually ends in a crash as well
-I have tried multiple nvidia graphics card drivers
-video card IS NOT over heating
-The crash below, I was simply typing a paper in Word, had been for the past 2 hours. Oh, and had south park in Firefox!
-Pinnacle.exe is a controller manager, that was just idleing, why would it cause trouble?
-Specs
-Core 2 Duo E8400 3.16ghz
-EVGA 780i
-EVGA 9800 GT 512mb
-4gb G-Skill ram
--THANKS!--

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!KeContextFromKframes+54
804fdd34 8b4760		  mov	 eax,dword ptr [edi+60h]

TRAP_FRAME:  b34004e4 -- (.trap 0xffffffffb34004e4)
ErrCode = 00000000
eax=00010001 ebx=b34006c8 ecx=00010001 edx=0000ffff esi=0001003f edi=00000000
eip=804fdd34 esp=b3400558 ebp=b34005f0 iopl=0		 nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010246
nt!KeContextFromKframes+0x54:
804fdd34 8b4760		  mov	 eax,dword ptr [edi+60h] ds:0023:00000060=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  pinnacle.exe

EXCEPTION_RECORD:  b34009d8 -- (.exr 0xffffffffb34009d8)
ExceptionAddress: 7c812aeb
   ExceptionCode: c000008f
  ExceptionFlags: 00000001
NumberParameters: 2
   Parameter[0]: deadcafe
   Parameter[1]: deadcafe

LAST_CONTROL_TRANSFER:  from 804fe4f8 to 804fdd34

STACK_TEXT:  
b34005f0 804fe4f8 00000000 00000000 b34006c8 nt!KeContextFromKframes+0x54
b34009b0 805028cf b34009d8 00000000 00000000 nt!KiDispatchException+0x82
b3400d34 80544ef7 0012b364 0012b080 00000000 nt!KiRaiseException+0x175
b3400d50 8054162c 0012b364 0012b080 00000001 nt!NtRaiseException+0x33
b3400d50 7c812aeb 0012b364 0012b080 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012b3b4 00000000 00000000 00000000 00000000 0x7c812aeb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeContextFromKframes+54
804fdd34 8b4760		  mov	 eax,dword ptr [edi+60h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeContextFromKframes+54

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4976fc91

FAILURE_BUCKET_ID:  0x8E_nt!KeContextFromKframes+54

BUCKET_ID:  0x8E_nt!KeContextFromKframes+54

Followup: MachineOwner
---------

Edited by Schuyler, 26 April 2009 - 10:34 PM.


BC AdBot (Login to Remove)

 


#2 Sunharrow

Sunharrow

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Socialist New Jersey
  • Local time:10:46 PM

Posted 26 April 2009 - 11:13 PM

If I read you correctly you are getting random crashes with all kinds of different error codes, correct? This is a strong indicator of bad RAM. In fact, the minidump information you posted has error 0x8E and these are almost always caused by hardware issues, and particularly points to corrupted memory. I suggest testing your memory with Memtest (I did search under the tutorials but I didn't find anything on memtest; perhaps I erred).

1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.

2. Burn ISO to a CD.

3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.

4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

5. If you have errors you have corrupted memory and it needs to be replaced.

6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.

#3 Schuyler

Schuyler
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:46 PM

Posted 26 April 2009 - 11:34 PM

Alrighty, Someone else actually just told me that. Hopefully it's the ram lol, got a lifetime warranty!

#4 Sunharrow

Sunharrow

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Socialist New Jersey
  • Local time:10:46 PM

Posted 27 April 2009 - 12:07 AM

The good thing about RAM is that it is one of the easiest hardware issues to deal with because it takes all of 30 seconds or so to pop the old stick out and replace it with a new one. Let us know of the results after you run memtest.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users