DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP
tcpip.sys
Edited by fidai, 02 January 2011 - 11:03 AM.
Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!
Edited by fidai, 02 January 2011 - 11:03 AM.
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
(Click to consult the online Win XP Resource Kit article.)
A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.
0x00000024: NTFS_FILE_SYSTEM
(Click to consult the online MSDN article.)
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.
I am to believe this is with the system sitting idle. If this is the case then we may be looking at a startup or service running in the background causing it. Booting into Safe Mode will load basic drivers and minimum Services. If the issue doesn't happen then we will look at these two areas further.Am having a problem by getting this blue screen every hour sometimes every 30 min
Am gonna do that now, btw i didnt mention that i ran memotest-86 all night with 13 pass and 0 error.I also tested cpu for like 6 hours with np.
Edited by fidai, 03 January 2011 - 03:12 AM.
OK I didn't realize there was a sound problem also.
OK I will await your results.
0 members, 1 guests, 0 anonymous users
Community Forum Software by IP.Board
Licensed to: Geeks to Go, Inc.