BSOD randomly happens every day, mainly error 0x0000003b

bsod321

New member
Local time
5:53 AM
Messages
1
Hello,
These BSODs are happening daily, and I can't find the cause of it myself. I have tried the following:

  1. CHKSDK /r (no errors)
  2. memtest86 (no errors)
  3. tried all kind of stress tests (CPU, GPU)
  4. resetting all components of PC
  5. reinstalled AMD Driver(installed disc version got BSOD, updated got BSOD, installed clean version from website got BSOD anyway...)
  6. Updated chipset, audio, ethernet drivers
  7. Checked for viruses with malwarebytes
I have MSE anti-virus, so I don't think it's the cause.
The last thing what I can do is to format HDD and reinstall OS but it's the least thing I want!
It would be really great if someone could see these logs.
Edit: Forgot to mention I installed OS in 2014-08-12 and started getting BSODs at least once a day starting with 2014-08-15. Maybe it's something related with MS updates.
 
Last edited:

My Computer My Computer

At a glance

Windows 7 Ultimate x64Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz4096MB RAMMSI AMD Radeon R9 270x
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 7 Ultimate x64
CPU
Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz
Motherboard
MSI B85-G41
Memory
4096MB RAM
Graphics Card(s)
MSI AMD Radeon R9 270x
Hard Drives
Samsung ST3500320AS
Internet Speed
100 Mbit/s
Antivirus
MSE
Browser
Mozilla Firefox
Code:
BugCheck 3B, {c0000005, fffff80002e8ace5, fffff88008458630, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeAcquireSpinLockRaiseToDpc+55 )

Followup: MachineOwner
---------
Code:
BugCheck A, {8000003f, 2, 1, fffff80002edd0d8}

Probably caused by : ndis.sys ( ndis!ndisKillReceiveWorkerThreadPool+a4 )

Followup: MachineOwner
---------
Hi bsod321.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If there is no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip


Let us know the results, with the subsequent crash dumps, if any.
 

My Computer My Computer

At a glance

Microsoft Windows 10 Pro Insider Preview 64-bitIntel(R) Core(TM) i3-4130 CPU @ 3.40GHzCorsair Vengence 4GB x2 (8.00GB Dual-Channel ...2047MB GeForce GTS 450 (ZOTAC International)
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
Back
Top