BSOD on boot, system exception, page fault

[CelestialScribe]

Hey all,

Whenever I boot my Windows 7 PC, I usually get to the Windows loading screen and then I get hit with a BSOD. The first one I noticed was a PAGE FAULT IN NONPAGED AREA notice. It restarts, then comes up another, it's either the PAGE FAULT IN NONPAGED AREA one, or a SYSTEM SERVICE EXCEPTION error. It's only these two. A few facts:

1. This doesn't occur in safe mode.
2. I've had this hardware for a month, the error did not occur with Windows XP
3. Once I actually get INTO Windows 7, which happens occasionally, the computer is fine for hours.
4. At the bottom of each blue screen, I see something happen called a memory dump, or something like that (it goes away pretty fast), with a percentage ticker.

Doing a bit of Googling tells me the fault could be made by faulty RAM, but I don't believe this to be the case as it is working fine in Safe Mode.

Any help would be greatly appreciated as these blue screens are ticking me off something shocking!

Cheers.

Edit: Sys Specs below.

 

[Capt.Jack Sparrow]

Hey all,

Whenever I boot my Windows 7 PC, I usually get to the Windows loading screen and then I get hit with a BSOD. The first one I noticed was a PAGE FAULT IN NONPAGED AREA notice. It restarts, then comes up another, it's either the PAGE FAULT IN NONPAGED AREA one, or a SYSTEM SERVICE EXCEPTION error. It's only these two. A few facts:

1. This doesn't occur in safe mode.
2. I've had this hardware for a month, the error did not occur with Windows XP
3. Once I actually get INTO Windows 7, which happens occasionally, the computer is fine for hours.
4. At the bottom of each blue screen, I see something happen called a memory dump, or something like that (it goes away pretty fast), with a percentage ticker.

Doing a bit of Googling tells me the fault could be made by faulty RAM, but I don't believe this to be the case as it is working fine in Safe Mode.

Any help would be greatly appreciated as these blue screens are ticking me off something shocking!

Cheers.

Edit: Sys Specs below.

Hi, Welcome to SF,

Could you please post the dump file http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Hope this helps,
Captain

 

[CelestialScribe]

Sure I'll get on that when I get home.

 

[lenlennart]

hi guys,

i do have the very same problem On the first boot, i always get this bluescreen - System Service Exception. I then have to switch the mashine back off and try again... chances are it works...

attached are the last two minidumps...

hope you can help me

Thanks a mill,
Lennart

 

[zigzag3143]

hi guys,

i do have the very same problem On the first boot, i always get this bluescreen - System Service Exception. I then have to switch the mashine back off and try again... chances are it works...

attached are the last two minidumps...

hope you can help me

Thanks a mill,
Lennart

hi and welcome. Both of these were probably caused by memory corruptions. In both there was an illegal instruction made.

I would
download memtestx86 and run it for 5 passes.
rub a system file check
type cmd in search>right click run as admin>sfc /scannow

If you are overclocking stop

let us know the results

Ken

013110-15272-01.dmp    1/31/2010 8:58:50 PM    NTFS_FILE_SYSTEM    0x00000024    00000000`001904fb    fffff880`02347a78    fffff880`023472d0    fffff880`014f6173    Ntfs.sys    Ntfs.sys+c6173                    x64        C:\Users\K\Desktop\013110-15272-01.dmp    4    15    7600    
013110-16005-01.dmp    1/31/2010 9:02:42 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c000001d    fffff880`02db2da7    fffff880`06159ea0    00000000`00000000    bowser.sys    bowser.sys+12da7                    x64        C:\Users\K\Desktop\013110-16005-01.dmp    4    15    7600

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\013110-16005-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Sun Jan 31 14:59:01.893 2010 (GMT-5)
System Uptime: 0 days 0:00:28.298
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff88002db2da7, fffff88006159ea0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff88002db2da7, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006159ea0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
bowser!WriteMailslotEx+13
fffff880`02db2da7 61              ???

CONTEXT:  fffff88006159ea0 -- (.cxr 0xfffff88006159ea0)
rax=fffff8800615a888 rbx=0000000000000000 rcx=fffffa8005ca6240
rdx=fffff8a001b64380 rsi=fffff8a001b64380 rdi=fffffa8005ca6240
rip=fffff88002db2da7 rsp=fffff8800615a888 rbp=fffff8800615aca0
 r8=0000000000000090  r9=fffff88000b6b750 r10=0000000000000000
r11=0000fffffffff000 r12=000000000013004b r13=00000000019cd6e0
r14=0000000000000090 r15=fffffa8005ca63e8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
bowser!WriteMailslotEx+0x13:
fffff880`02db2da7 61              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88002db2da7

STACK_TEXT:  
fffff880`0615a888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : bowser!WriteMailslotEx+0x13


CHKIMG_EXTENSION: !chkimg -lo 50 -db !bowser
16 errors : !bowser (fffff88002db20a7-fffff88002db2da7)
fffff88002db20a0  ff  46  3c  44  8b  c2  4c *a9  44  24  78  33  c0  48  83  c9 .F<D..L.D$x3.H..
...
fffff88002db2320  ff  ff  48  8b  4c  24  28 *c8  8c  21  00  00  8b  d8  eb  14 ..H.L$(..!......
...
fffff88002db23a0  00  00  48  8b  05  57  4d *df  ff  48  33  c4  48  89  84  24 ..H..WM..H3.H..$
...
fffff88002db2420  e8  6b  12  ff  ff  49  d1 *cc  66  42  89  7c  64  60  66  44 .k...I..fB.|d`fD
...
fffff88002db24a0  48  8b  f0  48  89  44  24 *00  48  3b  c7  75  07  bb  34  00 H..H.D$.H;.u..4.
...
fffff88002db2520  48  33  cc  e8  08  11  ff *df  4c  8d  9c  24  80  02  00  00 H3......L..$....
...
fffff88002db25a0  50  01  00  00  41  83  f8 *40  73  0a  bb  0d  00  00  c0  e9 P...A..@s.......
...
fffff88002db2620  7c  64  60  66  44  89  6b *3a  48  8b  43  30  48  89  44  24 |d`fD.k:H.C0H.D$
...
fffff88002db2720  8b  73  48  49  8b  e3  41 *7f  41  5e  41  5d  41  5c  5f  c3 .sHI..A.A^A]A\_.
...
fffff88002db2820  1f  03  00  00  66  3b  46 *08  0f  82  15  03  00  00  48  39 ....f;F.......H9
...
fffff88002db28a0  88  74  24  20  45  89  bc *04  fc  00  00  00  41  39  bc  24 .t$ E.......A9.$
...
fffff88002db2a20  f8  84  ff  ff  8b  d8  89 *64  24  24  b2  01  48  8b  ce  ff .......d$$..H...
...
fffff88002db2b20  24  24  3b  c7  7c  31  b2 *21  48  8b  ce  ff  15  07  25  ff $$;.|1.!H.....%.
...
fffff88002db2ba0  8b  e3  41  5f  41  5e  41 *7d  c3  cc  cc  cc  cc  cc  cc  cc ..A_A^A}........
...
fffff88002db2d20  48  8d  90  b8  03  00  00 *6c  8d  05  32  07  ff  ff  48  8b H......l..2...H.
...
fffff88002db2da0  89  78  18  4c  89  60  20 *61  55  41  56  41  57  48  83  ec .x.L.` aUAVAWH..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88006159ea0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

 

[lenlennart]

memtest86+ ran for 16 loops straight- no errors...

C:\Windows\system32>sfc /scannow

Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern.

Überprüfungsphase der Systemsuche wird gestartet.
Überprüfung 100 % abgeschlossen.

Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden.

that is, no error found...