Windows 7 Forums
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.


Windows 7: BSOD while browsing in internet and play games windows

16 Apr 2012   #1

windows seven ultimate, in 32 bit
 
 
BSOD while browsing in internet and play games windows

Hi Guys,

The problem is that I'have had in my system is random BSOD's
Sometimes writing a letter, a movie, a game windows or acess to internet;

IRQL_NOT_LESS_OR_EQUAL

MEMORY_MANAGEMENT

DRIVER_IRQL_NOT_LESS_OR_EQUAL

and sometimes when BSOD's occours many times and i reboot and occours:
Bootmger image is corrupt.



I've attached the dmp files


System Information (local)
computer name: OI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145964032 total
VM: 2147352576, free: 1976762368


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 12-04-2012 18:31:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-14437-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3FF)
Bugcheck code: 0xBE (0xFFFFFFFF82873A4C, 0x2873121, 0xFFFFFFFF8078AEDC, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12-04-2012 18:31:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x2C2F1)
Bugcheck code: 0xBE (0xFFFFFFFF82873A4C, 0x2873121, 0xFFFFFFFF8078AEDC, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: RunTime da Estrutura de Controladores de Modo de Kernel
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.


On Thu 05-04-2012 18:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040512-20312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF04)
Bugcheck code: 0x1A (0x41284, 0x72B21001, 0xAEC, 0xFFFFFFFFC0802000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Wed 04-04-2012 19:26:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040412-29671-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x620C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x2C7068, 0xFFFFFFFF9FE4B978, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestor de Filtros de Sistema de Ficheiros da Microsoft
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.


On Tue 03-04-2012 18:53:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-17765-01.dmp
This was probably caused by the following module: ew_jucdcacm.sys (ew_jucdcacm+0x4E96)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFFFF8638D5D8)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\ew_jucdcacm.sys
product: ew_jucdcacm Driver (x86)
company: Huawei Technologies Co., Ltd.
description: ew_jucdcacm Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: ew_jucdcacm.sys (ew_jucdcacm Driver, Huawei Technologies Co., Ltd.).
Google query: ew_jucdcacm.sys Huawei Technologies Co., Ltd. WDF_VIOLATION




On Tue 03-04-2012 08:51:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040312-17640-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x43813)
Bugcheck code: 0x1 (0xFFFFFFFF82A3E62E, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 02-04-2012 18:14:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-13421-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1456EB)
Bugcheck code: 0x50 (0xFFFFFFFFFD98B4E4, 0x1, 0xFFFFFFFF8295B943, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 para vários utilizadores
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.


On Sat 31-03-2012 13:51:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033112-12421-01.dmp
This was probably caused by the following module: hal.sys (hal+0x5CBA)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Sat 31-03-2012 13:49:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033112-13328-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x465A5)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF807C7750, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 20-03-2012 17:40:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032012-13171-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFF8287B788, 0x287B121, 0xFFFFFFFF8BE63B94, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 16-03-2012 18:12:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-21593-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x9E2, 0x1A0D009)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Fri 16-03-2012 18:11:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-18015-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x1A (0x41287, 0x63416D4D, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Fri 16-03-2012 18:07:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031612-19640-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82648F2B)
Bugcheck code: 0x7F (0x5, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: Unknown .
Google query: Unknown UNEXPECTED_KERNEL_MODE_TRAP




Conclusion
13 crash dumps have been found and analyzed. 3 third party drivers have been identified to be causing system crashes on your computer

My OS is a windows 7 ultimate x86 system, 32 bits. I have Windows Security Essentials installed.

Hopefully someone here can help me out!
Thanks in advance!

Norba




Attached Files
File Type: zip Windows_NT6_BSOD_jcgriff2.zip (616.2 KB, 6 views)
File Type: txt BSOD erros my computer.txt (24.0 KB, 4 views)
My System SpecsSystem Spec
.

16 Apr 2012   #2

Win 8 Release candidate 8400
 
 

No dmp's included in upload try this method

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:
Quote:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
My System SpecsSystem Spec
16 Apr 2012   #3

windows seven ultimate, in 32 bit
 
 
And now...

i attach another zip files, ok?

But konw the i don't have dumps file, is empty :S nozzy

thanks


Attached Files
File Type: zip Seven Forums.zip (773.7 KB, 3 views)
File Type: zip Windows_NT6_BSOD_jcgriff2.zip (616.2 KB, 3 views)
My System SpecsSystem Spec
.


16 Apr 2012   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by norbas View Post
i attach another zip files, ok?

But konw the i don't have dumps file, is empty :S nozzy

thanks
Unfortunately no. There are no DMPs in either file.


For dumps to be produced. . .
▪ Page file must be on OS drive
▪ Page file base allocation size must be > than installed physical RAM
▪ Windows Error Reporting (WER) system service should be set to MANUAL
▪ Set page file to system managed, OS drive

Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump

The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD

Thanks to jgriff2 @sysnative.com
My System SpecsSystem Spec
17 Apr 2012   #5

windows seven ultimate, in 32 bit
 
 

I attach ONE BSOD dmp.
New attachs to see...What I can do? Help....

ntkrpamp.exe


BSOD
MEMORY_MANAGEMENT




System Information (local)
computer name: OI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145964032 total
VM: 2147352576, free: 1942040576


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 17-04-2012 17:47:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041712-16250-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA10A6)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0014EC0, 0x5CBDF867, 0xFFFFFFFFC00146C2)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Tue 17-04-2012 17:47:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!PsReturnProcessPagedPoolQuota+0xAC6)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0014EC0, 0x5CBDF867, 0xFFFFFFFFC00146C2)
Error: MEMORY_MANAGEMENT
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.
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: ntkrpamp.exe .



Conclusion
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites


System Information (local)
computer name: OI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145964032 total
VM: 2147352576, free: 1942040576


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 17-04-2012 17:47:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041712-16250-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA10A6)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0014EC0, 0x5CBDF867, 0xFFFFFFFFC00146C2)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Tue 17-04-2012 17:47:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!PsReturnProcessPagedPoolQuota+0xAC6)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0014EC0, 0x5CBDF867, 0xFFFFFFFFC00146C2)
Error: MEMORY_MANAGEMENT
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe MEMORY_MANAGEMENT




Conclusion
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites


Attached Thumbnails
BSOD while browsing in internet and play games windows-bsod-problem-1.jpg   BSOD while browsing in internet and play games windows-bsod-problem-2.jpg   BSOD while browsing in internet and play games windows-bsod-problem-4.jpg  
Attached Files
File Type: rar BSOD.rar (369.2 KB, 3 views)
File Type: zip 041712-16250-01.zip (26.8 KB, 1 views)
My System SpecsSystem Spec
17 Apr 2012   #6

Win 8 Release candidate 8400
 
 


These crashes were caused by memory corruption probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.




Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.


RAM - Test with Memtest86+






Driver Verifer

Quote:
Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.
Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
17 Apr 2012   #7

windows seven ultimate, in 32 bit
 
 

More Dmp files...........


HELP !


Attached Files
File Type: zip Nova pasta.zip (155.3 KB, 2 views)
My System SpecsSystem Spec
17 Apr 2012   #8

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by norbas View Post
More Dmp files...........


HELP !
You had uploaded only one dmp from the last 3 weeks. It is related to memory corruption.

Have you run memtest? Have you run verifier?
My System SpecsSystem Spec
17 Apr 2012   #9

windows seven ultimate, in 32 bit
 
 

not yet....tomorrow i try and report to it. Wish me luck....

Thanks
My System SpecsSystem Spec
17 Apr 2012   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by norbas View Post
not yet....tomorrow i try and report to it. Wish me luck....

Thanks
My Pleasure and good luck
My System SpecsSystem Spec
Reply

 BSOD while browsing in internet and play games windows




Thread Tools



Similar help and support threads for2: BSOD while browsing in internet and play games windows
Thread Forum
BSOD while browsing internet eg. facebook, yahoomail, playing games BSOD Help and Support
BSOD while browsing Internet, playing FB Games BSOD Help and Support
Random BSOD on games and even on browsing internet BSOD Help and Support
random BSOD when gaming, exiting games, or browsing the internet BSOD Help and Support
BSOD (IRQL Not less or Equal) - Playing games, browsing internet BSOD Help and Support
BSOD 0x0000001e browsing internet or playing games BSOD Help and Support
BSoD whilst playing games, idling and browsing the internet. BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 03:49 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33