Help: Windows 7 Blue Screen of Death Caused By Address : ntoskrnl.exe+75bc0

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

jim_blake

Reputable
Mar 3, 2015
34
0
4,530
Hi. I had my first ever Blue Screen of Death in my brand new build of less than a month old. I was just browsing the web with Firefox 35.0 with a lot of tabs open when it went all blue!

I have installed all the drivers from the mobo CD and didn't update them. I didn't update the Windows either. I'm trying to download and update any drivers that I can find on MSI website!

My specs:
Mobo: MSI H81-P33
CPU: Intel Core i3 4150 (no OC)
GPU: Intel HD 4400
RAM: 2x4GB 1600MHz (no OC)
HDD: 1TB WD
PSU: Corsair 430w
OS: Windows 7 Ultimate SP1 64-bit

Here's the dump file.

Here's what BlueScreenView shows:

==================================================
Dump File : 030815-17503-01.dmp
Crash Time : 3/8/2015 11:16:38 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 00000000`3910055c
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`73dcdbd5
Parameter 4 : 00000000`00000008
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030815-17503-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 281,696
Dump File Time : 3/8/2015 12:05:17 PM
==================================================

I'd appreciate any comments and suggestions.
 
Solution
Voltages look ok, at least on the surface anyhow, thanks for that by the way. I was about to give up on you for a minute there. Heh.

So, the next thing I would do is go ahead and run Memtest again on each module individually. Just remove all but one module, test it then repeat the process with the next module.


I'd also go to the


motherboard product page for Windows 7 64bit drivers (<-------Click here to go to that page)


download and install the following drivers:

Realtek High Definition Audio Driver

Realtek PCI-E Ethernet Drivers

Intel Chipset Driver

Intel Management Engine Driver+Microsoft hotfix

Intel Smart Connect Technology Driver

Intel USB 3.0 Driver

Intel VGA Driver.


Then reboot and see if you have any...


The PC is running good and stable and the BSOD has not come up since the incident a few days ago (It actually came up after a month of using the PC), and I'm using the data on the second HDD. Is there a software or any method to test the second HDD?
 
Run Seatools for Windows. Run the Short drive self test and the Long generic.

http://www.seagate.com/support/downloads/item/seatools-win-master/



There are really no software based testing utilities that can ENTIRELY eliminate a hardware component from suspicion, they only diminish the likelihood of it being bad, so even if a particular component passes testing like Seatools, for drives, or Memtest, for memory, it doesn't absolutely mean that component can't still be the issue. I've seen plenty of RAM that passes Memtest but IS at fault and when replaced the issue cannot be replicated. However, you have to start somewhere even in those cases.
 
I tested the memory modules one by one and found the faulty one, then RMAed it and got a new one as a replacement. Tested the new one and it's just fine.
In the meantime updated all the drivers to latest version.
Hope the BSOD won't show up again.
Guys, thank you so much for all the help.
 

I tested the second hard drive using HD Tune and it looks like it has two damaged spots. In the five years I was using it I didn't notice it. Any idea?
tQv9VrBRH.jpg

oUmkHoTn.jpg

 
You should be able to find and use a utility that will cordon off those areas to stop the system from attempting to use it, but honestly, I'd get a replacement drive. Once areas begin failing, it generally not only continues to spread to other areas, but can accelerate as well. Once they start dying, they are no longer trustworthy with your data.