Go Back   AnandTech Forums > Hardware and Technology > Computer Help

Forums
· Hardware and Technology
· CPUs and Overclocking
· Motherboards
· Video Cards and Graphics
· Memory and Storage
· Power Supplies
· Cases & Cooling
· SFF, Notebooks, Pre-Built/Barebones PCs
· Networking
· Peripherals
· General Hardware
· Highly Technical
· Computer Help
· Home Theater PCs
· Consumer Electronics
· Digital and Video Cameras
· Mobile Devices & Gadgets
· Audio/Video & Home Theater
· Software
· Software for Windows
· All Things Apple
· *nix Software
· Operating Systems
· Programming
· PC Gaming
· Console Gaming
· Distributed Computing
· Security
· Social
· Off Topic
· Politics and News
· Discussion Club
· Love and Relationships
· The Garage
· Health and Fitness
· Merchandise and Shopping
· For Sale/Trade
· Hot Deals
· Free Stuff
· Contests and Sweepstakes
· Black Friday 2013
· Forum Issues
· Technical Forum Issues
· Personal Forum Issues
· Suggestion Box
· Moderator Resources
· Moderator Discussions
   

Reply
 
Thread Tools
Old 07-30-2011, 07:41 AM   #1
Mr.Nicklebe
Junior Member
 
Join Date: Jul 2011
Posts: 8
Default BSOD - PAGE_FAULT_IN_NONPAGED_AREA - ntoskrnl.exe

Hi guys I've been having some major problems with my PC over the last few days. I've been getting a mixture of system freezes, BSODS, random restarts when under full load (playing games of rendering 3D projects).

I reformatted my hard drives as I thought it was an error with them but that hasn't fixed it. I also ran memtest86+ for 2 passes which found no errors. I ran Seagate Hard drive scanner which found no errors on either of my Seagate drives.

I downloaded BlueScreenView to check out what the BSODS were from and it showed ntoskrnl.exe is at fault.

I can't seem to attach my minidump file so here's the the BlueScreenView BSOD text file I saved of the error:

Code:
==================================================
Dump File         : 073011-20248-01.dmp
Crash Time        : 30/07/2011 13:12:38
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff004`0000c080
Parameter 2       : 00000000`00000008
Parameter 3       : fffff004`0000c080
Parameter 4       : 00000000`00000007
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor         : x64
Crash Address     : ntoskrnl.exe+70700
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\073011-20248-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 284,296
==================================================
Oh and I ran Prime95's torture test which crashed my machine after a minute or two. So I'm fairly sure it's CPU, PSU, or Motherboard problem.

EDIT:

My system specs:

Windows 7 Professional 64Bit
AMD Phenom II X4 955 3.2Ghz
Asus M4A79XTD EVO 790X Motherboard
Corsair 8GB DDR3 1333MHz RAM
Gigabyte Nvidia GTX470 1280MB GDDR5 Graphics Card
1x Seagate ST3250620AS 250GB SATAII/300 7200RPM 16MB Cache (Very old drive)
1x Seagate ST3500320AS 500GB Hard Drive SATA II 7200rpm 32MB Cache (Not quite as old, but still old drive)
600w Solytech SL-8600EPS PSU

Last edited by Mr.Nicklebe; 08-02-2011 at 07:37 AM. Reason: Added system specs.
Mr.Nicklebe is offline   Reply With Quote
Old 07-30-2011, 09:47 AM   #2
denis280
Platinum Member
 
denis280's Avatar
 
Join Date: Jan 2011
Location: Shawinigan Québec Canada
Posts: 2,480
Default

Ok Most of the time reformat do the trick.but boot with cd and do a repair.sorry dint see that you did a prime test.are you overclock.if yes put it default.then remove rams and run them one by one.

Last edited by denis280; 07-30-2011 at 09:54 AM.
denis280 is offline   Reply With Quote
Old 07-30-2011, 10:20 AM   #3
Mr.Nicklebe
Junior Member
 
Join Date: Jul 2011
Posts: 8
Default

Quote:
Originally Posted by denis280 View Post
Ok Most of the time reformat do the trick.but boot with cd and do a repair.sorry dint see that you did a prime test.are you overclock.if yes put it default.then remove rams and run them one by one.
I reformatted but that didn't fix it. I also tried the repair function before that which didn't do the trick either. I'm not an overclocker and I have a lot of fan based cooling so I don't think it's a heat problem.

I did do memtest86+ which showed no errors after 2 passes on my RAM but I will try what you mentioned about the RAM sticks.
Mr.Nicklebe is offline   Reply With Quote
Old 07-30-2011, 10:26 PM   #4
Ultralight
Senior Member
 
Ultralight's Avatar
 
Join Date: Jul 2004
Posts: 982
Default

Blue Screen View is okay but reading the actual minidump with WinDebugger is a much better way to do it. Unfortunately these forums don't allow attachments.

The unwritten rule on Memtest is a minimum of 7 Passes and the more beyond 7 the better.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).
__________________
I'd rather be trout fishing in Pennsylvania.
Ultralight is offline   Reply With Quote
Old 08-01-2011, 12:32 PM   #5
Mr.Nicklebe
Junior Member
 
Join Date: Jul 2011
Posts: 8
Default

Update:

I ran memtest again for 6 passes over night and still got no errors. So not entirely convinced it's a memory problem.

I didn't get any BSOD's over the last few days but today I've been getting some different BSOD messages:

Code:
==================================================
Dump File         : 080111-27752-01.dmp
Crash Time        : 01/08/2011 12:11:18
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`02c6cbd1
Parameter 3       : fffff880`09eba070
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor         : x64
Crash Address     : ntoskrnl.exe+7fd00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 289,312
==================================================
And this one:

Code:
==================================================
Dump File         : 080111-28657-01.dmp
Crash Time        : 01/08/2011 12:16:27
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 00000000`001904fb
Parameter 2       : fffff880`0a2a0798
Parameter 3       : fffff880`0a29fff0
Parameter 4       : fffff880`012c3c11
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+b0c11
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7fd00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 283,736
==================================================
The second one seems like it's pointing to a hard drive error? Although Seagates HDD scanner detected no errors on either of my Seagate drives

I did also take a look a the minidumps with Windows Debugger. If anyone wants me to paste in the text dumps from that I can too.

Thanks again for any help!
Mr.Nicklebe is offline   Reply With Quote
Old 08-01-2011, 08:53 PM   #6
Ultralight
Senior Member
 
Ultralight's Avatar
 
Join Date: Jul 2004
Posts: 982
Default

Yes, paste the WinDebugger info. Do you only get these BSODs when playing games or rendering 3D projects?
__________________
I'd rather be trout fishing in Pennsylvania.
Ultralight is offline   Reply With Quote
Old 08-02-2011, 07:31 AM   #7
Mr.Nicklebe
Junior Member
 
Join Date: Jul 2011
Posts: 8
Default

Quote:
Originally Posted by Ultralight View Post
Yes, paste the WinDebugger info. Do you only get these BSODs when playing games or rendering 3D projects?
I originally thought it was only when I was under full load. But now the crashes are fairly random. I might be loading a web page or doing nothing at all and it'll BSOD.

Here are the windeugger text things:

Code:
Loading Dump File [C:\Windows\Minidump\073011-20248-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Sat Jul 30 13:11:12.636 2011 (UTC + 1:00)
System Uptime: 0 days 0:28:34.368
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff0040000c080, 8, fffff0040000c080, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40dcb )

Followup: MachineOwner
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff0040000c080, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff0040000c080, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef50e0
 fffff0040000c080 

FAULTING_IP: 
+3562336166386461
fffff004`0000c080 ??              ???

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a4a5770 -- (.trap 0xfffff8800a4a5770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff0040000c080 rbx=0000000000000000 rcx=fffffa80074ac060
rdx=0000000000000678 rsi=0000000000000000 rdi=0000000000000000
rip=fffff0040000c080 rsp=fffff8800a4a5908 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80092d6910
r11=fffff8800a4a5890 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff004`0000c080 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d3c959 to fffff80002cbd700

STACK_TEXT:  
fffff880`0a4a5608 fffff800`02d3c959 : 00000000`00000050 fffff004`0000c080 00000000`00000008 fffff880`0a4a5770 : nt!KeBugCheckEx
fffff880`0a4a5610 fffff800`02cbb7ee : 00000000`00000008 fffffa80`074ac060 00000000`80002700 fffff880`0a4a5928 : nt! ?? ::FNODOBFM::`string'+0x40dcb
fffff880`0a4a5770 fffff004`0000c080 : fffff800`02f7a4ed fffffa80`074ac060 00000000`00000001 fffffa80`074ac060 : nt!KiPageFault+0x16e
fffff880`0a4a5908 fffff800`02f7a4ed : fffffa80`074ac060 00000000`00000001 fffffa80`074ac060 00000000`00000000 : 0xfffff004`0000c080
fffff880`0a4a5910 fffff800`02fa1850 : 00000000`7efad000 fffff880`0a4a5c20 00000000`00000000 fffffa80`0910bd50 : nt!PspExitProcess+0x19d
fffff880`0a4a5970 fffff800`02f7b5bd : 00000000`c0000005 00000000`00000001 00000000`7efad000 fffffa80`0731ab60 : nt!PspExitThread+0x834
fffff880`0a4a5a30 fffff800`02c9a16b : 00000000`0a4a5ca0 fffffa80`0947fea0 00000000`0123e720 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`0a4a5a60 fffff800`02c9a5b0 : 00000000`0229fa78 fffff880`0a4a5ae0 fffff800`02f7b6cc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0a4a5ae0 fffff800`02cbc9f7 : fffffa80`09e8b760 00000000`7efad000 fffff880`000000c0 00000000`7efad000 : nt!KiInitiateUserApc+0x70
fffff880`0a4a5c20 00000000`77580fba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0123e6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77580fba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40dcb
fffff800`02d3c959 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+40dcb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40dcb

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40dcb

Followup: MachineOwner
---------
Code:
Loading Dump File [C:\Windows\Minidump\080111-27752-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e62650
Debug session time: Mon Aug  1 12:09:45.649 2011 (UTC + 1:00)
System Uptime: 0 days 0:53:00.210
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c6cbd1, fffff88009eba070, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnResourceQuota+51 )

Followup: MachineOwner
---------

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

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!PspReturnResourceQuota+51
fffff800`02c6cbd1 488910          mov     qword ptr [rax],rdx

CONTEXT:  fffff88009eba070 -- (.cxr 0xfffff88009eba070)
rax=0000000000000000 rbx=fffff80002e441d8 rcx=0000000000000001
rdx=0000000000000005 rsi=0000000000000001 rdi=fffffa80095db100
rip=fffff80002c6cbd1 rsp=fffff88009ebaa50 rbp=fffff8a0011d60e0
 r8=fffff8a0011d60e0  r9=0000000000000001 r10=fffffa80095db080
r11=fffff80002e22900 r12=0000000000000001 r13=0000000000000000
r14=fffff8a00a6b50a0 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!PspReturnResourceQuota+0x51:
fffff800`02c6cbd1 488910          mov     qword ptr [rax],rdx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Azureus.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fd1147 to fffff80002c6cbd1

STACK_TEXT:  
fffff880`09ebaa50 fffff800`02fd1147 : fffffa80`095db000 fffff8a0`0a6b50c0 fffffa80`095db140 00000000`00000005 : nt!PspReturnResourceQuota+0x51
fffff880`09ebaa90 fffff800`02ca6b1c : fffffa80`095db080 00000000`00000000 fffffa80`071cd370 fffffa80`06acb080 : nt! ?? ::NNGAKEGL::`string'+0x14cba
fffff880`09ebaae0 fffff800`02f93614 : fffffa80`071cd370 00000000`00000000 fffffa80`07afb060 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`09ebab40 fffff800`02f93bc4 : 00000000`00000058 fffffa80`071cd370 fffff8a0`099587d0 00000000`00000058 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`09ebabd0 fffff800`02c9bf93 : fffffa80`07afb060 fffff880`09ebaca0 00000000`7eef3000 00000000`00000004 : nt!ObpCloseHandle+0x94
fffff880`09ebac20 00000000`776b140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`072de808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776b140a


FOLLOWUP_IP: 
nt!PspReturnResourceQuota+51
fffff800`02c6cbd1 488910          mov     qword ptr [rax],rdx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!PspReturnResourceQuota+51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

STACK_COMMAND:  .cxr 0xfffff88009eba070 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!PspReturnResourceQuota+51

BUCKET_ID:  X64_0x3B_nt!PspReturnResourceQuota+51

Followup: MachineOwner
---------
Code:
Loading Dump File [C:\Windows\Minidump\080111-28657-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02ea6650
Debug session time: Mon Aug  1 12:14:43.020 2011 (UTC + 1:00)
System Uptime: 0 days 0:03:56.581
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800a2a0798, fffff8800a29fff0, fffff880012c3c11}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )

Followup: MachineOwner
---------

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800a2a0798
Arg3: fffff8800a29fff0
Arg4: fffff880012c3c11

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


EXCEPTION_RECORD:  fffff8800a2a0798 -- (.exr 0xfffff8800a2a0798)
ExceptionAddress: fffff880012c3c11 (Ntfs!NtfsFindPrefix+0x0000000000000121)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800a29fff0 -- (.cxr 0xfffff8800a29fff0)
rax=fffff8a003dce7e4 rbx=fffff8a002b99b28 rcx=000000000000004d
rdx=0000000000000055 rsi=fffff8a0002b4140 rdi=fffff8a002b99b18
rip=fffff880012c3c11 rsp=fffff8800a2a09d0 rbp=fffff8800a2a0c50
 r8=0000000000000000  r9=05c2120526d00508 r10=fffff8800a2a0a30
r11=fffff8800a2a0a10 r12=fffffa8006c71e40 r13=0000000000000000
r14=0000000000000000 r15=fffff880099150a8
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!NtfsFindPrefix+0x121:
fffff880`012c3c11 410fb709        movzx   ecx,word ptr [r9] ds:002b:05c21205`26d00508=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f10100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsFindPrefix+121
fffff880`012c3c11 410fb709        movzx   ecx,word ptr [r9]

FAULTING_IP: 
Ntfs!NtfsFindPrefix+121
fffff880`012c3c11 410fb709        movzx   ecx,word ptr [r9]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880012bb264 to fffff880012c3c11

STACK_TEXT:  
fffff880`0a2a09d0 fffff880`012bb264 : fffffa80`06c71e40 fffff8a0`002b4140 fffff880`09915088 fffff880`0a2a0c18 : Ntfs!NtfsFindPrefix+0x121
fffff880`0a2a0a80 fffff880`012b8911 : fffffa80`06c71e40 fffffa80`088fc420 fffff880`0a2a0c50 fffff880`0a2a0ca0 : Ntfs!NtfsFindStartingNode+0x6e4
fffff880`0a2a0b50 fffff880`01221a3d : fffffa80`06c71e40 fffffa80`088fc420 fffff880`09915020 fffffa80`07079900 : Ntfs!NtfsCommonCreate+0x3e1
fffff880`0a2a0d30 fffff800`02cd8817 : fffff880`09914f90 05b4026c`080589d4 500805f2`1f052691 05a40803`200595ee : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0a2a0d60 fffff800`02cd87d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`09914e60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsFindPrefix+121

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff8800a29fff0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+121

BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+121

Followup: MachineOwner
---------
The programs that are causing the crashes seem fairly random too? What would this point to? Hardware or software problems?

I also added my system specs to my original post too, if that helps.

Last edited by Mr.Nicklebe; 08-02-2011 at 07:38 AM.
Mr.Nicklebe is offline   Reply With Quote
Old 08-02-2011, 09:43 PM   #8
Ultralight
Senior Member
 
Ultralight's Avatar
 
Join Date: Jul 2004
Posts: 982
Default

Okay, let's start with the 0x3B error because they are usually caused by faulty video drivers. If you haven't already then update these drivers.
__________________
I'd rather be trout fishing in Pennsylvania.
Ultralight is offline   Reply With Quote
Old 08-03-2011, 11:05 AM   #9
Saithegeek
Member
 
Join Date: May 2011
Posts: 27
Default

Check for swollen capacitors on your motherboard. I've seen a system that acted this same exact way and it was the motherboard.
Saithegeek is offline   Reply With Quote
Reply

Tags
bsod, ntoskrnl.exe

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -5. The time now is 01:55 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.