Hp blue screen

[riverfest]

stop: 0x0000000A (0xdffc0b9e,0x00000002,0x00000000,0x8051fd93)

This was a brand new A1600N from HP that never worked. It blue screened on setup and on some re-installs. I finally got a clean install. I have changed to new memory, new HD and now new MB (Asus M2NPV-VM). I have mini dumps, but i don't know how to read them. I also got BSOD with windows vista installs.

Any thoughts? Drivers? Hardware - power supply or cpu?

Thanks in advance

[Mayet]

http://support.microsoft.com/kb/314063

are you using a video card and/or a sound card. IS there onboard sound/video on the motherboard.

if you have changed ram, hd and memory.. it narrows it down to cpu, video or any other hardware extras you have installed.

what does your event viewer say?

post your mini dumps here

[riverfest]

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: dffc0b9e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8051fd93, address which referenced memory

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


READ_ADDRESS: dffc0b9e

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmAccessFault+10e5
8051fd93 66837f0e01 cmp word ptr [edi+0Eh],1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: dumprep.exe

TRAP_FRAME: ba3f7d64 -- (.trap 0xffffffffba3f7d64)
ErrCode = 00000004
eax=00a17f80 ebx=00000000 ecx=0000ffff edx=00000003 esi=00000000 edi=0007aeec
eip=7c91280d esp=0007adf0 ebp=0007aeac iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
001b:7c91280d ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 805437c8 to 8051fd93

STACK_TEXT:
ba3f7d4c 805437c8 00000000 00a17f8c 00000001 nt!MmAccessFault+0x10e5
ba3f7d4c 7c91280d 00000000 00a17f8c 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007aeac 00000000 00000000 00000000 00000000 0x7c91280d


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+d0
805437c8 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+d0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: RAISED_IRQL_USER_FAULT

MODULE_NAME: Unknown_Module

Followup: MachineOwner



more dumps to follow as errors change

[riverfest]

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000045, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f6650208, address which referenced memory

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


READ_ADDRESS: 00000045

CURRENT_IRQL: 2

FAULTING_IP:
nv4_mini+1cb208
f6650208 8b5c2444 mov ebx,dword ptr [esp+44h]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 00000000 to f6650208

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x1cb208


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+1cb208
f6650208 8b5c2444 mov ebx,dword ptr [esp+44h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+1cb208

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43d6e7c7

FAILURE_BUCKET_ID: 0xD1_nv4_mini+1cb208

BUCKET_ID: 0xD1_nv4_mini+1cb208

Followup: MachineOwner



This appears to be NVIDIA driver, both MB used nvidia 6130 onboard video

[Mayet]

have you got a add in video card as well as the onboard vid?

[NooNoo]

What version nvidia drivers ( video and chipset) are you using?

[riverfest]

MB is ASUS M2NPV-VM with NVIDIA GeForce 6150 + nForce 430. My video is onboard and using asus/nvidia driver is 8.2.0.5. I have access to pci express nvidia 6800 GS and an old pci video card. I also have access to an AMD 64 X2 4400+, but it is from an asus A8N-SLI board - a socket 939. Can someone confirm that I cannot use this cpu in an AM2 MB?

I tried a P/S swap and got the 0x0000000A errors again. I have unplugged all accessories - usb, 1394, DVD drive. Only SATA cable and 1 hard drive are connected. I have changed SATA cables as well.

I am also tempted to drop a debian install on this system and see if I get any crashes.

[Mayet]

939 is not compatible with AM2 -different sockets.. the AM2 is newer technology

[NooNoo]

how to troubleshoot 0xA errors

[riverfest]

Noonoo, thanks for the link. That was the 1st place i started. I have not turned off all caching or shadowing, yet.

In my BIOS under advanced, CPU config - it lists cache ram as 512k x2 - but it is greyed out. Even if I change my "Jumper free Config in BIOS to manual, I cannot turn off L2 cache.

Underneath my chipset BIOS settings I have Spread Spectrum (down), PCIE Spread Spectrum (enabled), SATA Spreead Spectrum (enabled), and HT Spread Spectrum (down). These are the closest I can find to cachingand shadowing Should I disable these 4?I also have frame buffer size set to (32M), should I disable this?

Why i think it is not the HD:
I have disconnected all cables and devices from MB except SATA drive WD740DFD. I have used XP sp2 on this drive in a different system successfully which is why i am using it to troubleshoot.

Why I think it is not the RAM:
I have tried the original memory, one chip at a time in each in each of the 4 DIMM slots and tried it in pairs in each bank. I also have tried the same thing with an additional pair of DDR2.

I have swapped P/S.
I have swapped MB.

So, I am still at the conclusion of Video card or CPU. I will not get to add Video card until SAT

I did not wipe and reload. This was a cloned disk for troubleshooting purposes.
The OS has been reinstalled from the recovery partition with problems and reboots so i figured it was a hardware issue.

[NooNoo]

bios guide

It still could be your ram, but I agree, unlikely.

HP have specialised bios, therefore most of the things you see in the bios guide will not appear or be unavailable in an OEM machine such as an HP.

The spread spectrum can affect timings and therefore produce bsods.

You haven't said whether you have install the chipset drivers or not.

[riverfest]

Noonoo,
The orig board was an HP NodusM3-GL8E (also known as ASUS A8M2N-LA). I have swapped this out with a retail Asus M2NPV-VM. Both use the NVIDIA 6150 chipset. After the new install, I booted into safe mode and loaded the new drivers for this board including chipset, video, LAN, Audio & USB.

Ok. (not in this order)
1) I will try a case swap to get a different bios with additional settings.
2) Try to disable spread spectrum in HP BIOS settings
3) Try add-on video card and disable on-board
4) try add-on pci LAN card and disable on board. I have not swapped LAN, but have been using on board LAN from both boards.
5) WAR - wipe & reload from xp OEM CD not from HP recovery partition

[NooNoo]

Be careful with 5, you may invalidate the HP recovery partition function.

Don't forget the chipset drivers!

[slgrieb]

River, it is pretty long odds that you have problems related to any of the hardware you replaced (bad mainboard followed by defective replacement, etc.), so I would say the leading contender would be a bad power supply. The processor might be bad, but generally, these days they either work fine or not at all. I suppose you might have an issue with the CPU overheating; say cheap thermal compound or incorrectly applied compound, but the thermal circuit on a Socket 939 board really should just shut down the system before the processor starts to behave erratically.

So, I'd suspect you have a power supply that is out of spec. Easiest thing to do is beg, borrow, or steal a power supply that works, install it temporarily and see what happens. You can test your old supply with about $45-$65 of equipment, if you want to go that route. If you decide just to buy a new PSU, avoid the cheap ones because they aren't reliable. Even brand new out of the box.

[Kodiak]

If you got a floppy I would throw in memtest and test the memory even though you have tried different sticks. Or get the cd version. This could also have to do with memory timings or cpu issues such as overclocked. You may have to clock it down a little. Always if you have any important data back it up first. LOL