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.

If I switch my PC on first thing in the morning I get a lovely BSOD "What Joy" , when I eventually get past the BSOD by reset and selecting start in normal mode it starts up ok. When I've finnished using it I always turn it fully off including mains power, but if I were to turn it on later the same evening it powers up fine as if BSOD never existed.

Every time I've had a BSOD it throws up a different code, I've done a "Who's Crashed" and below are the results

On Sat 14/12/2013 10:38:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121413-7051-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Thu 12/12/2013 10:40:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121213-6864-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BC46090, 0xFFFF, 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.

On Wed 11/12/2013 14:48:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121113-6520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BAACDD0, 0xFFFF, 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.

On Tue 10/12/2013 13:54:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121013-5647-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Mon 09/12/2013 13:07:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120913-5896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800B8CE090, 0xFFFF, 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.

On Sun 08/12/2013 10:26:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-5226-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 07/12/2013 13:43:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-4648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800B83FB90, 0xFFFF, 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.

On Sat 07/12/2013 13:42:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-6520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BB7A390, 0xFFFF, 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.

On Sat 07/12/2013 13:41:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-6052-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003186068, 0xFFFFF880031858C0, 0xFFFFF80003091CFB)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Fri 29/11/2013 12:59:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112913-6614-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800BC075D0, 0xFFFF, 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.

14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

On Wed 18/12/2013 13:09:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121813-6302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C1D75D0, 0xFFFF, 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.

If you ran memtest86+ for at least 7 passes and it resulted no errors, enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun 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.

BSOD From cold start WIN 7 X 64 Ultimate

BSoD on cold start and during intense use.This isn't a new issue but I've only recently really started playing GTA 5 and Black Desert both of which will cause a BSoD randomly while playing. I also tend to crash with a BSoD or just a black screen when first starting the PC.
If you need any other info please let me know.

BSOD Help and Support

BSOD only on cold start up, then restarts.Hello to everyone!
About two months ago I build my first pc (after many sacrifices to get the money).
But I have from the beginning this frustrating bsod.
It appears only at cold start up, not appears in a restart or in warm start up.
If the pc is turned off for several hours (tipically...

BSOD Help and Support

BSOD not specific to loading but always within 5 min of cold startThis is driving me crazy, I have a gaming rig which has been fine up until Dec 16.
I did update some drivers with the IOrbit Driver program on that day.
This is what happens, I get one BSOD from a cold boot within 5-15 minutes, This occurs wither or not I actually log onto windows, windows...

BSOD Help and Support

Assist with bsod cold startHi
I hope someone can assist me are having cold start blue screen, so I turned of auto restart, to see what blue screen said, IRQL_NOT_LESS_OR EQUAL (forgot to write down the complete set of 0s etc however last set are 0xfffff80002cf3f74 hopefully someone may just kno what this refers to ie...

BSOD Help and Support

BSOD after cold start.Hello all, I made my own computer in the summer, everything went fine until i turned it off for a night and it took around 20 restarts until it would come back on, just from BSOD's right after the "Windows is loading" black screen with the emblem on it.
Here are my system specs DxDiag.txt | Game...