Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on new build

27 May 2011   #11
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

The cause is 0x1E_c0000005
A memory access violation occurred.


Code:
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000102e7c377, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000102e7c377, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
+6533393064336239
00000001`02e7c377 ??              ???
EXCEPTION_PARAMETER1:  0000000000000008
EXCEPTION_PARAMETER2:  0000000102e7c377
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b8100
 0000000102e7c377 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  1
TRAP_FRAME:  fffff88005ecb880 -- (.trap 0xfffff88005ecb880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=2104d017243c0000
rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000
rip=0000000102e7c377 rsp=fffff88005ecba10 rbp=0000000000000000
 r8=fffff880009e7180  r9=fffff880009e7180 r10=0000000000000100
r11=fffff80003038240 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
00000001`02e7c377 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ed45d8 to fffff80002e88d00
STACK_TEXT:  
fffff880`05ecaff8 fffff800`02ed45d8 : 00000000`0000001e ffffffff`c0000005 00000001`02e7c377 00000000`00000008 : nt!KeBugCheckEx
fffff880`05ecb000 fffff800`02e88382 : fffff880`05ecb7d8 fffffa80`05fbbb60 fffff880`05ecb880 fffffa80`05fbbbb0 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`05ecb6a0 fffff800`02e86efa : 00000000`00000008 00000001`02e7c377 fffffa80`059a2500 fffffa80`05fbbb60 : nt!KiExceptionDispatch+0xc2
fffff880`05ecb880 00000001`02e7c377 : fffffa80`05fbbb00 00000000`00000000 fffffa80`00000000 00001f80`00000000 : nt!KiPageFault+0x23a
fffff880`05ecba10 fffffa80`05fbbb00 : 00000000`00000000 fffffa80`00000000 00001f80`00000000 fffff880`05ecbaa8 : 0x1`02e7c377
fffff880`05ecba18 00000000`00000000 : fffffa80`00000000 00001f80`00000000 fffff880`05ecbaa8 fffff800`030bb8c0 : 0xfffffa80`05fbbb00
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4987d
fffff800`02ed45d8 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4987d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!_??_::FNODOBFM::_string_+4987d
BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!_??_::FNODOBFM::_string_+4987d
Followup: MachineOwner
---------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Enable Driver Verifier
Driver Verifier - Enable and Disable
Run system normally, when it crashes post the files here.
Code:
 
Event[28742]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-05-16T19:53:19.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DAVEQUADCORE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xfffff88002f2aca8, 0x0000000000000002, 0x0000000000000001, 0xfffff80002d08c22). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 051611-20436-01.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
This bug check is usually caused by drivers that have used improper addresses.
Code:
Event[29109]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-05-16T19:46:17.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DaveQuadcore-PC
Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000008, 0x0000000000000002, 0x0000000000000000, 0xfffff88000f0d5c2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 


Code:
 
Event[31291]:
  Log Name: System
  Source: Disk
  Date: 2011-05-16T18:34:51.649
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR1.
Run System File Checker:
How to Repair Windows 7 System Files with System File Checker


My System SpecsSystem Spec
.
27 May 2011   #12
Reubenb04

Windows 7 Ultimate x64
 
 

Hi,

I've run SFC and it has come back clean. Am also currently running Driver Verifier in the background and if there is another BSOD, I will upload the files.

Could the memory access violation be as a result of running Ram Disk?

thanks.
My System SpecsSystem Spec
28 May 2011   #13
Reubenb04

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Dave76 View Post
The cause is 0x1E_c0000005
A memory access violation occurred.


Code:
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000102e7c377, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000102e7c377, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
+6533393064336239
00000001`02e7c377 ??              ???
EXCEPTION_PARAMETER1:  0000000000000008
EXCEPTION_PARAMETER2:  0000000102e7c377
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b8100
 0000000102e7c377 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  1
TRAP_FRAME:  fffff88005ecb880 -- (.trap 0xfffff88005ecb880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=2104d017243c0000
rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000
rip=0000000102e7c377 rsp=fffff88005ecba10 rbp=0000000000000000
 r8=fffff880009e7180  r9=fffff880009e7180 r10=0000000000000100
r11=fffff80003038240 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
00000001`02e7c377 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ed45d8 to fffff80002e88d00
STACK_TEXT:  
fffff880`05ecaff8 fffff800`02ed45d8 : 00000000`0000001e ffffffff`c0000005 00000001`02e7c377 00000000`00000008 : nt!KeBugCheckEx
fffff880`05ecb000 fffff800`02e88382 : fffff880`05ecb7d8 fffffa80`05fbbb60 fffff880`05ecb880 fffffa80`05fbbbb0 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`05ecb6a0 fffff800`02e86efa : 00000000`00000008 00000001`02e7c377 fffffa80`059a2500 fffffa80`05fbbb60 : nt!KiExceptionDispatch+0xc2
fffff880`05ecb880 00000001`02e7c377 : fffffa80`05fbbb00 00000000`00000000 fffffa80`00000000 00001f80`00000000 : nt!KiPageFault+0x23a
fffff880`05ecba10 fffffa80`05fbbb00 : 00000000`00000000 fffffa80`00000000 00001f80`00000000 fffff880`05ecbaa8 : 0x1`02e7c377
fffff880`05ecba18 00000000`00000000 : fffffa80`00000000 00001f80`00000000 fffff880`05ecbaa8 fffff800`030bb8c0 : 0xfffffa80`05fbbb00
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4987d
fffff800`02ed45d8 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4987d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!_??_::FNODOBFM::_string_+4987d
BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!_??_::FNODOBFM::_string_+4987d
Followup: MachineOwner
---------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Enable Driver Verifier
Driver Verifier - Enable and Disable
Run system normally, when it crashes post the files here.
Code:
 
Event[28742]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-05-16T19:53:19.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DAVEQUADCORE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xfffff88002f2aca8, 0x0000000000000002, 0x0000000000000001, 0xfffff80002d08c22). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 051611-20436-01.
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
This bug check is usually caused by drivers that have used improper addresses.
Code:
Event[29109]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-05-16T19:46:17.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DaveQuadcore-PC
Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000008, 0x0000000000000002, 0x0000000000000000, 0xfffff88000f0d5c2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 
Code:
 
Event[31291]:
  Log Name: System
  Source: Disk
  Date: 2011-05-16T18:34:51.649
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR1.
Run System File Checker:
How to Repair Windows 7 System Files with System File Checker

Hello Dave76,
I have been running driver verifier for the last 20hrs and at start up, i got another BSOD.
As requested, i have attached the new crash files.

cheers.
My System SpecsSystem Spec
.

28 May 2011   #14
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Disable your Ram Disk, for testing purposes, you can use it again later after the cause is found.

The same cause as before 0x1E_c0000005
A memory access violation occurred.
No specific driver has been indicated.

Run a Disk Check on your drive.

Remove any browser toolbars, for testing purposes.
Code:
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000102ece377, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000102ece377, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
+6631313764313063
00000001`02ece377 ??              ???
EXCEPTION_PARAMETER1:  0000000000000008
EXCEPTION_PARAMETER2:  0000000102ece377
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
 0000000102ece377 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  1
TRAP_FRAME:  fffff880033b3880 -- (.trap 0xfffff880033b3880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=1ea79912c8bb0000
rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000
rip=0000000102ece377 rsp=fffff880033b3a10 rbp=0000000000000000
 r8=fffff8000304de80  r9=fffff8000304de80 r10=0000000000000100
r11=fffff8000308a240 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
00000001`02ece377 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002f265d8 to fffff80002edad00
STACK_TEXT:  
fffff880`033b2ff8 fffff800`02f265d8 : 00000000`0000001e ffffffff`c0000005 00000001`02ece377 00000000`00000008 : nt!KeBugCheckEx
fffff880`033b3000 fffff800`02eda382 : fffff880`033b37d8 fffffa80`05b2e040 fffff880`033b3880 fffffa80`05b2e090 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`033b36a0 fffff800`02ed8efa : 00000000`00000008 00000001`02ece377 fffffa80`05aad700 fffffa80`05b2e040 : nt!KiExceptionDispatch+0xc2
fffff880`033b3880 00000001`02ece377 : fffffa80`05b2e000 00000000`00000000 fffffa80`00000000 00001f80`00000000 : nt!KiPageFault+0x23a
fffff880`033b3a10 fffffa80`05b2e000 : 00000000`00000000 fffffa80`00000000 00001f80`00000000 fffff880`033b3aa8 : 0x1`02ece377
fffff880`033b3a18 00000000`00000000 : fffffa80`00000000 00001f80`00000000 fffff880`033b3aa8 fffff800`0310d8c0 : 0xfffffa80`05b2e000
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4987d
fffff800`02f265d8 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4987d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!_??_::FNODOBFM::_string_+4987d
BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!_??_::FNODOBFM::_string_+4987d
Followup: MachineOwner
---------
Are you using or trying to use Windows Backup?
Event[511]:
Code:
 Log Name: Application
  Source: MsiInstaller
  Date: 2011-05-27T13:14:26.000
  Event ID: 1015
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: S-1-5-21-3485215416-4126433605-2575317891-1000
  User Name: DaveQuadcore-PC\Dave Quadcore
  Computer: DaveQuadcore-PC
  Description: 
Failed to connect to server. Error: 0x8007043C
Code:
26/05/2011 20:36 Application Error Faulting application name: avast.setup, version: 5.0.0.0, time stamp: 0x4dc92ebc
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000374
Fault offset: 0x000ce653
Faulting process id: 0xb00
Faulting application start time: 0x01cc1be46faffcf0
Faulting application path: C:\Program Files\AVAST Software\Avast\setup\avast.setup
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: d3135527-87d7-11e0-916c-001d7d9d4784
Looks like Avast was causing a problem.

Run a full scan with your AntiVirus.

Download and run Malwarebytes, be sure to update it before running.


Let us know how the tests go, and if you have any questions.
My System SpecsSystem Spec
Reply

 BSOD on new build




Thread Tools




Similar help and support threads
Thread Forum
BSOD After New System Build, Many Different Types of BSOD Errors.
I had been getting BSODs on an older custom PC so I decided it was time to upgrade and I recently put together a new system and have been having irregular BSOD errors since day 1. I initially thought that it was the RAM because that was the only other part besides the hard drives that was recycled...
BSOD Help and Support
BSOD - New PC Build
Hi all, Appreciate the level of detail you go in providing the tool to take all the relevant info and the support you give back, Many thanks. So I had a Dell XPS 700 which died and therein i learnt it wasn't really upgradable so went to NovaTech and purchased the necessary components to...
BSOD Help and Support
Can I install Icon Packs designed for Build 7600 on to Build 7601?
Can I install Icon Packs designed for Build 7600 to Build 7601? An Icon Pack was saying install on to 7600 only and after I checked my regedit, I learned that I have 7601 (Probably SP1, I don't know). Would I have any problems if I install the icon pack? Thanks.
Customization
New Build BSOD
Hi there, I have been trying to work through this problem with another forum but have so far not had much luck. So I want to start afresh with a new team. I built my own PC Intel Core i7 870 Lynnfield 2.93GHz 8MB ASUS P7P55D-E LX DDR3 LGA1156 SATA3+USB3 ATX OCZ Intel Extreme Series 2x2GB...
BSOD Help and Support
New Build PC BSOD
Hi All I built a new PC a couple of days ago. OS: Windows Home Premium 64 bit (I now know I have to upgrade this to utilize 24Gb RAM) CPU: i7-980X Extreme Edition MOBO: ASUS P6X58D-E RAM: Corsair XMS (6x4Gb) CMX4GX3M1A1333C9 VID: Gigabyte GTX480 HD: Crucial RealSSD 128Gb (2x128GB) ...
BSOD Help and Support
Windows 7 Build 7012 Screenshots Emerged & Build 7013 Details
Windows 7 Build 7012 Screenshots Emerged & Build 7013 Details http://www.blogsdna.com/wp-content/uploads/2008/12/windows-7-logo.jpg We all are waiting for Windows 7 Beta 1 build 7000 to get release but it seems some one out their already have access to Windows 7 Build 7012. Here is...
News


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:46.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App