| 1. |
Solve : Blue Screen Problems.? |
|
Answer» Hello I've been having some problems where my computer will stop to a blue screen and I need to restart. The reported error codes are: 0x0000008e (0xC0000005, 0x805446F3, 0xA791CBCC, 0x00000000). 0xC0000005: STATUS_ACCESS_VIOLATION Test your RAM and considering the computer has been moved about if memtest shows any problems then re-seating your RAM may fix it.Neil....... I agree with what Fed has posted ....... By any chance have you overclocked your system ? If so , try unclocking it . dl65 The below site is a good place to search(self help} for most Windows errors. http://aumha.org/OK I had another one but this time it says DRIVER_IRQL_NOT_LESS_OR_EQUAL Stop codes: 0x000000D1 (0x00000038, 0x00000002, 0x00000001, 0xAAF15AB6) It says something is wrong with NVTcp.sys address AAF15AB6 base at AAF13000 Date Stamp 4253b85b My graphics card is ATI but my motherboard uses Nvidia nForce drivers. I'll try reinstalling and updating those. I haven't had chance to run memory test yet. Could you RECOMMEND a good scanner? I am not overclocking.Other possibilities: http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2005-29,GGLG:en&q=stop+0x0000008e+site%3Amicrosoft%2Ecom http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2005-29,GGLG:en&q=0x000000D1+site%3Amicrosoft%2EcomFrom the Mothership.... Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. Parameters The following parameters are displayed on the blue screen. Parameter Description 1 Memory referenced 2 IRQL at time of reference 3 0: Read 1: Write 4 Address that referenced memory Cause A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses. Resolving the Problem To begin debugging, use a kernel debugger to get a stack trace. Does anyone really understand all that stuff? I for one have no inclination to embark on that learning curve. My money is on the RAM. http://www.memtest86.com/ Download - Pre-Compiled Memtest86 v3.2 installable from Windows and DOS to your desktop double click and create a bootable floppy, reboot to that floppy & let it run for a couple of hours.Quote Download - Pre-Compiled Memtest86 v3.2 installable from Windows and DOS to your desktop double click and create a bootable floppy, reboot to that floppy & [highlight]let it run for a couple of hours.[/highlight] OK I'll do this... tonight Oh a QUESTION, when handling ram, how fragile is it? When I put in my new stick I tried to be CAREFUL, but I did need to give it a hearty shove to get it in the slot.I ran memtest for 2 passes and it found 0 errors.How long did the 2 passes take, most people seem to say run it for a couple of hours or so. Did this start HAPPENING after installing new ram, is it fully compatible and in the right slot etc? How about removing the new ram as a test?It took about an hour. This is a new computer, but I am using some ram from my old computer as well as some new ram. |
|