Sign in with
Sign up | Sign in
Your question

Need Help With BlueScreen Error 0X00000101

Last response: in Systems
Share
December 22, 2008 1:17:40 PM

I'm Having Problems with my new rig, BlueScreen Errors appear randomly.
I think the Power supply is the problem, but I haven't got any confirmation that the RAM: Corsair CM2X2048-6400C5 is supported with the Vista Ultimate 64. Windows Problem Reports and Solutions says that the graphic card caused the issues... BUT BUT BUT

Yesterday I got tired of the system Crash So i changed it with my old one, a Nvidia Gforce 8600 gt 256 mb and 2 hours later it crashed Again!!!!!

Here is some information:
*Vista ultimate 64
*Intel Quad Core Q9550 2,83 GHz
*Sapphire Radeon HD 4870 512Mb
*Corsair CM2X2048-6400C5
* Hiper HPU-4M530 530 Watt

Please Help Me, or my rig will be homeless :fou: 
December 22, 2008 1:41:49 PM

The first thing I'd do is download memtest86+ and let it run for 8+ hours to check for RAM errors. A lot of blue screen's are caused by RAM problems. Did you manually set the RAM timings and voltage to the manufacturers specs in the BIOS?
m
0
l
December 22, 2008 2:07:39 PM

I have tried it now, set the BIOS settings from [Auto] to [1,9 V] can it be so Simple? I'm going to run the test... :pt1cable: 
m
0
l
Related resources
December 22, 2008 2:12:53 PM

A lot of time it is that simple :) 
m
0
l
December 22, 2008 2:21:44 PM

I hope So...
m
0
l
December 22, 2008 2:23:20 PM

So the Power Supply is omitted?
m
0
l
December 22, 2008 2:27:30 PM

lilleenga said:
I have tried it now, set the BIOS settings from [Auto] to [1,9 V] can it be so Simple? I'm going to run the test... :pt1cable: 


Yes, it can be that simple. Default settings (auto) are at 1.8v. I run my OCZ ram at 2.1v and it works fine. The Corsair ram should be able to run at 2.1v as well. Generally speaking, the ram doesn't care what OS is being used, but it can be a problem with specific motherboards. You could check with Corsair as to whether or not your ram is certified your motherboard. Even if not, it still might work. Another way to check ram is to try one stick at a time and see if it fails on a particular stick. I had a case years ago with some Corsair ram that was not certified with a particular motherboard and it caused nothing but trouble until I got different ram that was certified for that motherboard.

You didn't say whether or not you are overclocking, but you might also try a slight increase in the voltage to the CPU. A CPU that gets starved for voltage will also crash the computer.
m
0
l
December 22, 2008 3:33:47 PM

I searched and figured out that 1,9 V is the recommended Voltage, Nothing is Overclocked, but should I give the CPU a little more voltage? can't I damage the CPU?!?!
m
0
l
December 22, 2008 3:52:28 PM

BSODs yuk,

If your computer usually boots normally and runs for a while, the BSODs are probably not truly random.

Make sure your OS and your drivers are up to date. Reinstall your video drivers. Google on how to properly remove and cleanly install vga drivers...(and look for ATI hotfixes). Next, set your bios settings to auto and default accept for any specific 64 bit settings. Some boards have them and they are defaulted at 32bit. Next run prime 95 and the ATI Tool video card stability test at the same time. If the problem is with the PSU than your system will crash quickly under the strain. If your system doesn't crash within 5 minutes of testing but crashes later (especially when gaming), your problem is most likely with a driver or heat build up.

Anyway, the point is, start testing components until you can crash the system and that will give you clues that will help you narrow down the problem.

My 2 cents says it's the power supply but the above steps should reveal if I'm correct. If it is the PSU don't skimp on the replacement. EDUCATE YOURSELF on how to choose a good power supply and you will save yourself money and grief.

I hope this helps.

Good luck and Happy Holidays.


m
0
l
December 22, 2008 5:31:17 PM

I'll Try this out, Thanks for every contributions and I hope This would do it :) 
m
0
l
December 22, 2008 6:23:39 PM

lilleenga said:
I searched and figured out that 1,9 V is the recommended Voltage, Nothing is Overclocked, but should I give the CPU a little more voltage? can't I damage the CPU?!?!


First, Hiper makes a fair PSU, though they can go bad, just like anything else. At 530wts, it should have enough power, since you're not overclocking and you don't have a lot of heavy draws on the power. You can also check out PSU quality ratings here: http://www.jonnyguru.com/index.php While the Hiper 530wt is not specifically tested, other Hyper models are.

As to the ram voltage, 1.9v is the factory spec, but occasionally ram will draw more. DDR2 ram can use up to 2.1v without damage. In fact, that's what much of the DDR2-1066 factory ram is, just overclocked DDR2-800 ram that has the voltage raised. A minor raise, about .1v, won't hurt the ram. Same with the CPU, bumping up the voltage can help it run stable, but in this case, you might raise it up to as much as 1.35 volts without any danger. Yes, theoretically it will burn the CPU out a bit faster, but in perspective, that's like dropping its lifespan from 10 years to 8 years. You most likely will not be using the CPU, or almost anything else in the computer, 10 years from now.

Likely as not, you have a bad ram stick, which is why the ram sticks need to be tested. As others have noted, you should make sure the old drivers are completely cleaned off the OS and the latest drivers installed for you video card, etc. There is an off chance that there is a motherboard problem. A great amount of diagnosing problems is trial and error. Test the ram, try different video cards, etc. It takes time and is tedious, but that's the only way to do it, unless you take it into a shop and pay them to do it.

A last thought is that you might check the temps. Download Speedfan or Core temp and check the temp of the CPU in particular. I try to keep the CPU temp in the 50s or cooler. Under full load, my QX9650 runs at 55c using Core temp. If your CPU is running hot, you may need to upgrade the cooling, either by getting a better heatsink or adding a fan(s) to the case.

m
0
l
December 22, 2008 6:42:47 PM

My Core Temps are Overall 45C when I'm gaming, the MB's temp is 25-30C and the graphic card 35-45C at 50% speed. I Have the Antec Nine Hundred Gaming case, so I don't suspect the temps for being the problem.

After I sat the default settings from Auto to 1,9 V It haven't appeared any new crashes...(In 4 hours)
The manufacturer (Corsair) recommends 1,9 V for my type of RAM, but turning it up to 2,1 does no harm?
m
0
l
December 22, 2008 6:48:35 PM

If you're running without crashes at 1.9v, just leave it there. I don't know where these suggestions of 2.1v and upping the CPU voltage came from. There's no need to raise voltages beyond what's needed for stability.

Now that you've manually set the voltage to the recommended spec, I'd run memtest86+ overnight and see if it returns any errors. If it shows any errors at the rated speed, timings, and voltage I'd RMA the RAM. RAM that's functioning correctly shouldn't even get one error in memtest.
m
0
l
December 22, 2008 7:03:01 PM

This case has temporary been solved, but not for sure. I will try this out and you guy will hear from me if it keeps on... Thanks!
m
0
l
December 23, 2008 12:20:04 AM

lilleenga said:
My Core Temps are Overall 45C when I'm gaming, the MB's temp is 25-30C and the graphic card 35-45C at 50% speed. I Have the Antec Nine Hundred Gaming case, so I don't suspect the temps for being the problem.

After I sat the default settings from Auto to 1,9 V It haven't appeared any new crashes...(In 4 hours)
The manufacturer (Corsair) recommends 1,9 V for my type of RAM, but turning it up to 2,1 does no harm?


Glad that raising the ram voltage to 1.9v seems to be working. As for my other suggestions to raising the ram voltage to 2.1v or raising the CPU voltage, those were meant only if nothing else seemed to work, and were meant as upper limits, not as standard for running. They were not meant to be done if unneeded.

Your temps are very good, and your Antec 900 case is a good one. I know, because that's what I use to house my overclocked QX9650, which does have the ram at 2.1v and the CPU at 1.35v.
m
0
l
December 23, 2008 4:20:44 PM

My PC haven't crash one time since I changed my RAM Voltage, but with my luck I can expect everything. It' been 24 hours, and nothing has happened, but can I really still Except the worse?!? I thought 0,1 voltage didn't change anything... Can it be solved?
m
0
l
December 23, 2008 5:48:54 PM

Yes, fixing a RAM issue can be as easy as setting the voltage to the recommended specs (even if it is only +.1v).
m
0
l
December 23, 2008 7:27:05 PM

lilleenga said:
I thought 0,1 voltage didn't change anything... Can it be solved?


Yes it can. With computers, sometimes what looks like the most insignificant thing can make all the difference in the world.

Of course, that applies to some women I've met in the past as well. :kaola: 
m
0
l
December 23, 2008 9:59:12 PM

I'm wondering.... I used the RAM on my previous PC too, why didn't it crash there? And a Biip sound disappeared after the change of the Voltage. I thought that it was a kind of a Alarm for overheating... Could it be a warning for wrong Voltage on my RAM?!?!
m
0
l
December 23, 2008 10:25:27 PM

lilleenga said:
I'm wondering.... I used the RAM on my previous PC too, why didn't it crash there? And a Biip sound disappeared after the change of the Voltage. I thought that it was a kind of a Alarm for overheating... Could it be a warning for wrong Voltage on my RAM?!?!


A number of possibilities. It could be that your previous PC didn't strain the ram as much, or that its BIOS fed the ram the correct voltage. Or it could be the your new motherboard is more sensitive to incorrect voltage in the ram. Such is life and its probably not a good idea to question the answers too highly.

As to the beeping sound, it most likely did refer to the ram voltage. There are a number of different beep codes that computers often give, each tied in with specific parts. Often these beep codes are contained in the handbook that comes with the motherboard, or can be found at the company's website.
m
0
l
December 24, 2008 2:49:00 PM

Looks like I'm starting to get somewhere, oh and by the way Merry Christmas everybody.
m
0
l
December 25, 2008 3:01:33 PM

Product
Windows

Problem
Shut down unexpectedly

Date
25.12.2008 17:58

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1044

Files that help describe the problem (some files may no longer be available)
Mini122508-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFFA60019D2180
BCP4: 0000000000000003
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information: 22b4b373-caac-402b-837c-93a73b957d4b

I had a feeling that this wasn't over... :sweat: 
m
0
l
December 25, 2008 7:46:03 PM


How many gigs of RAM, how many slots are populated and and what is your motherboard?


MERRY CHRISTMAS!!

m
0
l
December 26, 2008 10:49:36 AM

Usually 4Gb(2Gbx2) but I've tried to remove one already. My Motherboard is Asus P5Q Pro.

When I ran the MemTest86+ it said "Single Chanel" and the Cache was "on". It was no errors while I was running it. Is there any special Slots on the motherboard that is recommended different types of RAM?
m
0
l
December 29, 2008 2:31:47 AM

Sorry to take so long to get back.

If memtest says your ram is ok (you did what shortsuff_m said to do) then I'm going back to the first thing the windows error report said....video driver issues. The best guide I know of for video driver installation is in the TweakGuides companion. It's a PDF you can download for free.

As far as which slots to install the ram in, look in your motherboard manual. It will show you which slots to populate.

Good luck and Happy New Year.




m
0
l
December 29, 2008 5:27:28 AM

Back for the moment, then off later in the week.

OK, like am71 says, the issue remains in the video drivers, but I suspect that it might be deeper than that. One possible answer is that the BIOS is still trying to use a built in video from the motherboard and is running into a conflict, therefore the blue screen. It shouldn't happen, but I've heard of it happening in the past. Another possibility is that there are both ATI and Nvidia drivers active in the programing and though the computer may boot up initially, it eventually crashes because of a conflict. The solution there is to remove all drivers from every location that you can find, even those downloaded in temporary files. Just because you didn't run it through setup doesn't mean it can't cause a later conflict. So get rid of everything and then reload the drivers for the appropriate card.

Last, but by no means least, you may need to reinstall Windows from scratch. Its a PITA, but sometimes bugs get into the programming and the only way to get rid of them is to reload everything. Back in the days of Win95, it seemed that I had to reload everything every six months or so because of the bugs in the system. Just because its a lot rarer theses days to have to do it, that doesn't mean that it doesn't have to be done. You never know for sure, but you may have gotten a boot system virus or worm that is slowly destroying the OS or other parts of the programming. The advantage of reinstalling Windows is that you will know that you have a clean OS to start with, and then you add the drivers as necessary one by one and have no conflicting software to drive up your blood pressure.

Of course there is one very last resort, and that is taking the computer in to a professional shop for diagnosis. If you have an insurance company or know of an insurance company that covers house insurance, ask them where they would send a computer for diagnosis. One time a couple years back I fought with a computer problem for days, and nothing I did worked. My insurance company rep suggested a shop and I took it there. It cost me $35 and the guy at the shop said that my hard drive was bad. I put in a new hard drive, reinstalled the OS, and that computer is running fine to this day. That turned out to be $35 well spent in my book, if only for the cessation of the headache.
m
0
l
December 29, 2008 10:43:54 AM

I bought the components for a halt years ago, but my power supply and the RAM came from my old computer. (not original from the PC)

My computer crash at some games, but when I reboot Windows Problem Reports and Solutions says that it caused of my video card. I know that my ATI video card causes a system crash and I know how to fix it, but something else causes the other problem... and it gives me a totally different report.

When I run Itunes or WMP it can crash, it has happened a couple of times, and that is the same problem that "randomly" appears...
Is there any other information I can give you guys to help me? :??: 
m
0
l
December 31, 2008 10:26:59 AM

Here is another one:

Product
Windows

Problem
Shut down unexpectedly

Date
26.12.2008 19:57

Status
More information available

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1044

Files that help describe the problem (some files may no longer be available)
Mini122608-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 24
BCP1: 00000000001904AA
BCP2: FFFFFA60079FEAC8
BCP3: FFFFFA60079FE4A0
BCP4: FFFFFA600101CB49
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information: fbb3d109-eb95-4545-baab-aeef8c506f2b

and right now a BlueScreen Error 0X0000020 or something just came up...
I've tried most of your tips, nothing seems to work. I've also tried to scan the hard drive with:
Malwarebytes' Anti-Malware, AVG Anti virus and Windows defender, but it couldn't find anything.
This computer is useless now, I desperately need your help :( 

m
0
l
December 31, 2008 11:14:12 AM

There is a utitlity called "Win DBG" (for Windows Debugger):

Download it:
http://www.microsoft.com/whdc/devtools/debugging/defaul...


What it will do is help to identify the source of the issue. Though it may well only confirm what we already suspect: Something wrong with the video driver.

There are also some how to's on the page as well, which could help.

At this point, I would be inclined to souce different versions of your video card driver to see if an (older) one works.




m
0
l
December 31, 2008 12:36:45 PM


Microsoft (R) Windows Debugger Version 6.10.0003.233 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini123008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`02060000 PsLoadedModuleList = 0xfffff800`02225db0
Debug session time: Tue Dec 30 22:10:13.045 2008 (GMT+1)
System Uptime: 0 days 3:37:36.439
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff800053cef89, 8, fffff800053cef89, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff800053cef89, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff800053cef89, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002289080
fffff800053cef89

FAULTING_IP:
+fffff800053cef89
fffff800`053cef89 ?? ???

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffa60079f7310 -- (.trap 0xfffffa60079f7310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=fffff8800f3d3980 rcx=0000000000000001
rdx=fffffa800396b88c rsi=0000000000000000 rdi=fffff8800f3d3958
rip=fffff800053cef89 rsp=fffffa60079f74a0 rbp=0000000000000064
r8=0000000000000000 r9=fffffa60079f76d9 r10=fffff8800f3d3930
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff800`053cef89 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800020c3524 to fffff800020b5350

STACK_TEXT:
fffffa60`079f7218 fffff800`020c3524 : 00000000`00000050 fffff800`053cef89 00000000`00000008 fffffa60`079f7310 : nt!KeBugCheckEx
fffffa60`079f7220 fffff800`020b3ed9 : 00000000`00000008 00000000`00000008 00000000`00000000 00000000`00000064 : nt!MmAccessFault+0x534
fffffa60`079f7310 fffff800`053cef89 : 00000074`00000000 00000000`00000000 00000000`00000000 fffff880`0afd2210 : nt!KiPageFault+0x119
fffffa60`079f74a0 00000074`00000000 : 00000000`00000000 00000000`00000000 fffff880`0afd2210 00000000`00000000 : 0xfffff800`053cef89
fffffa60`079f74a8 00000000`00000000 : 00000000`00000000 fffff880`0afd2210 00000000`00000000 fffff880`0f3d3930 : 0x74`00000000
fffffa60`079f74b0 00000000`00000000 : fffff880`0afd2210 00000000`00000000 fffff880`0f3d3930 fffff880`0f3d3958 : 0x0
fffffa60`079f74b8 fffff880`0afd2210 : 00000000`00000000 fffff880`0f3d3930 fffff880`0f3d3958 fffff880`0f3d3974 : 0x0
fffffa60`079f74c0 00000000`00000000 : fffff880`0f3d3930 fffff880`0f3d3958 fffff880`0f3d3974 fffff880`0f3d3980 : 0xfffff880`0afd2210
fffffa60`079f74c8 fffff880`0f3d3930 : fffff880`0f3d3958 fffff880`0f3d3974 fffff880`0f3d3980 00000000`00000000 : 0x0
fffffa60`079f74d0 fffff880`0f3d3958 : fffff880`0f3d3974 fffff880`0f3d3980 00000000`00000000 00000000`00000000 : 0xfffff880`0f3d3930
fffffa60`079f74d8 fffff880`0f3d3974 : fffff880`0f3d3980 00000000`00000000 00000000`00000000 fffff800`00000001 : 0xfffff880`0f3d3958
fffffa60`079f74e0 fffff880`0f3d3980 : 00000000`00000000 00000000`00000000 fffff800`00000001 fffffa60`079f7518 : 0xfffff880`0f3d3974
fffffa60`079f74e8 00000000`00000000 : 00000000`00000000 fffff800`00000001 fffffa60`079f7518 fffff880`0afd2210 : 0xfffff880`0f3d3980
fffffa60`079f74f0 00000000`00000000 : fffff800`00000001 fffffa60`079f7518 fffff880`0afd2210 00000000`00000000 : 0x0
fffffa60`079f74f8 fffff800`00000001 : fffffa60`079f7518 fffff880`0afd2210 00000000`00000000 fffff800`00000064 : 0x0
fffffa60`079f7500 fffffa60`079f7518 : fffff880`0afd2210 00000000`00000000 fffff800`00000064 fffffa60`079f76d9 : 0xfffff800`00000001
fffffa60`079f7508 fffff880`0afd2210 : 00000000`00000000 fffff800`00000064 fffffa60`079f76d9 fffffa60`079f76f0 : 0xfffffa60`079f7518
fffffa60`079f7510 00000000`00000000 : fffff800`00000064 fffffa60`079f76d9 fffffa60`079f76f0 fffffa60`079f76f8 : 0xfffff880`0afd2210
fffffa60`079f7518 fffff800`00000064 : fffffa60`079f76d9 fffffa60`079f76f0 fffffa60`079f76f8 fffff880`0efae060 : 0x0
fffffa60`079f7520 fffffa60`079f76d9 : fffffa60`079f76f0 fffffa60`079f76f8 fffff880`0efae060 00000000`00000000 : 0xfffff800`00000064
fffffa60`079f7528 fffffa60`079f76f0 : fffffa60`079f76f8 fffff880`0efae060 00000000`00000000 00000000`00000000 : 0xfffffa60`079f76d9
fffffa60`079f7530 fffffa60`079f76f8 : fffff880`0efae060 00000000`00000000 00000000`00000000 fffff880`0d3ee554 : 0xfffffa60`079f76f0
fffffa60`079f7538 fffff880`0efae060 : 00000000`00000000 00000000`00000000 fffff880`0d3ee554 fffff800`02347803 : 0xfffffa60`079f76f8
fffffa60`079f7540 00000000`00000000 : 00000000`00000000 fffff880`0d3ee554 fffff800`02347803 00000000`00000000 : 0xfffff880`0efae060
fffffa60`079f7548 00000000`00000000 : fffff880`0d3ee554 fffff800`02347803 00000000`00000000 00000000`00000004 : 0x0
fffffa60`079f7550 fffff880`0d3ee554 : fffff800`02347803 00000000`00000000 00000000`00000004 fffff880`0d3ee500 : 0x0
fffffa60`079f7558 fffff800`02347803 : 00000000`00000000 00000000`00000004 fffff880`0d3ee500 fffff800`02193f00 : 0xfffff880`0d3ee554
fffffa60`079f7560 fffff800`0233d76f : fffff880`0efae060 fffffa80`0396b840 00000000`000000c8 fffffa60`079f7b28 : nt!RtlpInheritAcl+0x183
fffffa60`079f7630 fffff800`0233ef71 : fffffa60`079f7990 00000000`00000000 fffffa80`0600cda0 fffff880`0efae060 : nt!RtlpNewSecurityObject+0xacf
fffffa60`079f78b0 fffff800`022fb85f : 00000000`00000000 00000000`0155f340 fffff880`089a39c0 fffff880`07ff9060 : nt!ObInsertObject+0x291
fffffa60`079f7ac0 fffff800`022fb981 : fffffa80`04263760 fffffa60`00000008 fffffa60`079f7c00 00000000`00000000 : nt!NtOpenThreadTokenEx+0x35f
fffffa60`079f7be0 fffff800`020b4df3 : fffffa80`04263760 00000000`03c07c80 00000000`00000000 fffffa80`08685560 : nt!NtOpenThreadToken+0x11
fffffa60`079f7c20 00000000`77d45cba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0155f2f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d45cba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiPageFault+119
fffff800`020b3ed9 85c0 test eax,eax

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+119

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0x50_nt!KiPageFault+119

BUCKET_ID: X64_0x50_nt!KiPageFault+119

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

Ok, what is the problem?
m
0
l
December 31, 2008 12:54:35 PM

OK... We've gotten just a little further than before: "PAGE_FAULT_IN_NONPAGED_AREA (50)" - tells us that one of your drivers (I think we can agree it's Video) is referencing a memory location it should not.... Unfortunately, while it's better than we had before, it doens't tell us the exact root cause.

I did some checking and found some Knowledge Base articles for you:

http://support.microsoft.com/search/default.aspx?mode=r...


Reading through them to see if I can pick the likely suspect...


(yah - There's very little to do at work today, so...)
m
0
l
January 2, 2009 1:08:28 PM

what about "ntkrnlmp.exe"? It says that it's "Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 ) ???
m
0
l
January 2, 2009 1:46:28 PM

lilleenga said:
what about "ntkrnlmp.exe"? It says that it's "Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 ) ???


You seem to have some major errors in your system, that is, the OS has been corrupted in some way and is no longer functioning correctly. At this point, I would strip the machine down to its basics and reinstall the OS. Then add the various cards and their drivers. At least that is what I would do, as its easier than struggling along and hoping to find out what went wrong and correct that (those) things. Besides, when you start patching the patches that you patched before, using hotfixes or whatever, you add complexity and can make things even harder to figure out.

That's my 2 cents worth of opinion, anyway.
m
0
l
January 2, 2009 1:52:28 PM

This is an error in the core components of the Windows OS. Like a previous post suggests, re-install the OS is the best choice. Start installing the OS without any PCI cards in the sockets. After the OS is installed, add each card and install each device driver and then re-start your computer. If there is a problem before adding the PCI video card, ethernet card, sound card, etc. then it is likely a defective system board, CPU, BIOS, or disk drive.
m
0
l
January 2, 2009 3:36:04 PM

Do I have to format my hard drive? Or just "repair" the OS?
m
0
l
January 2, 2009 4:11:47 PM

lilleenga said:
Do I have to format my hard drive? Or just "repair" the OS?


Yes, you have to format the hard drive and install from scratch. Its a pain to do it, but that's the only way to make sure that the errors don't escape, which can happen under "repair". You should backup any data that's important so you can reinstall it later.
m
0
l
January 3, 2009 4:07:28 PM

No other way?
m
0
l
January 3, 2009 4:45:05 PM

lilleenga said:
No other way?


No other way to reliably fix the problem. That's why its so much of a pain.

Sure, you could try to simply "repair" the OS. Nothing really will get hurt in doing so. Never know, you might just get lucky. Then again, you could go through the time and effort only to find that the problem is still there, thereby leading to more frustration and headaches. Even worse, more problems could seep in and you have to reformat anyway. Then again, you might just get lucky.
m
0
l
!