Problems with Windows Vista x64 Startup. Errors:0x0000000A, 0x0000007E

Hello.
I am building my own system with the following specification.

System Specifications:
Intel Core 2 Quad Q6600 2.4Ghz
Asus P5N32-E SLI Plus Motherboard
Nvidia GeForce 8800GT 512Mb Graphics
2x OCZ 2GB DDR2 800Mhz
Windows Vista Home Premium 64 bit
160Gb Hitachi HardDrive 7200rpm
20x WriteMaster DVD RW

The problem is that the system will only boot on occasion. More often than not the system will display a blue screen with one of two error messages during loading windows. Then restart after several seconds.

Error Codes:
0x0000000A
0x0000007E

The same thing also happened in the final part of the installation of Windows Vista Home Premium 64 bit. After the system had restarted during the installation during the completing installation section the blue screen flashed up and then rebooted straight away.

I have tried several things to work out what is wrong but have been unable to work it out yet:
First I tried moving the two 2Gb Ram modules to the other dual memory slots but still experianced the same problem.
Next I tried each 2Gb Ram module on its own and with both modules the system sucessfully started several times.
Then I tried using two 1Gb 667Mhz Ram modules and again the system sucessfully started several times.
Finally I put the two 2Gb modules back in and changed the HardDrive to use a 160Gb Maxtor 7200rpm HardDrive running Windows Vista Home Premium 32 bit and the system sucessfully started several times again. However I also tried the orginal HardDrive in another system (specification below) and that sucessfully started several times.

Other system specification:
AMD Athlon 64 4200 Dual Core
ASRock AM2NF6G-VSTA
2x 1Gb DDR2 667Mhz Ram
Nvidia GeForce 7600GT 256Mb Graphics
20x DVD RW Drive

I have also updated the BIOS to the most recent from the ASUS website.

I am wondering if anyone can come up with a solution to this problem or indicate where the problem may be.

Thank you for your help.

not sure about the first code...but the second one looks like a memory issue...either a memory error or memory dump...try gettn logged into safemode...and run memtest86 or prime95...so try this first before we move on

I was unable get into safemode when having these problems, but I am currently using the system using the alternative harddrive mentioned in the above post.

I am unsure how to run memtest86 or prime95. Are they programs I can get somewhere or somthing including with windows. Where do I find them? Do I have to be in safe mode to use them? Sorry if these are stupid questions

Thanks
Mark

I have tried several things to work out what is wrong but have been unable to work it out yet:

Click to expand...

Do you have MS update (KB929777) installed?

Try memory diagnostic tool (type it into your start search to find it)

djt yes I do have that update.

z3r010 thanks for that. I have found it and will run it in about an hour since I am unable to right now. I will post back here straight after that.

Thanks for the help so far :D
Mark

sorry about that onslaught...and no you do not have to be in safe mode when running these..i just recommended that if you are unable to run your computer normally...now do what john said first, then download these and run them

Memtest86.com - Memory Diagnostic

Download Prime95 25.5a - A program designed to be used to find Mersenne Prime numbers. - Softpedia

havent tried memtest but prime95 works great

also i hope u have any luck running the memory diagnostic tool...its really great...once your back in your account...dont freak out and say it didnt do anything or tell u anything...it will give a popup about 15 min later

djt yes I do have that update

Click to expand...

Please keep us posted on your progress with this problem. I’m planning on using this same OCZ memory (CAS 4) in a build I’m about to put together with an Intel X38 motherboard.

I have done a memory test and it found no problems.
I am unable to use memtest as I dont have a floppy drive.
I am unsure of how to use prime95. Any directions on how to use it to test my machine are apriciated.

Thanks for the responses so far.
Mark

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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 which referenced memory


Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
Try disabling memory caching of the BIOS.
Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
Make sure the latest Service Pack is installed.
If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This indicates that a system thread generated an exception which the error handler did not catch.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The address of the exception record
4 The address of the context record


Cause
This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.

0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.


For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.

Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.

I hope this info helps you track down the blue screen errors your having, Have you attempted installing Vista with the most minimal amount of hardware installed?

What voltage are you supplying your RAM and what does OCZ specify you run it at? Guessing your Vdimm should be set to ~2.1 to 2.3v, depends on the exact part number. Under voltage can cause instability.

I had a very similar thing happen to me when I upgraded my memory from 2 to 4 (also using OCZ DDR2 800) and installed Vista x64.

I eventually managed to work out the one of the new memory modules was faulty, so I took them back to the shop. The guy working there exchanged them, no problem, and even said he was starting to lose faith in the OCZ ram.

The new ones are working perfectly.

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.
That is the 1st Parameter of the 0x0000007E error.

I have also contacted OCZ at the same time as posting this here and they sugested putting my DRAM voltage to 2.0V in the Bios. I couldn't find this exact setting but tried putting Memory Voltage to 2.0V, but after trying this I still recieved the 0x0000007E error. I intend to contact them again soon.

Both error messages seem to incidcate problems with memory so would that be my best place to be asking about?

Also I do have a full set of Parameters for each error, but I noticed some of them changed from time to time so chose not to post them here. If anyone believes they could help to finding a cause or fix please let me know and I will post them.

dmex I believe that I only used the very minimum hardware when trying. I have no onboard graphics so needed the graphics card. I only have 1 HardDrive and 1 DVD Drive. Then I had the Motherboard, Processor and Ram. I did sucessfully install Vista whilst using just 1 2Gb stick of Ram, but the problem continued when I added the other after installation.

Thanks for all your help so far.
Mark

Reset the bios to default settings then use NVIDIA nTune to overclock your system, ntune should detect any voltage or timing settings dynamically without forcing the hardware to use unstable settings in the bios.

I would strip the PC of just bare essentials and try to boot. From my past expiernces IRQL_NOT_LESS_OR_EQUAL means memory is bad.
Raj

if u have installed prime95...under one of the tabs...you should see one that says torture cpu..choose this, and do a blended test...if u do not see wat i am saying...please tell me, as i am not looking at the prime95 screen and will have to download it if necessary

cpuz does a good job detecting your mainboard info and memory timings

CPUID