[Help] I need help with BSOD.

[Viper81]

ok, almost every time I restart (or do a fresh start) right after windows boots up (about 30 seconds after the start menu appears). I get a BSOD. The stop code is this:

STOP : 0x0000008E (0x0000008E, 0x00C6AA38, 0xB56F199C, 0x00000000)

please help. I cant figure this out. Also while were on the topic of boot up's, i cant see my boot up screen. it goes from my bois screen to the "Windows is Starting..." screen with like 30-45 seconds of a blank monitor. I didn't change any setting as far as i know, no viruses or anything. please help me. Thanks alot.

Viper

Title edited -- Please, use [TAGS] in your topic's title.

Please follow XP Forum Rules from now on.

--Sonic

[spazmire11]

solution A: try safe mode?

solution GOOGLE: http://support.microsoft.com/kb/315335

says it could be your ram, the FIRST result in google search!

[cluberti]

Note that these stop 0x8E errors are almost always hardware or driver related, so the suggestion of safe mode is a good one - if the issue doesn't occur in safe mode, then it's a driver issue (as most drivers don't load in safe mode). However, if you still experience a stop 0x8E in safe mode, it's likely hardware at fault.

Is your system configured for a full memory dump, and is your pagefile on C: and at least RAM+50MB? If so, the next time it happens your machine should create a memory.dmp file in \Windows after the reboot, and if you PM me, I can probably tell you exactly what is happening.

[Viper81]

see that's what i thought. but i just got brand new a-data memory. 2 gigs of it. (1gb x 2) would new memory throw me that error?

about my virtual memory. i have 3.9 gigs of it.

sys specs.

3.2 pentium 4 ht

2 gb a-data ram

80 gig hard drive

30 gig hard drive

nd-2100 nec dvd burner (flashed to nd-2500 for dvd-r support)

[HyperHacker]

If the new RAM doesn't work or isn't compatible, all sorts of things can go wrong.

[LLXX]

Run MemTest86+ on your system to see if it detects any errors.

Bad RAM will probably fail on the first pass.

[Viper81]

ok, I just got done running memtest86+. No errors on 4 passes. what next. and i still don't have a solution about the no boot up screen deal. sorry to be a pain but im really close to just saying screw it and doing a fresh reinstall of windows. (really dont want to do that because i have alot of programs that i would have to reinstall and not enough time to do it.) please help me, thanks

Viper

[HyperHacker]

solution A: try safe mode?

solution GOOGLE: http://support.microsoft.com/kb/315335

says it could be your ram, the FIRST result in google search!

That page says during setup, though. It could be something different when Windows is running; bad driver perhaps?

[cluberti]

Follow these steps to enable complete memory dumps:

1. If you have a feature like Compaq's Automatic System Restart (ASR), please disable it. This setting is usually found in the BIOS. With this feature enabled, if the BIOS does not detect a heartbeat from the OS, it will restart the server. This will interrupt the dump process.

2. Create or set the following registry value:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

Value: CrashOnCtrlScroll

Type: REG_DWORD

Data: 1

Refer to the following Knowledge Base article for more information on this registry key:

244139 Windows Feature Allows a Memory.dmp File to Be Generated with Keyboard

http://support.microsoft.com/?id=244139

3. Right-Click on the "My Computer" icon on the desktop and select "Properties"; this will open the "System Properties" window. Go to the "Advanced" tab and click "Performance Options". Click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB (both min and max).

4. Also in the "System Properties" window, click on the "Advanced" tab, then click "Startup and Recovery". Make sure "Complete Memory Dump" is selected (see 4a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed.

4a. If the "Complete Memory Dump" option in step 4 is not available, you will need to manually set this registry value:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

Value: CrashDumpEnabled

Type: REG_DWORD

Value: 1

5. You will need to reboot for these changes to take effect.

6. The next time that the machine bugchecks, and after the machine comes back up, wait for the disk activity to stop before logging in. Once the disk activity has stopped, please log in and find the resulting memory dump file, located by default at %systemroot%\memory.dmp (C:\WINDOWS\memory.dmp).

7. Please compress the resulting .dmp file and then PM for instructions on how to upload the file to me.

[Viper81]

to cluberti:

ok, i figured out how to do everything, but you loose me at number 6. do i wait for it to crash by itself or do i manually crash it and send you the memory.dmp file? In regards to #3, i have 2 gb of ram, so i set my virtual ram to 2050mb (min & max) right? or am i an idi0t ? this thing crashes like every other reboot. i need help. THANKS ALOT

Viper

Edited April 29, 2006 by Viper81

[cluberti]

You've done everything great, and I'd only suggest you manually crash it if it happens to hang up at this point - if it bugchecks on it's own, that is even better .

[Viper81]

ok i'll post the memory.dmp file as soon as it crashes on me again, thanks in advance.

Viper

[cluberti]

If you've configured for a complete dump, that file will be as big as the amount of physical RAM in the machine - so uploading here is probably impossible. PM me and I'll give you FTP information once you've got the dump compressed .

[RJARRRPCGP]

Your processor overclock likely is unstable. Did you check the voltages.

Does this only occur with a cold boot? If it does, monitor the voltages for a cold boot voltage feed problem. Your motherboard may not be giving your processor enough Vcore during a cold boot or after log offs.

Also, if it's the RAM, you usually would get a STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA BSOD instead.

Be on the lookout for a STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA BSOD.

Edited April 30, 2006 by RJARRRPCGP

[Viper81]

Your processor overclock likely is unstable. Did you check the voltages.

Does this only occur with a cold boot? If it does, monitor the voltages for a cold boot voltage feed problem. Your motherboard may not be giving your processor enough Vcore during a cold boot or after log offs.

Also, if it's the RAM, you usually would get a STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA BSOD instead.

Be on the lookout for a STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA BSOD.

no, even if i roll it back to 3.2 it still does it, voltage in range according to cpu-z (1.360-1.376)