Solved BSOD - can boot system only in Safe Mode

marekb · Jul 30, 2011

After some days of use of a new computer a BSOD begin to appear. First, after booting computer some times in safe mode I managed to boot it normally. System word normally two days and BSOD appeared again. Now I can boot the system only in Safe Mode. Since the system is fairly new with a few programs I expect some hardware problems, however I am not sure.

Since I can boot the system only in Safe Mode I was unable to perform Health Report.

System informations:
Windows 7 Professional x64
It was the only system installed on the computer
It is MSDN AA version of the system
The age of the system (hardware) as well as OS is around two weeks

Hardware:
CPU: Intel Core i5 2400
Motherboard: Gigabyte GA-H67MA-USB3-B3
Memory: GoodRam DDR3 2x4GB 1333Mhz
Graphics Card: GeForce GTX 460 Gigabyte [GV-N460OC-1Gi]
PSU: OCZ ModXStream Pro 500W 80+ modular SLI
HDD: Samsung SpinPoint F3 1TB [HD103SJ]

Thank you for your help.

marekb · Jul 31, 2011

After setting BIOS option to "Optimized" I managed to boot the system normally. I attach System Health Report.

I have also run Memtest for several hours getting no errors.

Any idea what was the reason of BSOD?

Pls help.

usasma · Jul 31, 2011

Ensure that you have all available Windows Updates. Most systems with SP1 have over 50 updates - yours has 32

Your system has issues with this device:

Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.

In most cases that I see, this is indicative of a virus infection.
Please run several of these free antivirus scans: Free Online AntiMalware Resources (read the details at the link)
If infected, please post over in the Security forums for assistance: System Security - Windows 7 Forums

If not infected, Comodo Internet Security has been known to cause BSOD's in some systems. To test this on your system, please:

- Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Comodo Internet Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Comodo Internet Security using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN http://forums.comodo.com/index.php?action=dlattach;topic=17220.0;attach=17692 (Requires registration)
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Gigabyte's EasyTune6 is also known to cause BSOD's in Win7 systems. But, in most cases, the driver is older than the one on your system (yours is from 2009). Still, to be sure, please uninstall the EasyTune6 program from your system and monitor for further BSOD's.

Lot's of different errors blaming different causes. And, lot's of memory access errors (0xc0000005).
I suspect malware. If not malware, then I suspect Comodo.
If all else fails, post back and we'll start hardware diagnostics/stress testing.
Good luck!

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073011-21231-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 14:28:34.702 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:11.576
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_CLASSPNP!TransferPktComplete+1ce
Bugcheck code 0000000A
Arguments 00000000`00000080 00000000`00000002 00000000`00000001 fffff800`03a8cc3f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073011-24055-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 08:29:42.803 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:16.052
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Rotate+2d0 )
BUGCHECK_STR:  0x1a_5002
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x1a_5002_dxgmms1!VIDMM_PROCESS_HEAP::Rotate+2d0
Bugcheck code 0000001A
Arguments 00000000`00005002 fffff700`01080000 00000000`00000310 00020311`fffffffe
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3092
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-18720-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 14:29:38.234 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:13.576
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiGetTopLevelPfn+65
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0315a115 fffff880`0686ac60 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-21543-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 14:26:57.702 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:11.670
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionSet+9b
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`03081905 fffff880`037435d8 fffff880`03742e40
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-17815-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 14:19:54.045 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:11.388
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionSet+9b
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`0308e905 fffff880`037435d8 fffff880`03742e40
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-18018-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 14:11:41.859 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:04.201
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+22
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`033c174a fffff880`031af928 fffff880`031af190
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-22401-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 14:07:21.654 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:12.622
BugCheck D1, {fffff8800133c724, 2, 8, fffff8800133c724}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+3690 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+3690
Bugcheck code 000000D1
Arguments fffff880`0133c724 00000000`00000002 00000000`00000008 fffff880`0133c724
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

marekb · Aug 1, 2011

Thank you for help.

I run on-line scanners (ESET and Trend Micro) founding no infection.

Since again I can boot only in Safe Mode I couldn't uninstall COMODO - probably I can manually delete Comodo directory, but since BOSD happen most often during the boot (usually I cannot boot normally) I doubt if COMODO can be responsible for this.

I decided to reinstall system, but BSOD appeared again. Once some moment after 'Windows is loading files..." had finished, and twice just after selecting "Install Now"/"Repair the system".

Am I correct guessing that this means some hardware problem?

usasma · Aug 1, 2011

If, after reinstalling Windows, you experience BSOD's - it's most often a hardware problem. But it can also be due to other things if you haven't wiped the hard drive prior to reinstalling and if you have added other programs/drivers.

But, let's start with these free diagnostic tests and we'll move on from there:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Click to expand...

marekb · Aug 1, 2011

usasma said:
If, after reinstalling Windows, you experience BSOD's - it's most often a hardware problem. But it can also be due to other things if you haven't wiped the hard drive prior to reinstalling and if you have added other programs/drivers.

The problem is that I can't reinstall Windows since when setup program starts BSOD occurs. I have already run memtest for several hours and no errors were found. I will try with HD Diagnostic

marekb · Aug 1, 2011

HDD test found en error: RAM Error, code AJ41.

Thus, I am going to ask computer's retailer to change hard disk.

usasma · Aug 1, 2011

Thanks for letting us know!

marekb · Aug 2, 2011

Thank yu very much for helping.

Solved BSOD - can boot system only in Safe Mode

marekb

New member

My Computer

At a glance

marekb

New member

My Computer

At a glance

usasma

Mr. Cranky Pants

My Computer

At a glance

marekb

New member

My Computer

At a glance

usasma

Mr. Cranky Pants

My Computer

At a glance

marekb

New member

My Computer

At a glance

marekb

New member

My Computer

At a glance

usasma

Mr. Cranky Pants

My Computer

At a glance

marekb

New member

My Computer

At a glance

Similar threads

Solved BSOD - can boot system only in Safe Mode

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer