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 (http://support.microsoft.com/kb/314063)

[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 (http://www.techarp.com/freebog.aspx)

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

[riverfest]

Slgrieb, thanks for the info. I have already tried a known good Antec true 430 from a good sysytem and crashes still happen.

Kodiak, All 4 sticks have passed memtest, although I have had bad sticks pass these tests before. Also, no overclocking on this system. It was just a new system that never worked from the original HP deployment image.

Noonoo, I still have the original drive. I would just try a clean install on a seperate SATA drive, not activate it, and start to load drivers and see where it crashes.

I will start my work list here in a few hours and then update these posts.

[slgrieb]

Very interesting thread river. If this hadn't been a new machine I would say you had a corrupted video driver. I just can't recall seeing this on a new machine, though. Also, my take is that when you installed the new motherboard, you installed a new video driver. And you also got an error installing Vista, right? Do you have a video card available that uses something other than an nVidia chip?

[riverfest]

There are many posts about finicky memory issues with AM2 boards, so i am ordering 3 set of memory from crucial: BL2KIT12864AL804 . Certified by Crucial to work with board. I feel the original samsung M378T6553CZ3-CD5 is bad and that my Kingston KHX4300D2K2/1G is incompatable with new ASUS board, although it would boot and run with HP version of Asus board.

I tried new nic ( and disabled onboard Nvidia NIC) - still errors.
I tried an old PCI video card still errors.
I feel if it were CPU, i wouldn't be getting this far at all.
I tried a different ATX case with a different BIOS and turned off all caching,etc. - still errors
I tried new cables, a different outlet and different power cord. - still errors.
All drivers, including chipset at most recent versions.
I did not wipe and reload.

I will have more to post later this week after new memory arrives.

Thanks all for your help so far.

[riverfest]

:flames:
New memory came in this afternoon. Installed and BSOD 0x0000008E. I went into BIOS and manually set CAS, tRCD, tRP and tRAS without any change or benefit (except back to original 0x0000000A BSOD).

I am also getting other errors like "internet explorer has encountered an error and will be closed" and "lsass.exe has encountered an error and the system will shutdown." I guess these could come from the initial install if the files where not correctly installed before the random system reboots.

I have not changed CPU or done WAR. I am leaning towards a wipe and reload. (I backed up my activation files). If I encounter reboots during WAR, I would assume it is still a hardware error, but I have changed all components other than CPU. I still don't think I would get this far if it is CPU.

Suggestions?

[NooNoo]

Why not just run a repair install?

[riverfest]

All right. Cleaned house. Fresh install of XP Pro SP2. Got rid of HP's version of media center. Updated all drivers, installed Adobe Reader and some apps. No crashes of explorer and no BSOD's yet.

I am going to reset some bios options back to their defaults, the if all goes well, start enabling hardware, the adding back the original components such as the memory.

Lastly, I will install windows updates.....

I am now leaning towards the fact that it was a software/driver issue. BUT i got random reboots during a clean install of Vista so I figured it was a hardware issue....

..so some more troubleshooting

[riverfest]

I have reset Bios memory settings to auto, re-enabled caching and spread spectrum and HT support - no issues.

I have re-connected all devices - no issues.

I have re-installed ORIGINAL memory chips - no issues.

I have NOT reinstalled original HP motherboard to see if issues come back.

I have NOT tried a clean re-install from CD's (not recovery partition) of original OS (media center).

I am currently installing MS updates.

My current conclusion is bad HP motherboard was cause of reboots/BSOD and never allowed a clean install of OS. When I ghosted the image to another HD and did MB swap I believe I brought those problems into the new system with the ghosted drive.

i will update final results after this weekend when i have had more time to evaluate and test

Does this conclusion make sense?

[NooNoo]

Does to me!

[slgrieb]

Looking for something totally different, I found http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=204&p_created=1103226734&p_sid=xn*g2aHi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX 3Jvd19jbnQ9MiZwX3Byb2RzPSZwX2NhdHM9JnBfcHY9JnBfY3Y 9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wY WdlPTEmcF9zZWFyY2hfdGV4dD1kcml2ZXIgY2xlYW5lcg**&p_li=&p_topview=1

sounded strangely familiar.

[riverfest]

everything ran good for the last few days...even on the HP MB. So i am going to try an use the HP recovery partition to get back to the original setup and then see if Slgrieb's link provides a solution.

One side note - the recovery partition was not bootable nor did the F10 button work to load the recovery process. I followed the instructions at http://www.gripe2ed.com/scoop/comments/2004/1/18/113551/618/1 and am now performing a recovery installation.

I'll post more soon, but looks as if this could have been a driver issue - a driver for a device not even installed.

[riverfest]

no dice.
setup keeps failing with "the system is not fully installed please run setup again" I have also followed the instructions from HP over athttp://h10025.www1.hp.com/ewfrf/wc/document?docname=c00024476&lc=en&cc=us&dlc=&product=71747&rule=915.

Now I just get freezes at xp splash screen. does not work in safe mode either.

[riverfest]

hp recovery partition relaoded the OS. I ran drivercleaner pro as posted in the NVIDIA link slgrieb posted and found no Nvidia WDM drivers.... but i did find ATI WDM drivers. This is an HP branded ASUS Motherboard w/ NVIDIA chipset. I don't believe ATI drivers should be on here. I know they don't play nice together from previous systems. I used Drivercleaner to remove all ATI drivers.

Still crashes - 0x00000050 and then 0x0000000A.

Would anyone suggest using the driver cleaner to remove all the Nvidia drivers as well? and then install them from new sources?

OR

I could load an OEM media center 2005 and use the HP sn# to see if it is the install or maybe something just doesn't play well with media center.

[riverfest]

Still lots of wierd behaviors: errors in RPC, mshtml, drwatson.

I then tried to remove all NVIDIA drivers in safe mode using drivercleaner pro. When i restarted windows, there was no "new hardware found" dialogs, so i looked at device manager and there were NO yellow driver issues.

I even tried to manually install the NVIDIA chipset drivers as directed by HP and when i point to the .inf file windows says this filw was not intended for your hardware. Under automatic mode it says no better match was found.

Every couple reboots i have to go back into settings and performance and uncheck the restart box so i can get BSOD stop messages from the screen.

Also HP's 6150LE driver (nv4_disp.inf) has a version of 8.2.0.8 The same file on the ASUS website and CD is only at version 8.2.0.5

All advice will be considered.

[riverfest]

i still can't get HP's version to behave. I can install oem version of MCE on original HP hardware and it runs find with no BSOD's. It won't accept either the serial from the case sticker or the original key that is on the HP install and says i must activate it. (but this was just for test purposes) I also copied the wpa files from the original HP install into the oem install - no luck.

This point to a driver issue or a corrupt .sif.

I will try to copy the i386 folder from the HP recovery partition, delete the drivers folder and see if i can just get a clean MCE CD.

[riverfest]

I have given up.
I installed MCE 2005 OEM from disks. The serial from the .sif and the serial from original install would not take. The case sticker would work for entry but required activation. I even copied the wpa files from the HP installation to this one. I called MS talked to the computer and was given new activation code. No hardware had changed. Bith CD disks had the same info :
[Pid]
ExtraData=786F687170637175716954806365EF
Pid=76487OEM

One of these serials should have been a VL that did not require activation (which is why i got the " this serial has been activated too many times" when i used the case sticker)

I tried to extract the I386 files from the recovery partition, but i could not get the MCE functionality - only xp sp2. The media center .cab is in a folder called cmpnents on the HP main partition but not on the recovery. It might be part of the preload folder that has the data.inp files and base.inp files. MCE must be installed at the initial installation and cannot be added to later from what i undersatnd.

All is working flawlessly with original hardware and drivers from HP site. This may have been a DRIVER issue. I could not determine which one. OR it could have been a corrupt install or some HP bloatware that didn't play nice.

[NooNoo]

Glad you came to a conclusion RiverFest, perhaps not the ideal one, but one that works.