Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: d1 BCP1: 00000040 BCP2: 000000FF BCP3: 00000000 BCP4: 91535FDB OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\102310-17109-01.dmp C:\Users\OM SHAKTHI COMPUTERS\AppData\Local\Temp\WER-32203-0.sysdata.xml Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

Hi! Usually this is a driver issue, If you can locate C:\Windows\Minidump\102310-17109-01.dmp you can submit it for analysis to pinpoint the faulting software. However there are general troubleshooting procedure for this type of bsod. Determine what software or hardware have you added to the system before this happens. You can do last known good configuration from windows advanced boot option (it is when you press f8 upon bootup) if that doesn't work try system restore http://www.cesabarre.com/

A bugcheck (BSOD) is a mechanism to protect your PC from damage. Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. http://msdn.microsoft.com/en-us/library/ff560244%28VS.85%29.aspx It is also helpful to take a look at the dumps. Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your Skydrive [1] and post a link here, so that I can look at the dumps with the debugger and to to see the cause of the crash. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode. Perform a clean startup to determine whether background programs are interfering with your game or program If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause. Another way is enable muni-dump and use Windbg. Please refer: How to read the small memory dump files that Windows creates for debugging You may paste the result in your next post for analyzing. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.