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.

I have had the computer on all day without any BSOD! I am hoping the BIOS update and SP1 installation has solved the issue. Thank you so much Arc, for all your time and effort to help me. It is sincerely appreciated. Hopefully (fingers crossed) my computer will have no more hissy fits. If it does.. I know where to come for help!

Alright, things went well all day yesterday, computer was shutdown last night, and within about an hour I had a BSOD.
Seems my comp is still having hissy fits.

On Tue 12/31/2013 4:31:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-33727-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xC30E)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880033545B8, 0xFFFFF88003353E10, 0xFFFFF8800124730E)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Tue 12/31/2013 3:47:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-28345-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A010523EB0, 0xFFFFF8A010524AF0, 0x4C4F940)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 12/31/2013 10:08:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-23368-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x9A879)
Bugcheck code: 0xC4 (0xF6, 0xAC, 0xFFFFFA800A35FB30, 0xFFFFF8800F14D879)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

There was a Beta update for the Nvidia card, which I went ahead and installed. (via Nvidia Experience)

There is no defrag program installed on this comp other than the default program.

Uninstalled Nvidia drivers as listed and ran DDU in safe mode. After reboot, installed 314.22 graphics driver and PhysX, unchecking everything else and checking clean install. Rebooted again and once the windows loaded and the desktop came up the system went into another BSOD.

On Wed 1/1/2014 5:39:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010114-45240-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41287, 0x1, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

BSOD 0x3B and 0x1E

Intermittent BSOD; 0x1e, 0x7e, 0x3bHaving to type quickly as crashes are random, so apologies for mistakes.
Removed programs commonly related to causing problems, updates graphics driver on APU, cant update wireless drivers as its discontinued (possible culprit?).
Crashes are very random, can be days between or a loop of 5...

BSOD Help and Support

BSOD whenever playing games, 0x1E or 0x3BHi everyone,
So sorry to be just dropping in--I've been lurking since my first laptop (now on third) and I've been able to fix BSODs just reading. But this one's really a pain.
I get BSODs whenever I game--this happens whatever game I play, sometimes a few minutes after I start, sometimes a...

BSOD Help and Support

BSOD 0x3B / 0x1E @ ntoskml.exe during gamingOver the last few days I've been having constant crashes. It's not always a bluescreen, sometimes just an instant restart, others a total lockup with audio still coming out. (Just a loud continuous noise of what it was playing before crash) Sometimes it actually blue screened so I did get mini...