BSOD while idling on clean install

BSOD with Pointer reference error or something of the likes this morning. It was too fast by the time I noticed.
Really need this to stop BSOD on me or ill be forced to use my laptop only for college

Code:

BugCheck 18, {0, fffff8800ab39600, 2, fff0f0f0fff0f0ef}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )

Code:

Usual causes:  Device driver, kernel, hardware

This bugcheck indicates that a device driver has lowered the reference count for a device object too many times, by making extra routine calls which lower the reference count for the object. The reference count I believe is the amount of handles still open which refer to that object.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Thanks. Ill run this now and check back in a day. I always did suspect driver(s) but I really don't know.

I think it's drivers, and will forward for an update :)

No BSOD so far. I questioned if it was even running, so I went back in and looked.
5 drivers show "Never Loaded" status.
alsysio64.sys .... part of core temp that is not running
dump_diskdump.sys .... no info
hxctlflt.sys .... web cam driver
sncduvc.sys .... web cam driver
snp2uvc.sys .... web cam driver

Now I had problems in the past with my web cam. In Yahoo Messenger it caused BSOD on connection to a video call.
Eventually realized it was my cam and no driver update would stop this, I just used Skype instead and had no problems since.
With this fresh install of W7, I never installed the cam drivers and it has worked fine for Skype. Also, every BSOD I have had since about Feb, the cam was not in use. Around that time is when I stopped using Yahoo.

It just showed they weren't loaded for verification since you probably disabled the device or those drivers are meant for the webcam, but Windows couldn't find any on your system.

Driver Verifier running in the background, you can open a elevated command prompt, and then type:

Code:

verifier /query

To check if Driver Verifier is running or not.

Seems to be running and no problem, if Im reading it correctly
Also I did not disable the cam or any device, running normal mode too

Code:

8/24/2013, 10:46:05 AM
Level: 00000FBB
RaiseIrqls: 0
AcquireSpinLocks: 29818257
SynchronizeExecutions: 3102878
AllocationsAttempted: 52987521
AllocationsSucceeded: 52987521
AllocationsSucceededSpecialPool: 52987521
AllocationsWithNoTag: 47
AllocationsFailed: 0
AllocationsFailedDeliberately: 0
Trims: 9711601
UnTrackedPool: 51465631

Yeah it's fine, keep it running :)

I just clicked on core temp because it wasnt running. I got the sideways pixelated crash the shows for an instant before BSOD and it got stuck there. Now it wont boot into normal mode.

Updated: Booted safe mode and then restarted like normal

To be honest, I don't know why that happened, and hopefully you'll get a BSOD from Driver Verifier.