MasterChief
Banned
- Messages
- 1,883
Bingo, and we have a winner here. Two, actually and I can't believe I'm being kind enough to go against how I said I would not touch with 3rd party a/v.
Check your timings compared to the SPD - they are way off.
Set the bios manually to reflect SPD timings.
After, I suggest a run of from elevated prompt:
chkdsk /r
Reboot as it asks. Choose Y.
ALSO - YOU INSTALLED NORTON WHICH IS NOW CRASHING SYSTEM ??????????? <<<<< AMAZING I MIGHT SAY, HERE - AS IN, ARE YA KIDDING? lol MY MIND ONLY ACCEPTS THIS AS SOME KIND OF JOKE PLAYED. (Um, use the tool to remove it.) <<<< Just showing honesty of thoughts, is all.
Classic Norton 0x24 stop:
Check your timings compared to the SPD - they are way off.
Set the bios manually to reflect SPD timings.
After, I suggest a run of from elevated prompt:
chkdsk /r
Reboot as it asks. Choose Y.
ALSO - YOU INSTALLED NORTON WHICH IS NOW CRASHING SYSTEM ??????????? <<<<< AMAZING I MIGHT SAY, HERE - AS IN, ARE YA KIDDING? lol MY MIND ONLY ACCEPTS THIS AS SOME KIND OF JOKE PLAYED. (Um, use the tool to remove it.) <<<< Just showing honesty of thoughts, is all.
Classic Norton 0x24 stop:
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 24, {b500190637, ffffd0002595b568, ffffd0002595ad70, fffff80000a44b6a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsProcessUsnRecordsForCommit+1aa )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 000000b500190637
Arg2: ffffd0002595b568
Arg3: ffffd0002595ad70
Arg4: fffff80000a44b6a
Debugging Details:
------------------
Code:
*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
My Computer
System One
-
- OS
- 7601.18247.x86fre.win7sp1
- Computer type
- PC/Desktop
- System Manufacturer/Model
- Self-built Intel based
- CPU
- Pentium D 925 3.0 GHz socket 775, Presler @ ~ 3.2 GHz
- Motherboard
- Intel DQ965MT
- Memory
- Hyundai 2 GB DDR2 @ 333 MHz
- Graphics Card(s)
- ASUS DirectCU II HD7790-DC2OC-2GD5 Radeon HD 7790 2GB 128-Bit GDDR5
- Sound Card
- MOTU Traveler firewire interface
- Hard Drives
- 1 Seagate Barracuda SATA II system/boot drive 80 GB, 2 Western Digital hdds - 1 is SATA II Caviar Black 1 TB attached to card (assorted media, page, temp), other is SATA I 420 GB (games, media, downloads)
- PSU
- Thermaltake 450W
- Cooling
- stock Gateway cooling, extra large fan in rear of case
- Keyboard
- Alienware/Microsoft Internet kb
- Mouse
- Logitech M510
- Internet Speed
- Optimum Online, fast for US
- Browser
- Pale Moon
- Antivirus
- Kaspersky integrated into ZoneAlarm+Antivirus