- Local time
- 12:25 PM
- Messages
- 35,002
This is a verifier enabled dump.
But it does not catch anything there ... even in the raw stacks.
Generally a verifier enabled dump is supposed to express the failing driver before the first break point (the dotted line at the bottom of the code box).
So it is very doubtful that it is actually a driver that is causing the issue.
But before deciding, better we let verifier to have another run. Please do it again?
Code:
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
Code:
BugCheck A, {35ffffffe2, 2, 0, fffff80003324ba6}
Probably caused by : ntkrnlmp.exe ( nt!ViIrpDatabaseFindPointer+46 )
Followup: MachineOwner
---------
So it is very doubtful that it is actually a driver that is causing the issue.
But before deciding, better we let verifier to have another run. Please do it again?
My Computer
- 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