Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD "Page fault?"


  • Please log in to reply
21 replies to this topic

#1 Spectro

Spectro

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 21 May 2009 - 10:21 PM

I keep getting blue screens but I don't remember what most of them say. I can't remember where the log is. (I'm pretty sure there is one, right?)

I don't know what is causing these. It seems like I just keep going AFK and come back to a BSOD. One of them said something about a "page fault in a non page area", or something like that.

I'm not sure what to do.

BC AdBot (Login to Remove)

 


#2 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 22 May 2009 - 09:59 PM

This can be caused by faulty RAM. You should run a RAM diagnostic test.

http://www.memtest.org/
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#3 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 23 May 2009 - 03:04 PM

This can be caused by faulty RAM. You should run a RAM diagnostic test.

http://www.memtest.org/

I ran it overnight and it didn't find any errors. Is there some kind of log I can post? What next? >_<

#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 23 May 2009 - 06:44 PM

Right click on the C drive in Explorer and go Properties > Tools > Check Now (under Error Checking). Check both boxes then click "Start Now". A message will pop up saying that Error Checking will run after you restart the computer. Restart the computer and Error Checking will run automatically after the restart. After itís finished it will restart into Windows automatically.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#5 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 24 May 2009 - 12:29 PM

Ok, done. Now what?

Also, I should mention that I got a message saying that the "system recovered from a serious error". I'm thinking more and more that this is a hardware issue, but I don't know yet.

Edited by Spectro, 24 May 2009 - 12:30 PM.


#6 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 24 May 2009 - 04:22 PM

It may be a hardware issue, but there are some things we can look into.

Have a look in the Event Viewer for the error-checking log.

To open the Event Viewer go to Start > Control Panel > Administrative Tools > Event Viewer. Alternately, go to Start > Run and type in "eventvwr.msc" (without the quotes) and press Enter. Look for an entry called "winlogon" under Application.


Also, check your devices in Device Manager (Start > Run > type "devmgmt.msc" (without the quotes) and press Enter). Look for any "!", "?" or "X" symbols.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#7 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 25 May 2009 - 03:50 AM

There are several entries for "winlogon" and there has been a "?" for "Other devices" in device manager since my friend bult the PC. Under "Other devices" is "Audio Device on High Definition Audio Bus".

Also, I've found out that my computer crashes when I turn off my monitor.

#8 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 25 May 2009 - 04:06 PM

Did the error checking log find any problems/bad sectors on the hard drive?

Right click on the ? device in the Device Manager and select Properties, then click on the Details tab, then on Hardware ID in the dropdown box. It look something like this:

PCI\VEN_4444&DEV_0016&SUBSYS_40090070&REV_01

Post back what you find.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#9 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 25 May 2009 - 05:09 PM

I don't know if it found any errors/bad sectors because I ran it overnight and when I woke up it was done. Where do I check the log?

HDAUDIO\FUNC_01&VEN_10DE&DEV_0002&SUBSYS_10DE0101&REV_1000\4&12D5E64F&0&0301

Edited by Spectro, 25 May 2009 - 05:10 PM.


#10 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 25 May 2009 - 05:14 PM

The log will be in the winlogon entry in the event viewer for that time.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#11 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 25 May 2009 - 06:52 PM

Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk.                         Cleaning up 1 unused index entries from index $SII of file 0x9.Cleaning up 1 unused index entries from index $SDH of file 0x9.Cleaning up 1 unused security descriptors.CHKDSK is verifying Usn Journal...Usn Journal verification completed.CHKDSK is verifying file data (stage 4 of 5)...File data verification completed.CHKDSK is verifying free space (stage 5 of 5)...Free space verification is complete. 488375968 KB total disk space.  32963064 KB in 28097 files.      7896 KB in 2154 indexes.         0 KB in bad sectors.    134320 KB in use by the system.     65536 KB occupied by the log file. 455270688 KB available on disk.      4096 bytes in each allocation unit. 122093992 total allocation units on disk. 113817672 allocation units available on disk.Internal Info:90 76 00 00 37 76 00 00 60 99 00 00 00 00 00 00  .v..7v..`.......54 00 00 00 02 00 00 00 1a 01 00 00 00 00 00 00  T...............60 34 3c 02 00 00 00 00 80 2b 53 0b 00 00 00 00  `4<......+S.....28 c5 50 03 00 00 00 00 6e be 06 f9 00 00 00 00  (.P.....n.......ea 68 f7 41 0a 00 00 00 16 56 62 53 0b 00 00 00  .h.A.....VbS....99 9e 36 00 00 00 00 00 88 38 07 00 c1 6d 00 00  ..6......8...m..00 00 00 00 00 e0 e7 db 07 00 00 00 6a 08 00 00  ............j...Windows has finished checking your disk.Please wait while your computer restarts.For more information, see Help and Support Center at [url="http://go.microsoft.com/fwlink/events.asp"]http://go.microsoft.com/fwlink/events.asp[/url].


#12 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 25 May 2009 - 06:59 PM

The CHKDSK log looks okay and I can't find any information on that Hardware ID.

Are there any errors in the Event Viewer which occur at the time of the crashes?
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#13 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 25 May 2009 - 07:30 PM

Error code 1000007e, parameter1 c0000005, parameter2 6d665346, parameter3 b8517c10, parameter4 b851790c.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

#14 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:59 AM

Posted 25 May 2009 - 07:41 PM

Try running through the steps given here:

http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#15 Spectro

Spectro
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Michigan
  • Local time:05:59 PM

Posted 25 May 2009 - 08:02 PM

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini052509-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 XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.090206-1316
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon May 25 18:28:58.140 2009 (GMT-4)
System Uptime: 0 days 0:26:36.120
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 0, b850bc10, b850b90c}

Probably caused by : nv4_mini.sys ( nv4_mini+3b830f )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: b850bc10, Exception Record Address
Arg4: b850b90c, Context Record Address

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


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

FAULTING_IP:
+16
00000000 ?? ???

EXCEPTION_RECORD: b850bc10 -- (.exr 0xffffffffb850bc10)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: b850b90c -- (.cxr 0xffffffffb850b90c)
eax=b850bcf4 ebx=8a3c1750 ecx=b850bd24 edx=b850bd2c esi=00000000 edi=8a3c2008
eip=00000000 esp=b850bcd8 ebp=8a3ae000 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 00000000

WRITE_ADDRESS: 00000000

FOLLOWUP_IP:
nv4_mini+3b830f
b740a30f ?? ???

FAILED_INSTRUCTION_ADDRESS:
+28b952f017bdfdc
00000000 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from b740a30f to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b850bcd4 b740a30f 8a3c1750 8a3c2008 b850bcf4 0x0
b850bd68 80576ad5 8a421288 88f48cb0 8056485c nv4_mini+0x3b830f
b850bd7c 8053877d 8a438e10 00000000 8a66e640 nt!IopProcessWorkItem+0x13
b850bdac 805cffa0 8a438e10 00000000 00000000 nt!ExpWorkerThread+0xef
b850bddc 805460ee 8053868e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nv4_mini+3b830f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49fa9709

STACK_COMMAND: .cxr 0xffffffffb850b90c ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_nv4_mini+3b830f

BUCKET_ID: 0x7E_NULL_IP_nv4_mini+3b830f

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: b850bc10, Exception Record Address
Arg4: b850b90c, Context Record Address

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


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

FAULTING_IP:
+16
00000000 ?? ???

EXCEPTION_RECORD: b850bc10 -- (.exr 0xffffffffb850bc10)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: b850b90c -- (.cxr 0xffffffffb850b90c)
eax=b850bcf4 ebx=8a3c1750 ecx=b850bd24 edx=b850bd2c esi=00000000 edi=8a3c2008
eip=00000000 esp=b850bcd8 ebp=8a3ae000 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 00000000

WRITE_ADDRESS: 00000000

FOLLOWUP_IP:
nv4_mini+3b830f
b740a30f ?? ???

FAILED_INSTRUCTION_ADDRESS:
+28b952f017bdfdc
00000000 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from b740a30f to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b850bcd4 b740a30f 8a3c1750 8a3c2008 b850bcf4 0x0
b850bd68 80576ad5 8a421288 88f48cb0 8056485c nv4_mini+0x3b830f
b850bd7c 8053877d 8a438e10 00000000 8a66e640 nt!IopProcessWorkItem+0x13
b850bdac 805cffa0 8a438e10 00000000 00000000 nt!ExpWorkerThread+0xef
b850bddc 805460ee 8053868e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nv4_mini+3b830f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49fa9709

STACK_COMMAND: .cxr 0xffffffffb850b90c ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_nv4_mini+3b830f

BUCKET_ID: 0x7E_NULL_IP_nv4_mini+3b830f

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: b850bc10, Exception Record Address
Arg4: b850b90c, Context Record Address

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


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

FAULTING_IP:
+16
00000000 ?? ???

EXCEPTION_RECORD: b850bc10 -- (.exr 0xffffffffb850bc10)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: b850b90c -- (.cxr 0xffffffffb850b90c)
eax=b850bcf4 ebx=8a3c1750 ecx=b850bd24 edx=b850bd2c esi=00000000 edi=8a3c2008
eip=00000000 esp=b850bcd8 ebp=8a3ae000 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 00000000

WRITE_ADDRESS: 00000000

FOLLOWUP_IP:
nv4_mini+3b830f
b740a30f ?? ???

FAILED_INSTRUCTION_ADDRESS:
+28b952f017bdfdc
00000000 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from b740a30f to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b850bcd4 b740a30f 8a3c1750 8a3c2008 b850bcf4 0x0
b850bd68 80576ad5 8a421288 88f48cb0 8056485c nv4_mini+0x3b830f
b850bd7c 8053877d 8a438e10 00000000 8a66e640 nt!IopProcessWorkItem+0x13
b850bdac 805cffa0 8a438e10 00000000 00000000 nt!ExpWorkerThread+0xef
b850bddc 805460ee 8053868e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nv4_mini+3b830f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49fa9709

STACK_COMMAND: .cxr 0xffffffffb850b90c ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_nv4_mini+3b830f

BUCKET_ID: 0x7E_NULL_IP_nv4_mini+3b830f

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




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users