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 ntoskrnl.exe +75bc0

24 Jan 2014   #1
tompus

Windows 7 Ultimate x64 SP1
 
 
BSOD ntoskrnl.exe +75bc0

My system has been BSOD randomly for 3-4 months.
Would be grateful if someone can help me. SF diagnostic log attached.


My System SpecsSystem Spec
.
24 Jan 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_tompus\SF_24-01-2014\011114-18891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0320b000 PsLoadedModuleList = 0xfffff800`0344e6d0
Debug session time: Sun Jan 12 02:24:40.453 2014 (UTC + 6:00)
System Uptime: 0 days 9:54:44.857
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88007c0bd60, 0, fffff8000327fe5b, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )

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

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


Loading Dump File [C:\Users\Usra\Downloads\SF_tompus\SF_24-01-2014\012414-17331-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a06d0
Debug session time: Sat Jan 25 00:33:40.275 2014 (UTC + 6:00)
System Uptime: 0 days 7:57:44.680
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8886, fffffa8000d67ca0, fffffa8000581100, 205}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )

Followup: MachineOwner
---------
Start by taking Memtest.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
25 Jan 2014   #3
tompus

Windows 7 Ultimate x64 SP1
 
 

Thanks koolkat77, I'll start memtest and send results.
My System SpecsSystem Spec
.

04 Feb 2014   #4
tompus

Windows 7 Ultimate x64 SP1
 
 

Memtest86 did not show errors after 8 passes of all combinations of stick-slot, but after testing I changed slots of my RAM sticks, and I dont have BSOD.
Now, I'm going to wait a few weeks and if I have a BSOD again, I'll answer to you.
Thank you
My System SpecsSystem Spec
Reply

 BSOD ntoskrnl.exe +75bc0




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support
dxgkrnl.sys and ntoskrnl.exe+75bc0 BSOD, help please?
So I made this thread... http://www.sevenforums.com/general-discussion/345429-lots-programs-have-stopped-working-also-glitchy-screen.html#post2883271 but after a week I JUST got a BSOD so I guess I would like some troubleshooting for this, I think I'll copypaste what I posted in that thread. "An...
BSOD Help and Support
BSOD ntoskrnl.exe +75bc0
Hi, For the past couple moths my computer has been bluescreening due to ntoskrnl.exe +75bc0. It happens randomly sometimes when I'm playing a game other times when I'm watching youtube or a stream. Any help would be appreciated.
BSOD Help and Support
BSOD DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+75bc0
Hi all, Last few days I'm experiencing BSOD. After couple of days of browsing, searching, updating drivers etc. I find myself powerless. Please, can anyone help? Thank you in advance. Jonci
BSOD Help and Support
BSOD DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+75bc0
Hallo everyone, I am experiencing again this DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 fffffa80`073f0060 fffff800`00b9c3d8 fffffa80`06b8d540 ntoskrnl.exe+75bc0 6.1.7601.18247 (win7sp1_gdr.130828-1532)
BSOD Help and Support
BSOD DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+75bc0
Hi, Good Day Just got my HP ZBOOK 14 a month ago, since day one I am keep getting BSOB of DRIVER_POWER_STATE_FAILURE BUG CHECK: 0x0000009f Parm 1 = 00000000`00000003 Parm 2 = fffffa80`0d506a10
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 17:38.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App