BSOD when turning off/restarting windows

By spellcasterbr ·
Hello everyone, here's my first post:

I have recently changed my memory stick because of frequent random restarts. Ran memtest and found several errors.

Now the system runs almost fine, except for one thing: Whenever I restart or turn off the computer, about 1 in 4 times, I get a BSOD (Page Fault in Non Paged Area). This happens soon after then "saving settings" message appear.

After the system is restarted, I click on Start->Shut Down, and the system is shut down completely. It looks like the problem has more chances of happening after I power on the computer and use it for a while. If I just use it for a few minutes, I can shut it down with no problems.

Here's my minidump:
----- 32 bit Kernel Mini Dump Analysis

MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 06e80400
PfnDataBase 810a6000
PsLoadedModuleList 8055c700
PsActiveProcessHead 805627b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 10000050
BugCheckParameter1 e3e1c000
BugCheckParameter2 00000000
BugCheckParameter3 80636a16
BugCheckParameter4 00000001
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000500
DriverListOffset 00003110
DriverCount 0000007d
StringPoolOffset 00005630
StringPoolSize 00001120
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba0f1b00
DebuggerDataOffset 00002e80
DebuggerDataSize 00000290
DataBlocksOffset 00006750
DataBlocksCount 00000004

Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Apr 10 23:46:12 2007
System Uptime: 0 days 0:09:05
start end module name
804d7000 806e3000 nt Checksum: 001F5164 Timestamp: Wed Aug 04 02:58:37 2004 (41107B0D)

Unloaded modules:
b9f18000 b9f42000 kmixer.sys Timestamp: unavailable (00000000)
f7cb7000 f7cb8000 drmkaud.sys Timestamp: unavailable (00000000)
b9fea000 b9ff7000 DMusic.sys Timestamp: unavailable (00000000)
b9f42000 b9f65000 aec.sys Timestamp: unavailable (00000000)
ba01a000 ba028000 swmidi.sys Timestamp: unavailable (00000000)
f7b60000 f7b62000 splitter.sys Timestamp: unavailable (00000000)
bab1a000 bab2b000 Serial.SYS Timestamp: unavailable (00000000)
bab17000 bab2b000 Parport.SYS Timestamp: unavailable (00000000)
f77b0000 f77bb000 imapi.sys Timestamp: unavailable (00000000)
f7790000 f779f000 redbook.sys Timestamp: unavailable (00000000)
f79d8000 f79dd000 Cdaudio.SYS Timestamp: unavailable (00000000)
f72e3000 f72e6000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

Since it mentions several audio-related drivers, I thought the problem could be solved by updating audio/lan/chipset/sata drivers, but the problem persists.

Memtest86 reports no errors.

One interesting thing is that, whenever I use "chkdsk /F", it reports a few errors, fixes these errors and reboots. After the system is rebooted, I use chkdsk again, and it reports more errors.

Since I have changed the mem stick, is it possible for my motherboard or cpu to be faulty?

Here's my system specs:
Core 2 Duo E6300
1stick of 1GB Corsair RAM 667mhz (default timings)
Abit AB9 (onboard LAN/audio)
XFX GeForce 7300GT
Western Digital 250GB HD

Please help, and sorry for the long post.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Same applies here

by zio69 In reply to BSOD when turning off/res ...

Got the same problem with a totally different machine: it's an Athlon64/3200+ (939) with 2 512Mb unbranded sticks of memory, Nvidia 6100 chipset w/ integrated VGA. I've tried changing the board, the power supply, memory, I've even tried sticking a video card in it.... I've reinstalled XP, both clean and upgrade: nothing, still giving 0x000050 or 0x00008e at "saving settings" (which ARE saved, btw).

MS kb suggests it may be a virus (HAXDOOR), but Avast, McAfee and Norton ALL report the machine as clean.

The only thing that is left for me to try is... the processor (which isn't easy for 939 are quite scarce and expensive here). It's the most unlikely part.... considering the machine worked pretty well for over 1 year, but it seems that must be the case. I guess it might as well apply to you.

Good luck!

Related Discussions

Related Forums