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: random BSOD 0xc0000005 -fresh Windows 8 x64 install


25 Oct 2011   #1

Windows 7 Home Edition x64
 
 
random BSOD 0xc0000005 -fresh Windows 8 x64 install

Hello,

I am getting BSOD for a few weeks now, before that my PC was working fine. I have not added any new component recently.

I have fully installed the OS (Windows 7 x64) a couple of days ago, but still get BSOD randomly. I don't get any BSOD when I am in safe mode.

I have tried removing some of the ram sticks, running memtest86 for couple of hours (no error found), run disk checks on all hard disks (no errors), tried to remove the GPU (still get crashes).

I have posted the anaylysis of the BSOD, any help is appreciated

Thx


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004a03e51, fffff880097e93f0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
Followup: MachineOwner
---------
0: 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: fffff88004a03e51, Address of the instruction which caused the bugcheck
Arg3: fffff880097e93f0, 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:
+3732313831663533
fffff880`04a03e51 ?? ???
CONTEXT: fffff880097e93f0 -- (.cxr 0xfffff880097e93f0)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002acb0ca to fffff88003c7e7f2
STACK_TEXT:
fffff800`03f94c98 fffff800`02acb0ca : 00000000`0032e5ab fffffa80`051764e8 fffff800`02c45c40 00000000`00000002 : 0xfffff880`03c7e7f2
fffff800`03f94ca0 fffff800`02ac5d5c : fffff800`02c37e80 fffff800`00000000 00000000`00000000 fffff880`03f94db0 : nt!PoIdle+0x53a
fffff800`03f94d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c

FOLLOWUP_IP:
nt!PoIdle+53a
fffff800`02acb0ca 0fba25761518000f bt dword ptr [<Unloaded_Unknown_Module_00000000`00000000>+0x181576 (00000000`00181576)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+53a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
STACK_COMMAND: .cxr 0xfffff880097e93f0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!PoIdle+53a
BUCKET_ID: X64_0x3B_nt!PoIdle+53a
Followup: MachineOwner
---------

My System SpecsSystem Spec
.

25 Oct 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mfrey View Post
Hello,

I am getting BSOD for a few weeks now, before that my PC was working fine. I have not added any new component recently.

I have fully installed the OS (Windows 7 x64) a couple of days ago, but still get BSOD randomly. I don't get any BSOD when I am in safe mode.

I have tried removing some of the ram sticks, running memtest86 for couple of hours (no error found), run disk checks on all hard disks (no errors), tried to remove the GPU (still get crashes).

I have posted the anaylysis of the BSOD, any help is appreciated

Thx


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004a03e51, fffff880097e93f0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
Followup: MachineOwner
---------
0: 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: fffff88004a03e51, Address of the instruction which caused the bugcheck
Arg3: fffff880097e93f0, 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:
+3732313831663533
fffff880`04a03e51 ?? ???
CONTEXT: fffff880097e93f0 -- (.cxr 0xfffff880097e93f0)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002acb0ca to fffff88003c7e7f2
STACK_TEXT:
fffff800`03f94c98 fffff800`02acb0ca : 00000000`0032e5ab fffffa80`051764e8 fffff800`02c45c40 00000000`00000002 : 0xfffff880`03c7e7f2
fffff800`03f94ca0 fffff800`02ac5d5c : fffff800`02c37e80 fffff800`00000000 00000000`00000000 fffff880`03f94db0 : nt!PoIdle+0x53a
fffff800`03f94d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c

FOLLOWUP_IP:
nt!PoIdle+53a
fffff800`02acb0ca 0fba25761518000f bt dword ptr [<Unloaded_Unknown_Module_00000000`00000000>+0x181576 (00000000`00181576)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+53a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
STACK_COMMAND: .cxr 0xfffff880097e93f0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!PoIdle+53a
BUCKET_ID: X64_0x3B_nt!PoIdle+53a
Followup: MachineOwner
---------

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
Reply

 random BSOD 0xc0000005 -fresh Windows 8 x64 install




Thread Tools



Similar help and support threads for2: random BSOD 0xc0000005 -fresh Windows 8 x64 install
Thread Forum
Random BSOD(different error). Fresh install! BSOD Help and Support
Random BSOD after fresh install of Windows 7 on a SSD. BSOD Help and Support
Solved Random BSOD's even after fresh install BSOD Help and Support
Solved BSOD, Random times. Fresh install Windows 7 64 bit. BSOD Help and Support
Random BSOD following fresh install and new motherboard BSOD Help and Support
Random BSOD after a few Hours of a fresh install BSOD Help and Support
Random BSOD - Fresh install, fresh system BSOD Help and Support

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 04:23 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33